Changes for page Improved edit mode

Last modified by Ecaterina Moraru on 2018/09/26 16:02
From version 14.1
edited by Sergiu Dumitriu
on 2010/01/25 21:15
Change comment: There is no comment for this version
To version 18.1
edited by Sergiu Dumitriu
on 2010/01/25 21:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -25,6 +25,10 @@
25 25  
26 26  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.
27 27  
28 +==== AjaxSuggest for the parent field ====
29 +
30 +image:plwed2.png
31 +
28 28  ==== 2. List of included documents above the content, and a new label for the content ====
29 29  
30 30  ==== 3. Syntax switcher and syntax help above the content area ====
... ... @@ -59,7 +59,7 @@
59 59  
60 60  Again, AJAX-powered. The new object is displayed expanded initially, since the user probably wants to edit the object that he just added.
61 61  
62 -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 documents, the user could click at the top of the list, then not see the new object, which appeared bellow the window margin.
66 +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.
63 63  
64 64  === Class editor improvements ===
65 65  
... ... @@ -69,6 +69,12 @@
69 69  
70 70  This switcher now prompts to save the current class before leaving the page.
71 71  
76 +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:
77 +
78 +* it lists only classes, while GTP requires that the user knows at least part of the target classname
79 +* it goes to the class editor, not to the view more or the content editor
80 +* it separates classes by their space, to faster find the right class
81 +
72 72  ==== 10. Quick access to add a new property ====
73 73  
74 74  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.
plwed2.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.Sergiu
Size
... ... @@ -1,0 +1,1 @@
1 +23.5 KB
Content