Changes for page Improved edit mode

Last modified by Ecaterina Moraru on 2018/09/26 16:02
From version 6.3
edited by Ecaterina Valica
on 2010/01/22 16:55
Change comment: Added comment
To version 10.5
edited by Ecaterina Valica
on 2010/01/22 18:24
Change comment: Added comment

Summary

Details

AdvEditMode.pdf
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +242.8 KB
Content
AdvEditMode.svg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +455.6 KB
Content
propD1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +73.9 KB
Content
propE1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Size
... ... @@ -1,0 +1,1 @@
1 +71.8 KB
Content
XWiki.XWikiComments[3]
Date
... ... @@ -1,1 +1,1 @@
1 -2010-01-22 15:52:34.642
1 +2010-01-22 15:52:34.0
XWiki.XWikiComments[4]
Date
... ... @@ -1,1 +1,1 @@
1 -2010-01-22 15:55:33.416
1 +2010-01-22 15:55:33.0
XWiki.XWikiComments[5]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.Sergiu
Comment
... ... @@ -1,0 +1,6 @@
1 +Looks good, except that I'd make the parent input smaller (75/25 or 66/33).
2 +
3 +I'd say:
4 +CONTENT (Includes: Blog.BlogParameters[/], Blog.BlogCode[/])
5 +
6 +Still, in the WYSIWYG editor, does the "Help on the syntax" make any sense? Yes, if we consider the Source tab.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:09:35.0
Reply To
... ... @@ -1,0 +1,1 @@
1 +4
XWiki.XWikiComments[6]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.Marta
Comment
... ... @@ -1,0 +1,7 @@
1 +That looks great.
2 +
3 +Three minor comments:
4 +
5 +* I'd make the title field larger than the parent field, because you usually need to write more in the title field. Of course, then they might look a bit unbalanced, so if this turns out to be an issue they can be left with equal sizes.
6 +* Re "All languages will be in the menu, but will be shown active just the versions that exists for this page" - indeed there must be a difference between the appearance of entries for existing translations and non-existing translation, but I wouldn't say non-existing translation should look/be inactive, because the user should be able to create a new translation, and be aware of this possibility.
7 +* I'm not sure about listing the included documents before the text area, but I can't come up with a much better place either. One option is to list them under the text area, because they are not that important. However, this position would really decrease their visibility.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:19:14.0
Reply To
... ... @@ -1,0 +1,1 @@
1 +4
XWiki.XWikiComments[7]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,2 @@
1 +After some complains about Included Documents and Comment describing text:
2 +[[image:propD1.png||width="900px"]]
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:22:03.0
XWiki.XWikiComments[8]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.Marta
Comment
... ... @@ -1,0 +1,1 @@
1 +How about the complaints about the parent field size? :)
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:23:52.0
Reply To
... ... @@ -1,0 +1,1 @@
1 +7
XWiki.XWikiComments[9]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,3 @@
1 +This prop changes the way last three options are displayed. I prefer propC.
2 +
3 +Included documents have their specific place. Are we sure we want to remove all the panels? Included documents and localization could be better explained in a panel.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:23:59.0
Reply To
... ... @@ -1,0 +1,1 @@
1 +7
XWiki.XWikiComments[10]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,1 @@
1 +:)
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:24:11.0
Reply To
... ... @@ -1,0 +1,1 @@
1 +8
XWiki.XWikiComments[11]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,1 @@
1 +[[image:propE1.png||width="900px"]]
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:43:16.0
XWiki.XWikiComments[12]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,1 @@
1 +I've put the included documents before the text for cases like Blog.BlogCode, when you have pages that contain just included doc and you don't need to scroll to be able to access them.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:45:54.0
Reply To
... ... @@ -1,0 +1,1 @@
1 +6
XWiki.XWikiComments[13]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.Marta
Comment
... ... @@ -1,0 +1,1 @@
1 +For included documents: the brackets should either be around "Includes" as well, or should disappear completely. Otherwise, this looks great.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:50:07.914
Reply To
... ... @@ -1,0 +1,1 @@
1 +11
XWiki.XWikiComments[14]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,1 @@
1 +done - thanks for all the feedback
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:52:40.605
Reply To
... ... @@ -1,0 +1,1 @@
1 +13
XWiki.XWikiComments[15]
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.Marta
Comment
... ... @@ -1,0 +1,1 @@
1 +Just a thought: would the "autosave" part go better on the same line with the form buttons? IMO, semantically, it is more related to the buttons than to the change comment.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 16:54:51.848
Reply To
... ... @@ -1,0 +1,1 @@
1 +11
XWiki.XWikiComments[16]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,1 @@
1 +I didn't test autosave, but every 5 minutes the page saves with the comment described and as minor change if selected?
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 17:11:56.413
Reply To
... ... @@ -1,0 +1,1 @@
1 +15
XWiki.XWikiComments[17]
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.evalica
Comment
... ... @@ -1,0 +1,3 @@
1 +so autosave acts like a minor change with the current comment - the position is ok if we thing autosave apply those fields.
2 +
3 +Being on the line with buttons would describe the save action better. Would fit so well though.
Date
... ... @@ -1,0 +1,1 @@
1 +2010-01-22 17:24:25.282
Reply To
... ... @@ -1,0 +1,1 @@
1 +16