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 34.1
edited by Vincent Massol
on 2009/09/24
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  == New and Noteworthy (since XWiki Enterprise 1.9.3) ==
6 6  
7 -=== 1 UI Improvements ===
7 +=== 1 User Interface ===
8 8  
9 9  ==== Colibri skin ====
10 10  
... ... @@ -53,7 +53,6 @@
53 53  * The top level menu has been refactored in the Colibri skin:
54 54  ** More consistency
55 55  ** Addition of a Create action to create page, space and import office documents
56 -** Added watch/unwatch wiki action
57 57  * The Administration Import page now allows uploading several XARs at once
58 58  * Document footer now allows adding Tags
59 59  * Button order in preview mode has been modified for improved usability
... ... @@ -70,9 +70,9 @@
70 70  * Improved document footer section
71 71  * Improved tag display and editing
72 72  * Several IE6/7 bugfixes
73 -* TOC macro now starts at first level by default
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)
74 74  
75 -=== 2 WYSIWYG Improvements ===
74 +=== 2 WYSIWYG ===
76 76  
77 77  See [[WYSIWYG documentation>>platform:Features.WysiwygEditor]] for more details.
78 78  
... ... @@ -111,44 +111,27 @@
111 111  ** It's now possible to add JARs attached to a page to the Script Macro class loader.
112 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 113  ** 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 -=== Rendering 2.0 ===
115 +=== 4 Rendering ===
116 116  
117 -* New Section editing
118 -* Allow default document syntax to be specified in User profile configuration
117 +==== General improvements ====
119 119  
120 -{{warning}}
121 -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).
122 -{{/warning}}
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
123 123  
124 +{{warning}}Not all the pages from the default XAR have been converted to the XWiki Syntax 2.0 yet.{{/warning}}
125 +
124 124  ==== Output syntax parameter ====
125 125  
126 -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.)
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.)
127 127  
128 128  See [[URL parsing documentation>>platform:AdminGuide.URL resolution#HoutputSyntaxandoutputSyntaxVersion]].
129 129  
132 +=== 5 Watchlist ===
130 130  
131 -==== Smaller XHTML output ====
132 -
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.
134 -
135 -==== Renderers are now real components ====
136 -
137 -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.
138 -
139 -See [[code:Modules.RenderingModule]] for more details.
140 -
141 -==== New plain text parser ====
142 -
143 -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.
144 -
145 -=== Scheduler improvements ===
146 -
147 -* Allow to manually trigger a job (execute it once)
148 -* Upgrade to Quartz 1.6.5
149 -
150 -=== Watchlist ===
151 -
152 152  * Add watch/unwatch wiki in the Watch menu
153 153  * Improve notification email readability by displaying icons for objects, classes and properties
154 154  * Watch List support registering for user activity
... ... @@ -155,60 +155,61 @@
155 155  * Put document metadata modifications in diffs
156 156  * Make the watchlist work across multiple wikis
157 157  * Put links to pages in email notifications
158 -* Use activitystream feed building feature to generate watchlist RSS feed
159 159  * In virtual mode allow each wiki to have its own watchlist email template document
160 -* Big speed improvement by refactoring the watchlist based on activity stream plugin
161 161  * Add support for class and object diff in the mails
162 162  * Add support for full wiki watching
163 163  * Allow to create watchlist notifications for any interval of time
164 164  * Mails design improvement
165 165  
166 -=== New Activity stream ===
146 +=== 6 Clustering ===
167 167  
168 -* Provide a way to delete events after a configurable amount of time
169 -* Allow to store all activity events in the main wiki in virtual mode
148 +It's now possible to make different instances of XWiki or other programs shares events.
170 170  
171 -=== New events for XWiki startup/shutdown ===
150 +The main use cases for this are:
151 +- clustering
152 +- external monitoring of XWiki
172 172  
173 -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.
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.
174 174  
175 -=== Velocity tools and Velocity properties can be easily changed ===
156 +=== 7 Performance ===
176 176  
177 -See ##velocity.tools## and ##velocity.properties## parameters in xwiki.properties.
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).
178 178  
179 -=== Component Manager improvements ===
162 +=== 8 Changes for Developers ===
180 180  
181 -* Added way to programmatically provide the component instance when register it
182 -* Added way to programmatically unregister component
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
183 183  
184 -=== New xwiki-properties module ===
191 +=== 9 Others ===
185 185  
186 -See [[Properties module documentation>>code:Modules.PropertiesModule]].
193 +* The Scheduler now allows to manually trigger a job (execute it once)
187 187  
188 -* Java bean populating support
189 -* Java type conversion support
190 -* Java bean validation support
191 -
192 -Among other things this mean the following changes for the 2.0 macros:
193 -
194 -* Any case is supported for macros parameters names
195 -* Public fields are now supported (not only getters and setters)
196 -* Java macro parameters bean is validated agains JSR 303 (See )
197 -* Macro properties java bean can implements RawProperties to get custom non converted parameters
198 -* You can add support for any type conversion by implementing Converter component
199 -* Any Enum conversion is supported (no need to register each Enum subclass against ConvertUtils anymore)
200 -* Support for Color conversion
201 -
202 -=== Remote Observation Manager and clustering ===
203 -
204 -It's now possible to make different instances of XWiki or other programs shares events.
205 -
206 -The main use cases for this are:
207 -- clustering
208 -- external monitoring of XWiki
209 -
210 -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.
211 -
212 212  == Known issues ==
213 213  
214 214  * [[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