Changes for page Macro Options
Last modified by Ecaterina Moraru on 2013/11/13 12:50
From version 1.2
edited by Ecaterina Valica
on 2012/06/12 16:51
on 2012/06/12 16:51
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 (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -6,7 +6,7 @@ 6 6 == Community Feedback == 7 7 8 8 {{info}} 9 -[UX][Idea] 9 +[UX][Idea] Render Switches http://xwiki.markmail.org/thread/jwbbz4ypjqcpwral 10 10 {{/info}} 11 11 12 12 (% class="left column40 dashboardleft" %) ... ... @@ -13,10 +13,18 @@ 13 13 ((( 14 14 == Issues == 15 15 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 16 16 17 17 == Solution == 18 18 19 - 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 20 20 ))) 21 21 22 22 (% class="dashboardright right column60 " %)