Re: [xwiki-devs] [VOTE] Creation of xwiki-platform-uiextension module

Hi Vincent, On Thu, Nov 3, 2011 at 12:56 PM, Vincent Massol <vincent(a)massol.net> wrote: So how would this work exactly? Each UI (skin, xwiki bundled application, user application, etc.) defines these extension points that any other application can contribute to by using the "type" field in an XWiki.UIExtensionClass instance? This would, of course, mean a great deal of rewriting, but once done, it would be a good investment. Depending on the specifics of the extension point, the content gets treated differently? Also, I`m assuming this will generally be velocity/wiki syntax, right? Another thing that might be useful (maybe in future iterations) would be some kind of parameters that the extension could supply to its hook. In your particular use case, a tab extension could say to the AllDocs page that it wants its content to be loaded asynchronously, when the tab is selected. Another case would be a menu extension that wants the menu item to open in a new window when clicked or that wants to be placed before entry X or after entry Y. Etc. The only downside I see is the performance penalty once everything starts being extra extensible, but maybe using some smart caching (which you already mentioned something about) we can limit the damage. The extension content still needs to be evaluated every time (unless maybe otherwise stated by the extension itself), but at least the list of extensions can be easily cached. +1 if I understood it correctly. Thanks, Eduard