Last modified by Thomas Mortagne on 2023/10/13

From version 33.1
edited by Vincent Massol
on 2009/09/24
Change comment: There is no comment for this version
To version 32.1
edited by Vincent Massol
on 2009/09/24
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -20,98 +20,61 @@
20 20  
21 21  [[image:code:[email protected]]]
22 22  
23 -We provide several predefined themes out of the box (and it's possible to create new ones):
23 +We provide several predefined themes out of the box:
24 24  
25 25  [[image:code:[email protected]]]
26 26  
27 27  {{info}}Themes are indepedent of skins. However currently only the new Colibri skin uses them. Future skins will be made to use Color Themes. In addition, the Class/Object editor has been modified to use the selected color theme.{{/info}}
28 28  
29 -==== New Title handling ====
29 +==== Other UI improvements ====
30 30  
31 -The document title is now used as the top level header of pages. If no title is specified then it's extracted from the content of the page automatically.
31 +* Make section editing work for any section level. You can configure it using the new property ##xwiki.section.depth## in ##xwiki.cfg## file
32 +* Change button order in preview mode
33 +* Make all skins display the document title as the top level header and ensure there's no duplicate titles displayed.
32 32  
33 -This change has been done to all skins: Albatross, Toucan and Colibri.
35 +{{warning}}Not all the pages has been converted to new title handling. It will be fixed during the 2.0.x branch life (hopefully for 2.0.1).{{/warning}}
34 34  
35 -{{warning}}In order not to break existing content we've introduced a title compatibility flag (##xwiki.title.compatibility## in ##xwiki.cfg##) which when active will remove title duplication if your document has a title and a top level header inside the content with the same name. If you upgrade make sure you modify your ##xwiki.cfg## to use that compatibility flag.{{/warning}}
36 -
37 -{{info}}We recommend that you modify your pages to **always** use a title from now on{{/info}}
38 -
39 -==== New Search Interface ====
40 -
41 -The default search page UI has been improved to be easier to understand and use.
42 -
43 -[[image:[email protected]||width="600"]]
44 -
45 -==== New Tag Cloud Panel ====
46 -
47 -A panel containing the tag cloud is now provided by default and can be used like any other panel.
48 -
49 -[[image:[email protected]]]
50 -
51 -==== General UI improvements ====
52 -
53 -* The top level menu has been refactored in the Colibri skin:
54 -** More consistency
55 -** Addition of a Create action to create page, space and import office documents
56 -** Added watch/unwatch wiki action
57 -* The Administration Import page now allows uploading several XARs at once
58 -* Document footer now allows adding Tags
59 -* Button order in preview mode has been modified for improved usability
60 -* Reorganized editor buttons to be more intuitive and less prone to erros
61 -* Section editing now works for any section level. You can configure it using the new property ##xwiki.section.depth## in ##xwiki.cfg## file. By default sections level 1 and 2 can be edited.
62 -* Space Index, Document Index and Orphaned Page now use the generic Livetable
63 -* "History" tab gas been removed from the right panel in edit mode
64 -* Improved the Group creation form
37 +* Space Index, Document Index and Orphaned Page now use generic livetable tools
38 +* Remove "History" from the edit modes
39 +* TOC macro now starts at first level by default
40 +* Several IE6/7 bugfixes
41 +* Improve group creation form
42 +* Reorganize editor button
65 65  * Diff UI improvement
66 -* Improved the Rename form
44 +* Improve the Rename form
67 67  * Nicer pagination of the document history
68 68  * Display a friendly message instead of an error when clicking on History after having created a new page
69 69  * The "Rights editor help" panels has been removed
48 +* Improve Import administration section
70 70  * Improved document footer section
71 71  * Improved tag display and editing
72 -* Several IE6/7 bugfixes
73 -* TOC macro now starts at first level by default
74 74  
75 75  === 2 WYSIWYG Improvements ===
76 76  
77 77  See [[WYSIWYG documentation>>platform:Features.WysiwygEditor]] for more details.
78 78  
79 -==== Macro improvements ====
56 +* Upgrade to [[GWT 1.7.0>>http://code.google.com/webtoolkit/releases/release-notes-1.7.0.html#Release_Notes_Current]]
57 +* Faster navigation for image and link insertion
58 +* Add internationalization support
59 +* Improve UX in wysiwyg dialogs / wizards: navigation, error reporting, forms, etc
80 80  
81 -* User can now double click on a macro to edit it and double click in the list of macro to insert it.
82 -* Macro names are now displayed instead of their internal IDs.
83 -* Macros are now categorized and it's possible to override macro category through configuration:(((
84 -image:[email protected]
85 -)))
86 -* The Insert Macro dialog box now has a live search for easily finding macros:(((
87 -image:[email protected]
88 -)))
61 +==== Double click to edit a macro ====
89 89  
90 -==== Other improvements ====
63 +User can now double click on a macro to edit it and double click in the list of macro to insert it.
91 91  
92 -* Added IE8 support (thanks to the [[GWT 1.7.0>>http://code.google.com/webtoolkit/releases/release-notes-1.7.0.html#Release_Notes_Current]] upgrade)
93 -* Faster navigation for image and link insertion with tabs provided for easily selecting recently viewed pages and the addition of a search box
94 -* Added internationalization support and French translations
95 -* Dialog boxes in the WYSIWYG editor have been aligned and are now following XWiki's usability guidelines
65 +==== Nicer macro names in the list of macros ====
96 96  
97 -=== 3 Macros ===
67 +WYSIWYG does not expose macro identifier anymore but human readable names provided by the different macros.
98 98  
99 -* New [[Formula macro>>code:Macros.FormulaMacro]] for displaying Mathematical formulas. For example:(((
100 -[[image:code:[email protected]]]
101 -)))
102 -* New [[Info, Warning and Error macros>>code:Macros.MessageMacro]].
103 -* New [[Chart macro>>code:Macros.ChartMacro20]].
104 -* New [[Ruby macro>>code:Macros.RubyMacro]] to use JRuby for adding scripts into wiki pages (same binding as for the existing Velocity and Groovy macros).
105 -* New [[Python macro>>code:Macros.PythonMacro]] to use Jython for adding scripts into wiki pages (same binding as for the existing Velocity and Groovy macros).
106 -* New [[Footnote macro documentation>>code:Macros.Footnote20Macro]]. For example:(((
107 -[[image:code:[email protected]]]
108 -)))
109 -* Added ability to transform any wiki content into a Macro. See the [[Wiki Macro tutorial>>platform:DevGuide.WikiMacroTutorial]] for more details.
110 -* Improvements to the [[Script macros>>code:Macros.ScriptMacro]] (groovy, velocity, python, ruby)
111 -** It's now possible to add JARs attached to a page to the Script Macro class loader.
112 -** All the script macros in the same rendering process (a document and it's included documents) share the same class loader. For example this makes possible to declare a Groovy class in a document and use it in other documents which includes it.
113 -** It's now possible to not parse velocity macro content for wiki syntax by using the ##wiki="false"## parameter.
69 +==== Macros categories ====
114 114  
71 +Each macro can now be added in a default category the macro author thinks appropriate. It's also possible to overwrite the macro category with configuration.
72 +
73 +The macros categories are mainly used in WYSIWYG to make it easier to find the macros to use.
74 +
75 +image:[email protected]
76 +image:[email protected]
77 +
115 115  === Rendering 2.0 ===
116 116  
117 117  * New Section editing
... ... @@ -127,7 +127,54 @@
127 127  
128 128  See [[URL parsing documentation>>platform:AdminGuide.URL resolution#HoutputSyntaxandoutputSyntaxVersion]].
129 129  
93 +==== New Wiki rendering 2.0 macros ====
130 130  
95 +See [[Wiki macros documentation>>platform:DevGuide.WikiMacroTutorial]] for more details.
96 +
97 +==== New Tag Cloud Panel ====
98 +
99 +A panels containing the tag cloud is now provided by default and can be used like any other panel.
100 +
101 +image:[email protected]
102 +
103 +==== New Search Interface ====
104 +
105 +The default search page UI has been improved to be easier to understand and use.
106 +
107 +[[image:[email protected]||width="600"]]
108 +
109 +==== New info, warning and error macros ====
110 +
111 +See [[Message macro documentation>>code:Macros.MessageMacro]] for more details.
112 +
113 +==== New Chart macro for XWiki 2.0 syntax ====
114 +
115 +See [[Chart macro documentation>>code:Macros.ChartMacro20]].
116 +
117 +==== Script macro improvements ====
118 +
119 +See the [[Script Macro documentation>>code:Macros.ScriptMacro]] for more details.
120 +
121 +* It's now possible to add JARs attached to a page to the Script Macro class loader.
122 +* All the script macros in the same rendering process (a document and it's included documents) share the same class loader. For example this makes possible to declare a groovy class in a document and use it in other documents which includes it.
123 +* It's now possible to not parse velocity macro content for wiki syntax by using the wiki="false" parameter.
124 +
125 +==== New Python macro ====
126 +
127 +See [[code:Macros.PythonMacro]] for more details.
128 +
129 +==== Footnote macro ====
130 +
131 +See [[Footnote macro documentation>>code:Macros.Footnote20Macro]].
132 +
133 +[[image:code:[email protected]]]
134 +
135 +==== Formula macro ====
136 +
137 +Ability to render Mathematical Formulas using the ~{~{formula}} macro (see [[documentation page>>code:Macros.FormulaMacro]]).
138 +
139 +You can check for examples on the [[Wikipedia Math Markup page>>http://en.wikipedia.org/wiki/Math_markup]].
140 +
131 131  ==== Smaller XHTML output ====
132 132  
133 133  We introduced a light XHTML renderer which avoid having all extra datas needed by the WYSIWYG. You will not get any weird XHTML comment anymore in the rendered page.

Get Connected