[xwiki-devs] Support for Google Gadgets in pages in panels
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 ? Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
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
Hi, On Mon, Feb 23, 2009 at 2:48 PM, Vincent Massol <vincent@massol.net> wrote:
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
I agree with Vincent here, it's too late and not polished enough to be included in XE 1.8. We can add it at a later stage once it's been taken over by someone if we deem it important for XE's roadmap. Otherwise keeping it as an application looks fine to me for the time being. Guillaume _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -- Guillaume Lerouge Product Manager - XWiki Skype ID : wikibc http://guillaumelerouge.com/
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
On Feb 23, 2009, at 4:40 PM, Ludovic Dubost wrote:
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 ?
I don't like too much the fact that we'd be tying Gadgets in the core. I don't think this should be the case. Jerome is going to commit support for Velocity macros in the new rendering in 1.9M1 so maybe this is the chance to use it and thus have the macro defined in the gadget application? Note: I haven't had time to look at the code you wrote so maybe this is not possible for some reason. Thanks -Vincent
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
The tie is only in the displaypanel macro. It allows to make a panel that is made of a gadget. Currently the displaypanel is part of the core altough it's really XE Ludovic Vincent Massol a écrit :
On Feb 23, 2009, at 4:40 PM, Ludovic Dubost wrote:
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 ?
I don't like too much the fact that we'd be tying Gadgets in the core. I don't think this should be the case. Jerome is going to commit support for Velocity macros in the new rendering in 1.9M1 so maybe this is the chance to use it and thus have the macro defined in the gadget application?
Note: I haven't had time to look at the code you wrote so maybe this is not possible for some reason.
Thanks -Vincent
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 devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
-- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost
On Mon, Feb 23, 2009 at 6:43 AM, Ludovic Dubost <ludovic@xwiki.com> wrote:
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
Any chance this can get added to 2.0? It was not added in 1.8, nor 1.9 (As far as i can tell): Vincent Massol:
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 :)
Niels http://nielsmayer.com PS: when will related functionality, such as openid, opensocial or other foaf-enabling, be available for integration?
Hi Niels, On Aug 4, 2009, at 6:23 AM, Niels Mayer wrote:
On Mon, Feb 23, 2009 at 6:43 AM, Ludovic Dubost <ludovic@xwiki.com> wrote:
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
Any chance this can get added to 2.0? It was not added in 1.8, nor 1.9 (As far as i can tell):
The work done by Ludovic was a proof of concept only. However note that we have a GSOC going on for this: - http://gsoc.myxwiki.org/ - http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/GoogleGadgetsandOpenS... I don't have the exact status of the project as of now (AnaMaria can you give a status?) but it certainly won't be ready for 2.0. The ability to include it in a future release will depend on the quality of the work done (the quality of the design, the following of xwiki dev best practices, etc). At this point it's hard to tell if and when it could be included.
Vincent Massol:
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 :)
Niels http://nielsmayer.com
PS: when will related functionality, such as openid, opensocial or other foaf-enabling, be available for integration?
- re opensocial see above - re openid, when someone (could be you maybe?) has the time to work on http://jira.xwiki.org/jira/browse/XWIKI-2588 & http://jira.xwiki.org/jira/browse/XWIKI-2630 . Right now it's not on the roadmap defined by current xwiki committers but anyone interested can provide patches and provided they're good they'll be applied quickly. Thanks -Vincent
participants (5)
-
Guillaume Lerouge -
Ludovic Dubost -
Ludovic Dubost -
Niels Mayer -
Vincent Massol