Last modified by Thomas Mortagne on 2023/10/13

From version 34.1
edited by Vincent Massol
on 2009/09/24
Change comment: There is no comment for this version
To version 31.1
edited by Thomas Mortagne
on 2009/09/23
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.VincentMassol
1 +XWiki.ThomasMortagne
Content
... ... @@ -4,38 +4,102 @@
4 4  
5 5  == New and Noteworthy (since XWiki Enterprise 1.9.3) ==
6 6  
7 -=== 1 User Interface ===
7 +* New Colibri skin
8 +* Many UI improvements
9 +* Many WYSIWYG improvements
10 +* Many rendering improvements
11 +* New events distribution and clustering support
12 +* Various scripting improvements
13 +** Python support
14 +** Classpath charing between script macros
15 +* Big refactor of the Watchlist
8 8  
9 -==== Colibri skin ====
17 +=== Colibri skin ===
10 10  
11 -XWiki 2.0 introduces a new, lightweight, easily customizable skin. The main goal of the Colibri skin is to provide the proper support for fast and easy modifications of the look and feel of the wiki.
12 -
13 -[[image:code:[email protected]]]
14 -
15 15  See [[Colibri skin documentation>>code:Skins.ColibriSkin]] for more details.
16 16  
17 -==== Color Themes ====
21 +XWiki 2.0 introduces a new, lightweight, easily customizable skin. The main goal of the Colibri skin is to provide the proper support for fast and easy modifications of the look and feel of the wiki. The Colibri skin colors and decorative images are defined in ColorTheme objects inside Wiki documents, that can be changed directly in the web interface.
18 18  
19 -[[Color Themes>>code:Skins.ColibriSkin]] is an easy way to modify colors for your wiki:
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):
25 +Several predefined themes are bundled with XE:
24 24  
25 25  [[image:code:[email protected]]]
26 26  
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}}
29 +=== General UI ===
28 28  
29 -==== New Title handling ====
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.
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.
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}}
32 32  
33 -This change has been done to all skins: Albatross, Toucan and Colibri.
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
43 +* Diff UI improvement
44 +* Improve the Rename form
45 +* Nicer pagination of the document history
46 +* Display a friendly message instead of an error when clicking on History after having created a new page
47 +* The "Rights editor help" panels has been removed
48 +* Improve Import administration section
49 +* Improved document footer section
50 +* Improved tag display and editing
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}}
52 +=== WYSIWYG ===
36 36  
37 -{{info}}We recommend that you modify your pages to **always** use a title from now on{{/info}}
54 +See [[WYSIWYG documentation>>platform:Features.WysiwygEditor]] for more details.
38 38  
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
60 +
61 +==== Double click to edit a macro ====
62 +
63 +User can now double click on a macro to edit it and double click in the list of macro to insert it.
64 +
65 +==== Nicer macro names in the list of macros ====
66 +
67 +WYSIWYG does not expose macro identifier anymore but human readable names provided by the different macros.
68 +
69 +==== Macros categories ====
70 +
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 +
78 +=== Rendering 2.0 ===
79 +
80 +* New Section editing
81 +* Allow default document syntax to be specified in User profile configuration
82 +
83 +{{warning}}
84 +Not all the pages has been converted to new xwiki/2.0 syntax. It will be fixed during the 2.0.x branch life (hopefully for 2.0.1).
85 +{{/warning}}
86 +
87 +==== Output syntax parameter ====
88 +
89 +It's now possible to decide which renderer to use to print the document content. For example if you want to generate dome JSON page you can use "?outputSyntax=plain&xpage=plain" to make sure only the content is printed and there is no html syntax printed, just a plain text of what exactly was generated by a velocity macro (without macro markers html comments etc.)
90 +
91 +See [[URL parsing documentation>>platform:AdminGuide.URL resolution#HoutputSyntaxandoutputSyntaxVersion]].
92 +
93 +==== New Wiki rendering 2.0 macros ====
94 +
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 +
39 39  ==== New Search Interface ====
40 40  
41 41  The default search page UI has been improved to be easier to understand and use.
... ... @@ -42,95 +42,59 @@
42 42  
43 43  [[image:[email protected]||width="600"]]
44 44  
45 -==== New Tag Cloud Panel ====
109 +==== New info, warning and error macros ====
46 46  
47 -A panel containing the tag cloud is now provided by default and can be used like any other panel.
111 +See [[Message macro documentation>>code:Macros.MessageMacro]] for more details.
48 48  
49 -[[image:ReleaseNotesXWikiEnterprise20M1@tagcloudpanel.png]]
113 +==== New Chart macro for XWiki 2.0 syntax ====
50 50  
51 -==== General UI improvements ====
115 +See [[Chart macro documentation>>code:Macros.ChartMacro20]].
52 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 -* The Administration Import page now allows uploading several XARs at once
57 -* Document footer now allows adding Tags
58 -* Button order in preview mode has been modified for improved usability
59 -* Reorganized editor buttons to be more intuitive and less prone to erros
60 -* 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.
61 -* Space Index, Document Index and Orphaned Page now use the generic Livetable
62 -* "History" tab gas been removed from the right panel in edit mode
63 -* Improved the Group creation form
64 -* Diff UI improvement
65 -* Improved the Rename form
66 -* Nicer pagination of the document history
67 -* Display a friendly message instead of an error when clicking on History after having created a new page
68 -* The "Rights editor help" panels has been removed
69 -* Improved document footer section
70 -* Improved tag display and editing
71 -* Several IE6/7 bugfixes
72 -* Documents created internally for XWiki's needs are now created under the ##superadmin## user and are not visible to Simple Users by default (Advanced users and Admin see them though)
117 +==== Script macro improvements ====
73 73  
74 -=== 2 WYSIWYG ===
119 +See the [[Script Macro documentation>>code:Macros.ScriptMacro]] for more details.
75 75  
76 -See [[WYSIWYG documentation>>platform:Features.WysiwygEditor]] for more details.
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.
77 77  
78 -==== Macro improvements ====
125 +==== New Python macro ====
79 79  
80 -* User can now double click on a macro to edit it and double click in the list of macro to insert it.
81 -* Macro names are now displayed instead of their internal IDs.
82 -* Macros are now categorized and it's possible to override macro category through configuration:(((
83 -image:[email protected]
84 -)))
85 -* The Insert Macro dialog box now has a live search for easily finding macros:(((
86 -image:[email protected]
87 -)))
127 +See [[code:Macros.PythonMacro]] for more details.
88 88  
89 -==== Other improvements ====
129 +==== Footnote macro ====
90 90  
91 -* 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)
92 -* Faster navigation for image and link insertion with tabs provided for easily selecting recently viewed pages and the addition of a search box
93 -* Added internationalization support and French translations
94 -* Dialog boxes in the WYSIWYG editor have been aligned and are now following XWiki's usability guidelines
131 +See [[Footnote macro documentation>>code:Macros.Footnote20Macro]].
95 95  
96 -=== 3 Macros ===
97 -
98 -* New [[Formula macro>>code:Macros.FormulaMacro]] for displaying Mathematical formulas. For example:(((
99 -[[image:code:[email protected]]]
100 -)))
101 -* New [[Info, Warning and Error macros>>code:Macros.MessageMacro]].
102 -* New [[Chart macro>>code:Macros.ChartMacro20]].
103 -* 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).
104 -* 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).
105 -* New [[Footnote macro documentation>>code:Macros.Footnote20Macro]]. For example:(((
106 106  [[image:code:[email protected]]]
107 -)))
108 -* Added ability to transform any wiki content into a Macro. See the [[Wiki Macro tutorial>>platform:DevGuide.WikiMacroTutorial]] for more details.
109 -* Improvements to the [[Script macros>>code:Macros.ScriptMacro]] (groovy, velocity, python, ruby)
110 -** It's now possible to add JARs attached to a page to the Script Macro class loader.
111 -** 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.
112 -** It's now possible to not parse velocity macro content for wiki syntax by using the ##wiki="false"## parameter.
113 -* The Table Of Content macro now starts at the first level by default (it used to start at the second level by default).
114 114  
115 -=== 4 Rendering ===
135 +==== Formula macro ====
116 116  
117 -==== General improvements ====
137 +Ability to render Mathematical Formulas using the ~{~{formula}} macro (see [[documentation page>>code:Macros.FormulaMacro]]).
118 118  
119 -* Section editing is now supported with XWiki Syntax 2.0
120 -* Definition lists now support parameters
121 -* Document syntax to use for new pages by default can now be configured on a per user level in user profiles
122 -* Velocity Tools and Velocity configuration can now be specified in the ##xwiki.properties## configuration file
139 +You can check for examples on the [[Wikipedia Math Markup page>>http://en.wikipedia.org/wiki/Math_markup]].
123 123  
124 -{{warning}}Not all the pages from the default XAR have been converted to the XWiki Syntax 2.0 yet.{{/warning}}
141 +==== Smaller XHTML output ====
125 125  
126 -==== Output syntax parameter ====
143 +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.
127 127  
128 -It's now possible to decide which renderer to use to print the document content. For example if you want to generate a JSON page you can use "?outputSyntax=plain&xpage=plain" to make sure only the content is printed and there is no HTML syntax printed, just a plain text of what exactly was generated by a velocity macro (without macro markers HTML comments etc.)
145 +==== Renderers are now real components ====
129 129  
130 -See [[URL parsing documentation>>platform:AdminGuide.URL resolution#HoutputSyntaxandoutputSyntaxVersion]].
147 +The same way it's possible to add any parser it's now possible to add any renderer for a specific output simply by registering it as a component.
131 131  
132 -=== 5 Watchlist ===
149 +See [[code:Modules.RenderingModule]] for more details.
133 133  
151 +==== New plain text parser ====
152 +
153 +Plain text parser make possible to put in a page some plain text to render it exactly as it. The syntax name of plain text renderer is ##plain/1.0##, you can enable it in xwiki.cfg.
154 +
155 +=== Scheduler improvements ===
156 +
157 +* Allow to manually trigger a job (execute it once)
158 +* Upgrade to Quartz 1.6.5
159 +
160 +=== Watchlist ===
161 +
134 134  * Add watch/unwatch wiki in the Watch menu
135 135  * Improve notification email readability by displaying icons for objects, classes and properties
136 136  * Watch List support registering for user activity
... ... @@ -137,61 +137,60 @@
137 137  * Put document metadata modifications in diffs
138 138  * Make the watchlist work across multiple wikis
139 139  * Put links to pages in email notifications
168 +* Use activitystream feed building feature to generate watchlist RSS feed
140 140  * In virtual mode allow each wiki to have its own watchlist email template document
170 +* Big speed improvement by refactoring the watchlist based on activity stream plugin
141 141  * Add support for class and object diff in the mails
142 142  * Add support for full wiki watching
143 143  * Allow to create watchlist notifications for any interval of time
144 144  * Mails design improvement
145 145  
146 -=== 6 Clustering ===
176 +=== New Activity stream ===
147 147  
148 -It's now possible to make different instances of XWiki or other programs shares events.
178 +* Provide a way to delete events after a configurable amount of time
179 +* Allow to store all activity events in the main wiki in virtual mode
149 149  
150 -The main use cases for this are:
151 -- clustering
152 -- external monitoring of XWiki
181 +=== New events for XWiki startup/shutdown ===
153 153  
154 -This release include documents events support for code using new Observation Manager and remote events support in document cache so that's it's possible to do basic clustering already. The old code using old notification system will be upgraded during the RC process before the final 2.0 version and support will be added for other types of events. Note that Remote Observation Manager already support any kind of fully Serializable events.
183 +It's now possible for a component or a plugin to register to startup or shutdown events. It's very useful when some plugin need to start and stop an external service.
155 155  
156 -=== 7 Performance ===
185 +=== Velocity tools and Velocity properties can be easily changed ===
157 157  
158 -* We have introduced a lighter XHTML renderer which avoid having all extra datas needed by the WYSIWYG, thus reducing a lot the size of rendered pages in view mode.
159 -* JS and CSS files are now compressed.
160 -* The watchlist feature now supports multi wiki and has improved performances to prevent farm wikis to be stuck when sending all notifications for all wikis (this is done by using the new Activity Stream feature).
187 +See ##velocity.tools## and ##velocity.properties## parameters in xwiki.properties.
161 161  
162 -=== 8 Changes for Developers ===
189 +=== Component Manager improvements ===
163 163  
164 -* Renderers are now real components. The same way it's possible to add any parser it's now possible to add any renderer for a specific output simply by registering it as a component. See [[code:Modules.RenderingModule]] for more details.
165 -* New plain text parser. Pain text parser make possible to put in a page some plain text to render it exactly as it. The syntax name of plain text renderer is ##plain/1.0##, you can enable it in ##xwiki.cfg##.
166 -* The WYSIWYG editor menus are now more easily configured since it nows reads the following XWikiPreferences properties:
167 -** ##wysiwyg.plugins## (the list of plugins to load)
168 -** ##wysiwyg.menu## (the top menu entries)
169 -** ##wysiwyg.toolbar## (the list of features to place on the tool bar)
170 -* New color picker widget
171 -* New Velocity RegexTool (usable using the ##$regextool## variable in Velocity)
172 -* Added new Activity Stream plugin to record events happening in the system with the following features:
173 -** Applications can create their own activity streams to record custom events
174 -** Provide a way to delete events after a configurable amount of time
175 -** Allow to store all activity events in the main wiki in multi wiki mode
176 -* New events for XWiki startup/shutdown. It's now possible for a component or a plugin to register to startup or shutdown events. It's very useful when some plugin need to start and stop an external service.
177 -* Component Manager improvements
178 -** Added way to programmatically provide the component instance when register it
179 -** Added way to programmatically unregister component
180 -* New [[Properties module>>code:Modules.PropertiesModule]] that offers:
181 -** Java bean populating support
182 -** Java type conversion support
183 -** Java bean validation support
184 -* Upgraded several libraries:
185 -** Upgraded to Quartz 1.6.5
186 -** Upgraded to GWT 1.7
187 -** Upgraded to Jython 2.5.1 RC3
188 -** Upgraded to Smart GWT 1.2
189 -** Upgraded to Prototype 1.6.1
191 +* Added way to programmatically provide the component instance when register it
192 +* Added way to programmatically unregister component
190 190  
191 -=== 9 Others ===
194 +=== New xwiki-properties module ===
192 192  
193 -* The Scheduler now allows to manually trigger a job (execute it once)
196 +See [[Properties module documentation>>code:Modules.PropertiesModule]].
194 194  
198 +* Java bean populating support
199 +* Java type conversion support
200 +* Java bean validation support
201 +
202 +Among other things this mean the following changes for the 2.0 macros:
203 +
204 +* Any case is supported for macros parameters names
205 +* Public fields are now supported (not only getters and setters)
206 +* Java macro parameters bean is validated agains JSR 303 (See )
207 +* Macro properties java bean can implements RawProperties to get custom non converted parameters
208 +* You can add support for any type conversion by implementing Converter component
209 +* Any Enum conversion is supported (no need to register each Enum subclass against ConvertUtils anymore)
210 +* Support for Color conversion
211 +
212 +=== Remote Observation Manager and clustering ===
213 +
214 +It's now possible to make different instances of XWiki or other programs shares events.
215 +
216 +The main use cases for this are:
217 +- clustering
218 +- external monitoring of XWiki
219 +
220 +This release include documents events support for code using new Observation Manager and remote events support in document cache so that's it's possible to do basic clustering already. The old code using old notification system will be upgraded during the RC process before the final 2.0 version and support will be added for other types of events. Note that Remote Observation Manager already support any kind of fully Serializable events.
221 +
195 195  == Known issues ==
196 196  
197 197  * [[Bugs we know about>>http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&&type=1&pid=10010&resolution=-1&sorter/field=updated&sorter/order=DESC]]

Get Connected