Changes for page Macro Options
Last modified by Ecaterina Moraru on 2013/11/13 12:50
From version 3.2
edited by Ecaterina Valica
on 2012/06/12 16:58
on 2012/06/12 16:58
Change comment:
There is no comment for this version
To version 1.1
edited by Ecaterina Valica
on 2012/06/12 16:50
on 2012/06/12 16:50
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,0 @@ 1 -Improvements.HomepageContent - Content
-
... ... @@ -6,8 +6,7 @@ 6 6 == Community Feedback == 7 7 8 8 {{info}} 9 -[UX][Idea] 10 -[users] Making it user-friendly to edit pages with macros for new users (was Re: Need some Help & Explanations) http://xwiki.markmail.org/thread/rnhe6tl3x7snquz7 9 +[UX][Idea] Render Switches http://xwiki.markmail.org/thread/jwbbz4ypjqcpwral 11 11 {{/info}} 12 12 13 13 (% class="left column40 dashboardleft" %) ... ... @@ -14,42 +14,60 @@ 14 14 ((( 15 15 == Issues == 16 16 16 +* Hard for users to make the difference between inputs that can contain velocity code and text only inputs 17 +* Hard for users to understand what the velocity code will render 18 +* Hard for simple users to map what they see in view mode with the velocity code in edit mode 17 17 18 18 == Solution == 19 19 20 - 22 +* Have a switch attached to velocity enabled inputs that switch the content from velocity code to rendered content 23 +* The switch acts like an inline preview of the velocity code 24 +* It can be implemented using JS, having a css class hook (like .hasVelocity) to desired inputs 25 +* The default state of the inputs (syntax/rendered) can be customized in the Profile 26 +* The default state should be 'rendered' for simple user and can be 'syntax' to advanced users 27 +* For performance issues the switch should be done at least on demand 21 21 ))) 22 22 23 23 (% class="dashboardright right column60 " %) 24 24 ((( 25 -== Current==26 - (% class="left column50 dashboardleft"%)27 - (((32 +== Proposal == 33 + 34 +=== Current === 28 28 [[[[image:current.png||style="max-width: 98%; margin-bottom: 3em;"]]>>attach:current.png]] 29 -))) 30 30 31 -(% class="left column50 dashboardleft"%) 32 -((( 33 -[[[[image:currentCollapsed.png||style="max-width: 98%; margin-bottom: 3em;"]]>>attach:currentCollapsed.png]] 34 -))) 37 +=== Rendered Input == 38 +[[[[image:rendered.png||style="max-width: 98%;"]]>>attach:rendered.png]] 39 +[[[[image:renderedTitle.png||style="max-width: 98%;"]]>>attach:renderedTitle.png]] 35 35 41 +=== Syntax Input === 42 +[[[[image:syntax.png||style="max-width: 98%;"]]>>attach:syntax.png]] 43 +[[[[image:syntaxTitle.png||style="max-width: 98%;"]]>>attach:syntaxTitle.png]] 44 + 36 36 (%class='clearfloats'%)((())) 37 37 38 -== Proposal == 47 +=== Wireframe === 48 +[[[[image:wireframe.png||style="max-width: 98%;"]]>>attach:wireframe.png]] 39 39 50 +(%class='clearfloats'%)((())) 51 + 52 +=== In the wild === 53 + 40 40 (% class="left column33 dashboardleft"%) 41 41 ((( 42 42 57 +[[[[image:Homepage.png||style="border: 1px dotted #DFDFF2; max-width: 90%;"]]>>attach:Homepage.png]] 43 43 ))) 44 44 45 45 (% class="left column33 dashboardleft"%) 46 46 ((( 47 47 63 +[[[[image:Welcome gadget.png||style="border: 1px dotted #DFDFF2; max-width: 90%;"]]>>attach:Welcome gadget.png]] 48 48 ))) 49 49 50 50 (% class="left column33 dashboardright" %) 51 51 ((( 52 52 69 +[[[[image:Search.png||style="border: 1px dotted #DFDFF2; max-width: 90%;"]]>>attach:Search.png]] 53 53 ))) 54 54 55 55 (%class='clearfloats'%)((()))
- current.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.evalica - Size
-
... ... @@ -1,1 +1,0 @@ 1 -110.3 KB - Content
- currentCollapsed.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.evalica - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.9 KB - Content