FYI, I am going to start the implementation of the first proposal, for 6.1. - In order to help developers to create their application panel, I will create a wiki macro so they just have to call it. - In the future, we will investigate a way to have customizable panels (like we have for dashboard gadgets and wiki macros). - The Panel Wizard should be improved too to make it easy for users to understand that they should use it to add their favourite applications in the left bar. - I will remove the left panel configuration of the Blog Application to fit with Flamingo. Thanks, Louis-Marie. 2014-04-15 16:01 GMT+02:00 [email protected] <[email protected]>:
On 14 Apr 2014 at 18:27:50, Guillaume Louis-Marie Delhumeau ( [email protected](mailto:[email protected])) wrote:
So you are not opposed to the panel improvements we have proposed, but you don't want users to create a panel per application, by themselves.
[Brainstorm] If we agree on the idea that the application icons should be implemented with panels, maybe we can add different kinds of panels:
A - the normal panels: what we already have B - auto-generated "virtual" panels.
For these (B), we can propose in the panel wizard some panels that do not really exists, but that are generated upon app descriptors.
Other idea: a document listener that generates the appropriate application panel every time the app descriptor is changed.
In the two cases, we need to define what a descriptor is. Caty is writing a proposal about it and we will post it here when it is ready.
What do you think?
If we want to go that way we could define the notion of Panels at the java level as components and then have wiki components for implementing Panels as wiki pages. This allows generating and registering panels dynamically easily. Then have some java code that listen to UIX for “platform.panels.leftPanels” and “platform.panels.rightPanels” extension ids (in the future for some XObject) and register new Panel impls agains the CM.
But that’s a bit of work…
Thanks -Vincent
Thanks, Louis-Marie
2014-04-10 21:06 GMT+02:00 Marius Dumitru Florea < [email protected]>:
On Thu, Apr 10, 2014 at 6:08 PM, Guillaume "Louis-Marie" Delhumeau wrote:
But developers already needs to create a UI Extension, why not a panel?
Because for the panel you'd have to write code.. Moreover, we discussed about the fact that the non-typed parameters of the UI Extension are not always a good idea and that for the application panel a dedicated class would have been better (with typed properties). There is a big difference between having:
icon: myIcon.png
and
content: #if ($panelWidth == "small") [[image:myIcon.png]] #else ## Display stuff as a list #end
The first is semantic (data) and can be reused in other places. The second would have to take the image from a property in order to not duplicate the application icon, so more code.. The first is clear to the developer: he has to specify the application icon. The second is not, without reading documentation about what to write in the panel content in order to have the application icon available for the application bar.
Maybe we should provide a template for this kind of panels so it would be very easy to create a new one, or a wizard that generates it easily?
I find it awkward to ask the dev to create a panel in order to display an icon on the application bar. The dev should just fill an application descriptor and then the App Bar manager (panel wizard or whatever) should create a panel on the fly (if that is needed for the underlying implementation) to display the icon/shortcut on the application bar.
Thanks, Marius
2014-04-10 16:09 GMT+02:00 Marius Dumitru Florea < [email protected]>:
To be clear, I'm not against reusing the left panels bar for the app bar. What I don't like is asking application developers to write a panel (boilerplate code) in order to have their application listed somewhere.
Thanks, Marius
On Thu, Apr 10, 2014 at 4:41 PM, Marius Dumitru Florea wrote:
I don't like it very much. Instead of writing code like this:
#if ($panelWidth == "small") ## Display stuff as icons #else ## Display stuff as a list #end
in a panel, I would prefer to describe my application using an
XClass
(with properties for app name and icon). Then the system (XWiki, Panel Wizard, whatever) should use these data (app name and icon) to build and UI that lets the user put shortcuts to his favourite app to a bar. If you want, the system should create this "panel". Asking app developers to write this boilerplate code to have their app listed is not nice.
Thanks, Marius
On Thu, Apr 10, 2014 at 4:17 PM, Guillaume "Louis-Marie" Delhumeau wrote: > Hi. > > After some discussions with Caty and Vincent, we would like to propose you > new ideas about the panels technology, that replaces our previous > propositions about the Flamingo Applications Bar. > > The proposal is there, with more explanations and screenshots: > http://design.xwiki.org/xwiki/bin/view/Proposal/PanelsImprovements > > Here is my +1. > > Louis-Marie
devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs