[xwiki-devs] Gadgets & Dashboard roadmap

Hi all, I am now restarting the work on the gadgets & dashboard project, documented here http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration (however documentation needs to be slightly revised). What is done already can be summarized as: * gadgets are implemented as macros and there is a script to import google gadgets as xwiki macros, * also, right now, gadgets are implemented as xwiki macros and can be used anywhere just like a regular wiki macro, and any wiki macro can be seen/used as a gadget so **there is no difference between macros and gadgets** . WDYT about this? should we keep it like that? (A) * there is a dashboard macro responsible with layouting a gadgets dashboard, which also provides specific editing features in inline mode (gadgets can be dragged around, toolboxes for gadgets in the top right) * there is a minimal macros directory, where one can see all the existing macros, descriptions, details about the parameters. * there is an PanelMacro macro, that displays an xwiki panel inside a document, which can be used to display xwiki panels as gadgets in a dashboard. The big picture of the roadmap is that we should: 1/ have a fully working dashboard, that is implement add gadget and edit gadget settings 2/ implement the main dashboard (Main.Dashboard) as a dashboard and fill it with the appropriate gadgets by default, and also to add a user specific dashboard ("My dashboard") where each user can configure his/her dashboard, and is available to a user from his / her profile or the user menu 3/ have a nice macros directory where a user can navigate through existing gadgets and add one to a dashboard 4/ have a "dashboard template", integrated with the document templates system to easily allow a user to create a dashboard 5/ also, since the xwiki panels can be seen as gadgets / macros, and can be implemented as such, somewhere in the future a refactoring should be made to integrate the 2 notions 6/ be able to publish the gadgets in the wiki such that other apps can integrate this in their content WDYT about the order above? (B) with the mention that points 5 and 6 could eventually be infinitely postponed. Also, after points 1 and 2 are implemented, the feature could be available with xwiki platform and integrated in XE by default. WDYT? (C) my +1 for (A), (B) and (C). Happy hacking, Anca