Yesterday, Quentin, Eric and I had a discussion on SILC about what the user experience (and, at some level, the developer experience) should look like under Etoile when interacting with Documents. Rather than debating the merits of each of our points, I'd rather just ask a series of questions that I hope gets to everyone's vision of the interaction model.
1. How does a user create a new (generic) Document? What menu steps must they walk through? 2. Assuming a user wants a specific Document type (say, a vector art document that can be easily converted to SVG), what steps must they walk through to get their original generic Document into a format easily converted to that specific type? 3. If a user wants to then edit that (now SVG-friendly) Document, how do they launch the proper tools/palettes? 4. When in editing mode, what app should be represented in the system's Menu bar? 5. When a user closes (hides/puts away) the current Document, what methods can they use to reopen it? 6. What happens when a user selects on a specific object (a bar graph, for example) within a compound Document? What happens when a user wants to edit that object? How do they initiate that process? 7. How does a user manage the various Services on their system? Through what type of UI? 8. How are those Services organized? 9. How does a user get new Services on their system? Getting answers to these questions should help with some of the specifics of how applications work and are integrated in Etoile. Thanks in advance for contributions. J. _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
