On 01/27/2010 02:22 PM, Vincent Massol wrote: > I've discussed it a bit with Guillaume and here are some ideas: > > * In the same manner that we have simple/advanced mode for view mode > (user type) we could also have the same for the edit mode. > * The simple edit mode would be an inplace editing mode where the > page doesn't reload and the user is shown with an edit box for > title/content (still to be decided for the parent). There would be a > button to switch to advanced edit mode. > * The advanced edit mode would be similar to the current edit mode, > i.e panels on the left removed and panels on the right replaced by > advanced edit panels, ie: included docs, syntax change, language > translations, other metadata changes, etc. There would be a button to > swtich to simple edit mode. > * Basically the idea is to do what all tools do when there's not > mandatory options to display, ie create an inspector/panel/dialog box > to move non mandatory stuff out of the main view. > > WDYT?
I don't really like it. All of the fields are important and should be displayed by default (except maybe the syntax switch, which really is an advanced field). Having access to translations is important, and hiding them in a different interface is not good. Changing the parent should be easy. And in general, people rarely go to the alternative edit mode, unless they really want something and they're courageous and they're willing to search for it everywhere. From my experience with users, people are not courageous, they don't just push buttons to see what they do. > > Others: > * I don't really have a pb with the other editors (object/class). So, you think that the class/object editors can be panelless, but the content editors should still have panels? What about consistency and the skin complexity? Did you read my previous email? > * For the class editor, I'd put the class properties as vertical tabs > instead so that opening a property doesn't hide the others from the > view (ie no accordion). What accordion? There's no accordion since 1.9. LATFW. > Thanks -Vincent > > On Jan 25, 2010, at 9:37 PM, Sergiu Dumitriu wrote: > >> Hi devs, >> >> We've been working on improving the editors (content, class, >> object), and now I have some pretty important UI changes to commit, >> but not everybody seems to agree with them, so I bring up a vote. >> >> The whole improvements can be seen on >> http://incubator.myxwiki.org/xwiki/bin/Improvements/ImprovedEdit >> >> Here are the individual voted points: >> >> 0 Remove all panels in edit mode >> >> 1a Parent and title above the content in wiki/wysiwyg mode >> >> 1b The same style in edit mode as in view mode for the parent/title >> fields >> >> 1c AJAX Suggest for the parent field >> >> 2a New label for the content textarea ("Content") >> >> 2b List of included documents after the Content label >> >> 3a Syntax switcher in the top right corner of the content >> >> 3b Syntax help in the top right corner of the content >> >> 3c Syntax help and switcher only in the wiki editor >> >> 4 Better label for the version comment >> >> 5a Right float the Minor edit field >> >> 5b Put the Minor edit label after the checkbox >> >> 6 Move autosave in line with the submit buttons >> >> 7 Introduce new AJAX-powered Add Object i) above the objects ii) >> bellow the objects >> >> 8 Introduce new AJAX-powered Add Object from this class i) at the >> top of the list of existing objects ii) at the end of the list >> >> 9 Move the class switcher in the top right corner >> >> 9b Remove the class switcher >> >> 10 Introduce new AJAX-powered Add Property i) at the top of the >> list of properties ii) at the end of the list >> >> >> I vote +1 for all of the above, except 9b (-0), and with options >> 7i), 8ii), and 10ii) -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
