Hi team, I talked on Friday with Vincent about how to approach editing of a dashboard, and we rethought the current approach of specifying the gadgets in a dashboard.
Right now, the solution I started to implement is Option 4) in the Dashboard syntax section, http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HOption429Columnmacroforlayouting2Cdashboardextendscolumnmacro , having the gadgets be actual macro calls in wiki syntax in the content of the dashboard macro. This is causing quite some issues on editing, because the wiki syntax of the document needs to be re-generated when the dashboard changes. We detailed another solution, option 5) in the same document http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HOption529Gadgetentriesstoredinobjects2Cdashboardmacroonlypinpointsthepositioninthepage , where gadgets will be specified by objects in the dashboard document, and the dashboard macro call in the page will only mark the point where the objects are read and rendered as a dashboard. Editing should be easier in this case, as the data is more structured than in option 4) (reading and changing object fields). My question here is, does anyone see anything wrong with option 5) ? So far to me it seems a better choice than 4), easier to implement and fixing more problems, and it feels a bit more "semantic" to store the gadgets as structured data, rather than "unstructured" document content. Thanks, Anca _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
