Dear all, Apologies for skipping an update in May: it was a busy month. I have prepared another iteration for you to test, mostly concerning the UI because the main operations remain adding and removing elements and modules. It's not a lot, but it took me a bit to get up to speed with using React components properly and I think things are pretty solid now, which should pave the way for faster development and collaboration (?). https://raffazizzi.github.io/romajs/ Possible prompts for your feedback are in bold. As I mentioned in my last update, I moved away from organizing elements by modules. I think I heard/read a few times that *people prefer to think about elements rather than modules anyway*. So I've created a unified interface that lists all elements and allows users to: - add/remove elemets - read <desc>s of each element at a glance - filter elements with a search box to look elements up - add remove modules in their entirety - note that modules appear "added" even when only some of their elements are added. This means that to add the rest of the module at once, the user will need to remove the module first, then re-add it in its entirety. This is not unlike dealing with checkboxes that support indeterminate states https://jsfiddle.net/leaverou/ASPUA/. *If you have any thoughts about this please let me know *- it may have consequences I haven't thought of. Eventually, I would like all ODD "items" to end up in this unified list. I'm calling an "ODD item" anything that has an @ident and belongs to a module. Namely: - elements - classes - datatypes - macros Users will be able to hide/show those groups with the "chips" on the top left of the screen. *Am I leaving anything out or mixed something up?* Does this make sense? *Next, I'll move on to other Element operations* (edit, create) and stay away from the UI for a while, unless you all find bugs or hate the unified view. I may need to throw some ideas at the group related to Element operations, so expect a follow up email in the next couple weeks. Also, *I encourage you to work with me :)* What could you work on? For anyone: - Help me draft the components for editing/creating elements https://docs.google.com/presentation/d/1sUESuY9pF3DkHoQMJJjrVMV2SPFQYE1YqmGr... using Material Design Components Web https://github.com/material-components/material-components-web (ie HTML/CSS mockups to be re-used later) - Work on the decision tree that will eventually front-face this Roma tool - Identify element actions https://github.com/raffazizzi/romajs/issues/3 For those interested in coding: - Element operations: we need to write code that perform the changes https://github.com/raffazizzi/romajs/issues/4 on the ODD (in its JSON serialized version); there will be more than one, so we can work together! - Write tests https://github.com/raffazizzi/romajs/issues/6 for new operations - More UI components development: Uploading and downloading the ODD https://github.com/raffazizzi/romajs/issues/5 Happy to do code walkthroughs, set people up, etc. Speak soon, Raff