[xwiki-devs] [Discussion] Gadgets in XWiki
Hi devs, Following the implementation of gadgets we'd need to discuss the approach of implementing xwiki as an open social container (also see http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HXWikiasOpenSoc... for the discussion). There are 2 approaches that can be used: Short story: Option A): open social gadgets are imported as xwiki macros (one macro for each imported gadget), the xwiki dashboard works with macros as gadgets, to publish the xwiki macros as gadgets we provide an automatic transformation of xwiki macros in open social gadgets XML definition Option B): dashboard accepts a single macro inside, the {{gadget}} macro, which will specify a reference to the gadget to display (URL to XML if it's open social, page reference if it's xwiki gadget) and the parameters, there would be a mechanism to automatically publish these xwiki pages as gadgets (to be used either by this {{gadget}} macro or by other containers). Long story (also discussing possible approaches for subproblems, and also containing some pros & cons): Option A) See http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalA-Gadg... Option B) See http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalB-Allg... WDYT? Do you think there are other possible approaches that should be added to this list before the vote? What do you think would be more suitable? Some usage scenarios are documented at http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HScenarios . Please, if you feel the list is not complete, contribute your usecases. Thanks, Anca
Hi Anca, +1 for A) I like the fact that this will easily get integrated into the wysiwyg, the fact that it offers more display freedom, better reuse and cleaner syntax. Sorry, I didn't follow your roadmap, but how do you plan to integrate this into the platform? I see the gadgets/directory/dashboard as distinct elements. Are these going to be implemented(to be read 'implemented & released') separately or in one big step? Thanks, Florin Ciubotaru On Wed, Jul 7, 2010 at 7:13 PM, Anca Luca <[email protected]> wrote:
Hi devs,
Following the implementation of gadgets we'd need to discuss the approach of implementing xwiki as an open social container (also see
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HXWikiasOpenSoc... for the discussion). There are 2 approaches that can be used:
Short story: Option A): open social gadgets are imported as xwiki macros (one macro for each imported gadget), the xwiki dashboard works with macros as gadgets, to publish the xwiki macros as gadgets we provide an automatic transformation of xwiki macros in open social gadgets XML definition
Option B): dashboard accepts a single macro inside, the {{gadget}} macro, which will specify a reference to the gadget to display (URL to XML if it's open social, page reference if it's xwiki gadget) and the parameters, there would be a mechanism to automatically publish these xwiki pages as gadgets (to be used either by this {{gadget}} macro or by other containers).
Long story (also discussing possible approaches for subproblems, and also containing some pros & cons):
Option A) See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalA-Gadg...
Option B) See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalB-Allg...
WDYT? Do you think there are other possible approaches that should be added to this list before the vote? What do you think would be more suitable?
Some usage scenarios are documented at http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HScenarios . Please, if you feel the list is not complete, contribute your usecases.
Thanks, Anca
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi Florin, On 07/08/2010 01:41 PM, Florin Ciubotaru wrote:
Hi Anca,
+1 for A)
I like the fact that this will easily get integrated into the wysiwyg
Not that spectacularly easily. The only advantage from the wysiwyg pov is when you'll want to add a gadget in a page, not in a dashboard (because it's not possible to edit the content of a macro in wysiwyg manner). The dashboard will have its own edit UI (very wysiwyg as well), which would be the same for option B as well.
, the fact that it offers more display freedom, better reuse and cleaner syntax.
Sorry, I didn't follow your roadmap, but how do you plan to integrate this into the platform? I see the gadgets/directory/dashboard as distinct elements. Are these going to be implemented(to be read 'implemented& released') separately or in one big step?
In the other mail I was proposing some steps to make it happen, and also the point when it would be ready to be integrated in the platform. Basically once you can build a dashboard and put gadgets in it, it would be available in the platform, and then perfect the interaction with the dashboard (directory, adding stuff, editing properties) and then the 2 default dashboards will be created. So answer is gradually once it's stable it should be in the platform. Thanks, Anca
Thanks, Florin Ciubotaru
On Wed, Jul 7, 2010 at 7:13 PM, Anca Luca<[email protected]> wrote:
Hi devs,
Following the implementation of gadgets we'd need to discuss the approach of implementing xwiki as an open social container (also see
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HXWikiasOpenSoc... for the discussion). There are 2 approaches that can be used:
Short story: Option A): open social gadgets are imported as xwiki macros (one macro for each imported gadget), the xwiki dashboard works with macros as gadgets, to publish the xwiki macros as gadgets we provide an automatic transformation of xwiki macros in open social gadgets XML definition
Option B): dashboard accepts a single macro inside, the {{gadget}} macro, which will specify a reference to the gadget to display (URL to XML if it's open social, page reference if it's xwiki gadget) and the parameters, there would be a mechanism to automatically publish these xwiki pages as gadgets (to be used either by this {{gadget}} macro or by other containers).
Long story (also discussing possible approaches for subproblems, and also containing some pros& cons):
Option A) See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalA-Gadg...
Option B) See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalB-Allg...
WDYT? Do you think there are other possible approaches that should be added to this list before the vote? What do you think would be more suitable?
Some usage scenarios are documented at http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HScenarios . Please, if you feel the list is not complete, contribute your usecases.
Thanks, Anca
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Hi, On Thu, Jul 8, 2010 at 2:46 PM, Anca Luca <[email protected]> wrote:
Hi Florin,
On 07/08/2010 01:41 PM, Florin Ciubotaru wrote:
Hi Anca,
+1 for A)
I like the fact that this will easily get integrated into the wysiwyg
Not that spectacularly easily. The only advantage from the wysiwyg pov is when you'll want to add a gadget in a page, not in a dashboard (because it's not possible to edit the content of a macro in wysiwyg manner). The dashboard will have its own edit UI (very wysiwyg as well), which would be the same for option B as well.
Yes, I was referring to the wysiwyg and the gadgets(imported macros) only.
, the fact that it offers more display freedom, better reuse and cleaner syntax.
Sorry, I didn't follow your roadmap, but how do you plan to integrate this into the platform? I see the gadgets/directory/dashboard as distinct elements. Are these going to be implemented(to be read 'implemented& released') separately or in one big step?
In the other mail I was proposing some steps to make it happen, and also the point when it would be ready to be integrated in the platform. Basically once you can build a dashboard and put gadgets in it, it would be available in the platform, and then perfect the interaction with the dashboard (directory, adding stuff, editing properties) and then the 2 default dashboards will be created.
OK. I was hoping to get the gadgets before the dashboard. Florin Ciubotaru
So answer is gradually once it's stable it should be in the platform.
Thanks, Anca
Thanks, Florin Ciubotaru
On Wed, Jul 7, 2010 at 7:13 PM, Anca Luca<[email protected]> wrote:
Hi devs,
Following the implementation of gadgets we'd need to discuss the approach of implementing xwiki as an open social container (also see
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HXWikiasOpenSoc...
for the discussion). There are 2 approaches that can be used:
Short story: Option A): open social gadgets are imported as xwiki macros (one macro for each imported gadget), the xwiki dashboard works with macros as gadgets, to publish the xwiki macros as gadgets we provide an automatic transformation of xwiki macros in open social gadgets XML definition
Option B): dashboard accepts a single macro inside, the {{gadget}} macro, which will specify a reference to the gadget to display (URL to XML if it's open social, page reference if it's xwiki gadget) and the parameters, there would be a mechanism to automatically publish these xwiki pages as gadgets (to be used either by this {{gadget}} macro or by other containers).
Long story (also discussing possible approaches for subproblems, and also containing some pros& cons):
Option A) See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalA-Gadg...
Option B) See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalB-Allg...
WDYT? Do you think there are other possible approaches that should be added to this list before the vote? What do you think would be more suitable?
Some usage scenarios are documented at http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HScenarios . Please, if you feel the list is not complete, contribute your
usecases.
Thanks, Anca
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 07/08/2010 01:41 PM, Florin Ciubotaru wrote:
Hi Anca,
+1 for A)
I like the fact that this will easily get integrated into the wysiwyg, the fact that it offers more display freedom, better reuse and cleaner syntax.
also, it would not necessarily be cleaner syntax, from one point of view: We need to find a way to specify the gadgets in a dashboard and, if any macro can be used as a gadget, it means that we're gonna find a method to display these macros as gadgets without adding extra params (like title, width, height, position in the dashboard).
Sorry, I didn't follow your roadmap, but how do you plan to integrate this into the platform? I see the gadgets/directory/dashboard as distinct elements. Are these going to be implemented(to be read 'implemented& released') separately or in one big step?
Thanks, Florin Ciubotaru
On Wed, Jul 7, 2010 at 7:13 PM, Anca Luca<[email protected]> wrote:
Hi devs,
Following the implementation of gadgets we'd need to discuss the approach of implementing xwiki as an open social container (also see
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HXWikiasOpenSoc... for the discussion). There are 2 approaches that can be used:
Short story: Option A): open social gadgets are imported as xwiki macros (one macro for each imported gadget), the xwiki dashboard works with macros as gadgets, to publish the xwiki macros as gadgets we provide an automatic transformation of xwiki macros in open social gadgets XML definition
Option B): dashboard accepts a single macro inside, the {{gadget}} macro, which will specify a reference to the gadget to display (URL to XML if it's open social, page reference if it's xwiki gadget) and the parameters, there would be a mechanism to automatically publish these xwiki pages as gadgets (to be used either by this {{gadget}} macro or by other containers).
Long story (also discussing possible approaches for subproblems, and also containing some pros& cons):
Option A) See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalA-Gadg...
Option B) See
http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalB-Allg...
WDYT? Do you think there are other possible approaches that should be added to this list before the vote? What do you think would be more suitable?
Some usage scenarios are documented at http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HScenarios . Please, if you feel the list is not complete, contribute your usecases.
Thanks, Anca
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
On 07/07/2010 07:13 PM, Anca Luca wrote:
Hi devs,
Following the implementation of gadgets we'd need to discuss the approach of implementing xwiki as an open social container (also see http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HXWikiasOpenSoc... for the discussion). There are 2 approaches that can be used:
Short story: Option A): open social gadgets are imported as xwiki macros (one macro for each imported gadget), the xwiki dashboard works with macros as gadgets, to publish the xwiki macros as gadgets we provide an automatic transformation of xwiki macros in open social gadgets XML definition
Option B): dashboard accepts a single macro inside, the {{gadget}} macro, which will specify a reference to the gadget to display (URL to XML if it's open social, page reference if it's xwiki gadget) and the parameters, there would be a mechanism to automatically publish these xwiki pages as gadgets (to be used either by this {{gadget}} macro or by other containers).
Long story (also discussing possible approaches for subproblems, and also containing some pros& cons):
Option A) See http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalA-Gadg...
Option B) See http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalB-Allg...
WDYT? Do you think there are other possible approaches that should be added to this list before the vote? What do you think would be more suitable?
I'm for option A) because: * it's easier to insert a gadget in a wiki page, outside a dashboard ** the list of parameters is known (determined during the import) ** gadgets are wiki macros * it's easier for an admin to control what gadgets are available * seems easier to generate a gadget specification from a wiki macro than from a plain wiki page (e.g. for using wiki macros as gadgets outside XWiki). Besides A) we still need, as Anca said, a macro to draw the window-like decorations when gadgets/macros are displayed inside the dashboard. Thanks, Marius
Some usage scenarios are documented at http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HScenarios . Please, if you feel the list is not complete, contribute your usecases.
Thanks, Anca
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
I'm +1 for A) for the same reasons. On Thu, Jul 8, 2010 at 7:01 PM, Marius Dumitru Florea <[email protected]> wrote:
On 07/07/2010 07:13 PM, Anca Luca wrote:
Hi devs,
Following the implementation of gadgets we'd need to discuss the approach of implementing xwiki as an open social container (also see http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HXWikiasOpenSoc... for the discussion). There are 2 approaches that can be used:
Short story: Option A): open social gadgets are imported as xwiki macros (one macro for each imported gadget), the xwiki dashboard works with macros as gadgets, to publish the xwiki macros as gadgets we provide an automatic transformation of xwiki macros in open social gadgets XML definition
Option B): dashboard accepts a single macro inside, the {{gadget}} macro, which will specify a reference to the gadget to display (URL to XML if it's open social, page reference if it's xwiki gadget) and the parameters, there would be a mechanism to automatically publish these xwiki pages as gadgets (to be used either by this {{gadget}} macro or by other containers).
Long story (also discussing possible approaches for subproblems, and also containing some pros& cons):
Option A) See http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalA-Gadg...
Option B) See http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposalB-Allg...
WDYT? Do you think there are other possible approaches that should be added to this list before the vote? What do you think would be more suitable?
I'm for option A) because:
* it's easier to insert a gadget in a wiki page, outside a dashboard ** the list of parameters is known (determined during the import) ** gadgets are wiki macros * it's easier for an admin to control what gadgets are available * seems easier to generate a gadget specification from a wiki macro than from a plain wiki page (e.g. for using wiki macros as gadgets outside XWiki).
Besides A) we still need, as Anca said, a macro to draw the window-like decorations when gadgets/macros are displayed inside the dashboard.
Thanks, Marius
Some usage scenarios are documented at http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HScenarios . Please, if you feel the list is not complete, contribute your usecases.
Thanks, Anca
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (4)
-
Anca Luca -
Florin Ciubotaru -
Jean-Vincent Drean -
Marius Dumitru Florea