This should go beyond user profiles. Space home pages but any page should be able to be dashboard pages. For these pages we would need a way to make them display as dashboard pages by default. We should also make it easy to make these pages dashboard pages when in the wysiwyg. Like include a "dashboard" macro. I view it like that: 1/ Open a page in wysiwyg 2/ Type some text, include a dashboard macro 3/ Save When in view the dashboard macro renders the dashboard settings saved in the content field of the dashboard macro or in XWiki objects save in the page. It adds JS tools to allow to move and change your gadgets and panels used in your dashboard.

With this method we might not need the xpage=dashboard template, as you could just have an #if in the XWikiUserSheet which displays the dashboard based on URL params. The #if would make a call to the XWiki {{dashboard}} macro Ludovic Anamaria Stoica a écrit : can located Panels) wiki 2.2M1. and Directory In Interface. only and/or -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi, To address Caty's feedback on http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration(than… Caty!): 1. Should Google Gadgets also be able to add on the side menus? (where the Panels currently are) I think users should be able to do this also. If so, it would make sense to also have a Gadgets macro (not only a dashboard macro). But how would it be connected to the dashboard macro? Can the content of a macro be other macros? Something like: {{dashboard}} {{gadget ../}}{{gadget ../}}{{gadget ../}} {{gadget ../}} {{gadget ../}} {{/dashboard}} , where each row is a stack(column) of the dashboard.

2. "The thing is that we need to think about the functional duplication of the Panel Wizard and the new Dashboard." Caty <http://incubator.myxwiki.org/xwiki/bin/view/XWiki/AnamariaStoica> Yes, we need to think about the interface for (Gadgets&XWiki) Gadgets Directory and Panel Wizard. What would their roles be? Their content? (One would add Google Gadgets/Panels to Dashboard macros, the other to side menus...?) Is one interface enough for Dashboard Gadgets and Panels? If so, how would it look like? (where to put it, Panel Wizard is in Admin interface) Also, should the Gadgets Directory support adding gadgets to any Dashboard macro in any page, or just to personal dashboard?

Thanks, Anamaria On Sat, Dec 5, 2009 at 10:56 PM, Anamaria Stoica &lt;anam.stoica(a)gmail.com > > > On Thu, Dec 3, 2009 at 3:57 PM, Ludovic Dubost &lt;ludovic(a)xwiki.org&gt; > wrote: > >> >> This should go beyond user profiles. Space home pages but any page >> should be able to be dashboard pages. >> For these pages we would need a way to make them display as >> dashboard >> pages by default. >> >> We should also make it easy to make these pages dashboard pages >> when in >> the wysiwyg. Like include a "dashboard" macro. >> >> I view it like that: >> >> 1/ Open a page in wysiwyg >> 2/ Type some text, include a dashboard macro >> 3/ Save >> >> When in view the dashboard macro renders the dashboard settings >> saved in >> the content field of the dashboard macro or in XWiki objects save >> in the >> page. >> It adds JS tools to allow to move and change your gadgets and panels >> used in your dashboard. >> > > Gadgets on the iGoogle panel also have an Edit Settings action on > the top > right > corner of every gadget, which opens a form with settings for that > gadget. > > Question: > If one user changes these settings, should they be visible to > everyone, or > just to the > user editing them? (this way different users will see the gadgets > with > different settings > for the same dashboard) > > On the personal dashboard is obvious that only you get to change > them, and > maybe view > the dashboard, > but what about any dashboard added as a macro on a regular page? > > I think the changes should be visible to everyone with view rights > on the > page, and > the settings editable for everyone with edit rights on the same page. > > WDYT? > > > >> >> With this method we might not need the xpage=dashboard template, >> as you >> could just have an #if in the XWikiUserSheet which displays the >> dashboard based on URL params. >> The #if would make a call to the XWiki {{dashboard}} macro >> >> Ludovic >> >> Anamaria Stoica a écrit : >>> Hi devs, >>> >>> I'd like to start working on Gadgets Integration. (this is a new >> feature) >>> >>> I've been working on the specs with Guillaume, and you can see the >> Design >>> page here: http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration >>> >>> The aim of the gadget integration is to provide XWiki users with a >>> dashboard-like page that will display a list of gadgets. These >>> gadgets >> can >>> be either internal gadgets (similar to XWiki panels) or external >>> gadgets >>> (coming from the Google Gadget repository for instance). Users can >> select >>> which gadgets to display on their dashboard from a gadget directory >> located >>> on the wiki. >>> >>> I've also created a few Mockups here >>> http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationfor >>> the Dashboard, Gadget Windows and Gadgets Directory. >>> >>> List of features: >>> Dashboard >>> - Dashboard for each user with drag&drop for Gadget Windows >>> - Display both Google Gadgets and XWiki Gadgets (Panels) >>> Directory >>> - An internal directory with Gadgets in the wiki divided in 3 >>> parts: >>> * XWiki Gadgets defined in the wiki / in the farm (current >> Panels) >>> * Google Gadgets selected out of the global Google >>> Directory by >> wiki >>> admins >>> * If allowed by wiki admins: full Google Gadgets Directory >>> >>> I'd like to include all of the above with basic functionalities >>> into >> 2.2M1. >>> >>> One thing is not clear at this point >> The relationship between >>> XWiki >>> Gadgets and current Panels: >>> >>> They are basically the same thing (same content), but they will >>> have >>> different containers (drag&drop window with edit settings on >>> Dashboard >> and >>> present containers for the side menu Panels). >>> >>> Will all Panels make sense as XWiki Gadgets? If no, when a new >>> Panel is >>> created, how do you know it's meant to be only a side menu Panel >>> and not >>> also a XWikiGadget? (this applies for current Panels as well) >>> >>> Also, very important: where should the interface for the Gadgets >> Directory >>> be placed? Appended to Panels.WebHome or new directory >>> Gadgets.WebHome? >> In >>> my opinion it needs a different interface from the Panel Wizard >> Interface. >>> The Panel Wizard is in the Wiki Preferences (administration >>> space) open >> only >>> to Admins, but the Directory will have to be available to all users >> (even >>> browsable by everyone). >>> >>> An admin interface for picking Google Gadgets from iGoogle >>> Directory >> and/or >>> XWiki Panels for the Gadgets Directory might be needed. >>> >>> How should I treat the 2 of them (XWiki Gadgets vs side menu >>> Panels)? >>> >>> Thanks, >>> Anamaria

On Tue, Dec 8, 2009 at 10:08 AM, Vincent Massol&lt;vincent(a)massol.net&gt; wrote: The dashboard should contain the gadgets on 3 columns, and support drag&drop for them, like here: http://gsoc.myxwiki.org/xwiki/bin/view/Google+Gadget+and+OpenSocial+Integra… or on iGoogle. Now, it's not clear whether the window of the gadget should be part of the Dashboard or the Gadget's macro. Supporting drag&drop, the windows must be subclasses of isc.Window, placed inside a isc.VStack subclass, which are placed inside a isc.HLayout subclass. (the last 2 obviously being part of the Layout of the Dashboard) (isc.Window, isc.VStack, isc.HLayout are classes in the SmartClient library).

But the Gadgets outside of a Dashboard don't need to be placed inside isc.Window's, as they don't need drag&drop. How can the container of a Gadget be chosen depending on where it's placed (into a Dashboard, on a side menu Panel), if the window is not part of the Layout? About DisplayPanelLayoutMacro&Column macros: I think that a kind of DisplayPanelLayoutMacro in combination with a kind of ColumnMacro would work just fine.

I say a kind of, because the DisplayPanelLayoutMacro would have to create a isc.HLayout object and the ColumnMacro a isc.VLayout object. But I'd rather use just one simple macro using the combination of the 2 mentioned above called dashboard. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi devs, I restructured a bit the Design page for Gadgets Integration [0]. I introduced 2 new sections called 'Main Elements' and 'Full Proposals'. The 'Main Elements' section describes the general elements which would be needed/affected by the integration like the Dashboard, Gadgets Directory, Gadget Macros and Panel Wizard, providing several implementation options for each of them. The next section 'Full Proposals' describes entire solutions for Gadgets integration (the full story), by combining implementation options for each element defined in the 'Main Elements' section. Right now there are only 2 Proposals: * Proposal 1 - Gadgets added on Dashboards through Gadgets Directory, and not WYSIWYG Insert Macro Dialog [1] * Proposal 2 - Multiple Macros - each XWiki&Google Gadget as its own Macro [2] , but other may be proposed by mixing other element options in the 'Main Elements' section or introducing new ones. For example, Proposal 1 could be modified to also use an extended WYSIWYG Insert Macro dialog for gadgets.

The mockups page has been divided into 3: * Mockups for GadgetsIntegration - General [3] * Mockups for GadgetsIntegration - Proposal 1 [4] * Mockups for GadgetsIntegration - Proposal 2 [5] Feedback and new ideas are very welcome Thanks! Anamaria [0] - http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration [1] - http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposal1Gadg… [2] - http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposal2Mult… [3] - http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration [4] - http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… [5] - http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… On Tue, Dec 8, 2009 at 12:04 PM, Jerome Velociter &lt;jerome(a)xwiki.com&gt; wrote: wrote: http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration(than… < http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration%28th… drag&drop http://gsoc.myxwiki.org/xwiki/bin/view/Google+Gadget+and+OpenSocial+Integra… the placed being placed kind of http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-rendering-macro-co… create a Gadgets anam.stoica(a)gmail.com http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationfor _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Guillaume Lerouge wrote: Macro favor extend. Hmm, IMO it is exactly the opposite. If gadgets are imported as macros then the WYSIWYG editor doesn't have to know about gadgets and doesn't have to be extended. If we implement a single generic gadget-macro then it will require special handling from the WYSIWYG editor. I'm more for unifying the notion of gadget, panel or macro, thus I'm more for proposal 2.

Thanks, Marius http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposal1Gadg… http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposal2Mult… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration(than… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration%28th… In be http://code.xwiki.org/xwiki/bin/view/Macros/DisplayPanelLayoutMacro http://gsoc.myxwiki.org/xwiki/bin/view/Google+Gadget+and+OpenSocial+Integra… it http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-rendering-macro-co… together, 2 panels page. the a can directory http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationfor (current Directory users _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Guillaume Lerouge wrote: anam.stoica(a)gmail.com introduce I see what you mean. So gadgets are supposed to work only inside a dashboard? The idea of importing gadgets as macros was, I think, to be able to use gadgets anywhere.

If we have a dashboard macro containing multiple gadget macros then we hit the same problem as with any other nested macros (e.g. HTML inside velocity). The WYSIWYG editor needs to be improved so that macro content is edited also in rich text mode (if supported). But this is not going to happen too soon, unless we raise its priority. is gadget I don't think so. Sounds too complicated. Marius http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposal1Gadg… http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposal2Mult… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration(than… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration%28th… a we http://gsoc.myxwiki.org/xwiki/bin/view/Google+Gadget+and+OpenSocial+Integra… of obviously inside 2.0 http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-rendering-macro-co… the how interface) there's panel. page save rights new with external http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationfor between Panel Gadgets _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi On Thu, Dec 17, 2009 at 11:32 AM, Anamaria Stoica &lt;anam.stoica(a)gmail.com I own an in today. macros doesn't dashboard Insert http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… 'Add editor http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration#HGoo… point I think the correct option for now is a mix of stuff that was said before: - Gadgets are created as macros - The wiki admin can select a gadget, click on "turn it into a macro" and the gadget "magically" becomes a XWiki macro - If the whole Google gadget repository is available for users, it means that any user can turn a gadget into a XWiki macro

- We rewrite existing panels to use macros to generate their output

- We create a macro repository at .../bin/view/Macros/WebHome - We add a "Create macro" form in the repository where the user can choose between: - Create a wiki macro - Create a macro from a Google gadget - Gadgets are thus usable through macros and can be added from the WYSIWYG

- The {{dashboard}} macro has the following parameters: "how many boxes to display?" "personal or public dashboard?" - When the {{dashboard}} macro is used into a page, each display box has an "edit" link - Clicking on that link send the user to a special dialog box where she selects which macro to use in the box (through the macro repository and not through the WYSIWYG)

- Since panels are individual documents, choosing which macros to put in them can be done through the WYSIWYG

This has all the advantages and few of the problems of various other implementations: - All the data is generated through macros (be it a list of XWiki pages or a Google World Clock) - All macros get grouped together in a repository - Macro creation is easier and centralized - Panels are only here for display purposes - {{dashboard}} macro is a specific displayer only

WDYT? Guillaume content http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposal1Gadg… http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HProposal2Mult… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… jerome(a)xwiki.com http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration(than… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration%28th… http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegration%28th… menus? dashboard to support http://gsoc.myxwiki.org/xwiki/bin/view/Google+Gadget+and+OpenSocial+Integra… with syntax http://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-rendering-macro-co… to of (Gadgets&XWiki) Google menus...?) so, any any and action same a http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationfor 3 on well) all menu -- Guillaume Lerouge Product Manager - XWiki SAS Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On Thu, Dec 17, 2009 at 1:12 PM, Guillaume Lerouge &lt;guillaume(a)xwiki.com&gt;wrote;wrote: Agree. All of the above make sense Do you mean here to transform all Panels into Macros and to change the content field of all Panels.PanelClass objects to use the corresponding macros (thus keeping also all the Panels)? I don't see the point of Panels if so, they look like generic containers How would the Panel Wizard look like? (see Options 1, 2, 3 for Panel Wizard on Design page http://dev.xwiki.org/xwiki/bin/view/Design/GadgetIntegration#HPanelWizard)

Also, Marius, Option 3 tries to open an Insert Macro Dialog box to insert a macro from outside the WYSIWYG (by clicking 'Add Gadget' button in the interface), would that work? (or something similar...). If not, the macros could still be added to

the panels (empty containers) through the Macros Directory (Option 1) Agree Additional no of boxes parameter makes the users think of something they shouldn't at this point. The way I think about a dashboard is a place where you add stuff or delete stuff as you please, without thinking/planing in advance about it. If you still have to go to the View action to add gadgets on the dashboard, then the solution with just one 'Add more gadgets>>' button at the top I think is better and sufficient. (see http://incubator.myxwiki.org/xwiki/bin/view/Mockups/GadgetsIntegrationPropo… )

Still why is it not possible to add other macros inside the dashboard macro while still in the WYSIWYG editor?

See question above about Panels and Panel Wizard All sound good Anamaria _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs