Changes for page Improved edit mode

Last modified by Ecaterina Moraru on 2018/09/26 16:02
From version 19.5
edited by Ecaterina Valica
on 2011/09/07 12:23
Change comment: There is no comment for this version
To version 20.1
edited by Ecaterina Moraru
on 2013/11/13 12:48
Change comment: Moved page to http://design.xwiki.org/xwiki/bin/view/Improvements/ImprovedEdit

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.evalica
1 +xwiki:XWiki.risherry
Content
... ... @@ -1,96 +1,1 @@
1 -{{velocity}}
2 -$xwiki.ssx.use("Improvements.WebHome")
3 -$xwiki.ssx.use("Standards.WebHome")
4 -{{/velocity}}
5 -
6 -== Community Feedback ==
7 -
8 -{{info}}
9 -Discussed: [VOTE] Edit UI improvements and panelless edit: http://xwiki.markmail.org/thread/qq5zixa2qyqkppcj
10 -JIRA: http://jira.xwiki.org/browse/XWIKI-6404
11 -{{/info}}
12 -
13 -== Goal ==
14 -
15 -The goal is to improve the usability of the edit modes, and to give more space to the edit area by removing the edit mode panels, which don't bring real value.
16 -
17 -== Overview ==
18 -
19 -Note that the images have a smaller edit area, in order to fit inside the content area of this page, so they look a bit more crowded than they will be in practice.
20 -
21 -In all the edit modes, there are no panels on the right side anymore.
22 -
23 -[[image:plwed.png]]
24 -
25 -[[image:plged.png]]
26 -
27 -[[image:ploed.png]]
28 -
29 -[[image:plced.png]]
30 -
31 -== Individual changes ==
32 -
33 -=== Wiki editor improvements ===
34 -[[image:plwed1.png]]
35 -
36 -==== 1. Parent and title above the content in wiki/wysiwyg mode, having the same look as they do in view mode ====
37 -
38 -The advantage is that they have consistency, being in the same place as the view interface, so the user knows where to look for them. A minor possible problem is that they might not look like editable fields at a first glance, since they don't have the classic size and color of normal input fields.
39 -
40 -==== AjaxSuggest for the parent field ====
41 -
42 -image:plwed2.png
43 -
44 -==== 2. List of included documents above the content, and a new label for the content ====
45 -
46 -==== 3. Syntax switcher and syntax help above the content area ====
47 -
48 -I believe that the syntax of the content is a very important setting, and it is closely related to the content, so the syntax chooser should be as near the content as possible. The same thing for the syntax help, since a side panel can easily be overlooked.
49 -
50 -Also note that the syntax help and switcher are not present in the WYSIWYG editor, since the wiki syntax is not relevant in such an editor. Still, this is debatable, since the WYSIWYG editor has the Source tab.
51 -
52 -==== 4. Better label for the version comment field ====
53 -
54 -"Comment" is really not intuitive.
55 -
56 -==== 5. Better position and display of the "minor edit" field ====
57 -
58 -The current position, right next to the Comment label, is crowded and not intuitive, since the checkbox is right between the two labels.
59 -
60 -==== 6. Better position for the autosave field ====
61 -
62 -IMO it is closely related to the save buttons, so it should be near them.
63 -
64 -=== Object editor improvements ===
65 -
66 -image:ploed1.png
67 -
68 -==== 7. Quick access to adding a new object ====
69 -
70 -This is AJAX-powered, meaning that the object will be added without reloading the page and loosing the changes. However, it does create a new version in the background.
71 -
72 -A debate is whether to put it before or after the list of existing documents. I've put it on top since a user that goes to the object editor and wants to add a new object should not have to scroll past the existing objects.
73 -
74 -==== 8. Quick access to add a new object from the same type ====
75 -
76 -Again, AJAX-powered. The new object is displayed expanded initially, since the user probably wants to edit the object that he just added.
77 -
78 -The same debate about the position. I placed it after the existing objects, since the object will be added there (objects are always sorted by their number). Otherwise, in a list of many objects, the user could click at the top of the list, then not see the new object, which appeared bellow the window margin.
79 -
80 -=== Class editor improvements ===
81 -
82 -image:plced1.png
83 -
84 -==== 9. Class switcher at the top of the editor ====
85 -
86 -This switcher now prompts to save the current class before leaving the page.
87 -
88 -It would be possible to remove it completely, since now we have the JumpToPage feature for quick access to other documents, but IMO we should keep it, since:
89 -
90 -* it lists only classes, while GTP requires that the user knows at least part of the target classname
91 -* it goes to the class editor, not to the view more or the content editor
92 -* it separates classes by their space, to faster find the right class
93 -
94 -==== 10. Quick access to add a new property ====
95 -
96 -AJAX-powered, the new property is added expanded at the bottom. I placed it at the top, although I think it should be at the bottom, since the property appears at the end of the list.
1 +{{warning}}Moved to [[design.xwiki.org:Improvements.ImprovedEdit>>http://design.xwiki.org/xwiki/bin/view/Improvements/ImprovedEdit]]{{/warning}}