Changes for page Macro Options

Last modified by Ecaterina Moraru on 2013/11/13 12:50
From version 3.4
edited by Ecaterina Valica
on 2012/06/12 17:07
Change comment: There is no comment for this version
To version 1.1
edited by Ecaterina Valica
on 2012/06/12 16:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -Improvements.HomepageContent
Content
... ... @@ -6,52 +6,67 @@
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 14  (((
15 15  == Issues ==
16 -* the include macro rendering is confusing because the user might think he can in-line edit the content
17 -* trying to delete some words in the welcome message results in deleting the dashboard macro
18 -* we need to make clear that the home page content is just using an include macro to display the content located in another place
19 19  
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
19 +
20 20  == Solution ==
21 -* first have all macros collapsed by default
22 22  
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
23 23  )))
24 24  
25 25  (% class="dashboardright right column60 " %)
26 26  (((
27 -== Current ==
28 -(% class="left column50 dashboardleft"%)
29 -(((
32 +== Proposal ==
33 +
34 +=== Current ===
30 30  [[[[image:current.png||style="max-width: 98%; margin-bottom: 3em;"]]>>attach:current.png]]
31 -)))
32 32  
33 -(% class="left column50 dashboardleft"%)
34 -(((
35 -[[[[image:currentCollapsed.png||style="max-width: 98%; margin-bottom: 3em;"]]>>attach:currentCollapsed.png]]
36 -)))
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]]
37 37  
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 +
38 38  (%class='clearfloats'%)((()))
39 39  
40 -== Proposal ==
47 +=== Wireframe ===
48 +[[[[image:wireframe.png||style="max-width: 98%;"]]>>attach:wireframe.png]]
41 41  
50 +(%class='clearfloats'%)((()))
51 +
52 +=== In the wild ===
53 +
42 42  (% class="left column33 dashboardleft"%)
43 43  (((
44 44  
57 +[[[[image:Homepage.png||style="border: 1px dotted #DFDFF2; max-width: 90%;"]]>>attach:Homepage.png]]
45 45  )))
46 46  
47 47  (% class="left column33 dashboardleft"%)
48 48  (((
49 49  
63 +[[[[image:Welcome gadget.png||style="border: 1px dotted #DFDFF2; max-width: 90%;"]]>>attach:Welcome gadget.png]]
50 50  )))
51 51  
52 52  (% class="left column33 dashboardright" %)
53 53  (((
54 54  
69 +[[[[image:Search.png||style="border: 1px dotted #DFDFF2; max-width: 90%;"]]>>attach:Search.png]]
55 55  )))
56 56  
57 57  (%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