You can look at the change here http://incubator.myxwiki.org/xwiki/bin/view/Gadgets/Macros?viewer=code
Ludovic Ludovic Dubost a écrit : > I understand. Now there is one thing it would be great to include in XE, > it's the 2 macros > > - the change in #displaypanel > - the #displaygadget > > The displaypanel macro change can be reviewed. It only tests for the > panel to exist in PanelClass > If the param exist it calls displaygadget, if not it continues the > normal display panel > > Having it commited would make it much easier to deploy the gadget > application > > WDYT ? > > Ludovic > > Vincent Massol a écrit : > >> On Feb 23, 2009, at 2:43 PM, Ludovic Dubost wrote: >> >> >> >>> Hi devs, >>> >>> I've implemented support for Google Gadgets for pages and for panels. >>> >>> http://incubator.myxwiki.org/xwiki/bin/view/Gadgets/ >>> >>> It is possible to browse the Google Gadget Directory and select a >>> gadget, set it's parameters and either: >>> >>> - insert a call to a gadget macro in a wiki page >>> - create a panel with this gadget >>> >>> >>> It's basically working, except for a few Gadget translations issues >>> in the gadget settings page (for some gadgets). >>> To integrate in XE this requires: >>> >>> - a slight modification to the PanelClass and the displaypanel macro >>> (to support a gadgeturl and gadgetprefs field) >>> - a few pages including a Gadget Groovy page (which requires >>> programming rights) >>> >>> I think we should transform the Gadget Groovy to a plugin to avoid >>> the need for programming rights. >>> >>> We can also from there create a special page type to make a display >>> of gadgets or panels like iGoogle or NetVibes. >>> It would store gadgets or panel lists in a special class with some >>> position parameters. And with some JS we can reposition the panels >>> or gadgets and save the config in the wiki page. >>> This would be an easy way to make some portal like experience in the >>> wiki. >>> >>> Who wants to takeover this from the dev team ? Do you think we can >>> have this in 1.8 ? >>> >>> >> My opinion is no for XE 1.8. Too late, too risky, not ready enough in >> term of quality, everyone busy on trying to release 1.8 in time :) >> >> However since it's an application it's not related to the lifecycle of >> XE and can be released independently. So here's what I suggest: >> >> 1) It's put quickly on code.xwiki.org as an app for testing/having fun/ >> trying out >> 2) if someone in the devs community is interested to take over then it >> could be improved and moved to our svn (after a vote) >> 3) I'd release a first version 1.0 without including it in the XE >> distribution just to get feedback, ensure it works fine, make it >> nicer, etc >> 4) We could then release the 1.1 version in XE whenever it's ready. It >> could be in 1.8.1, 1.8.2, 1.9M1, etc >> >> WDYT? >> >> Thanks >> -Vincent >> >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs >> >> >> > > > -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
