On Wed, Apr 2, 2014 at 9:49 AM, Ecaterina Moraru (Valica) <[email protected]
> wrote:

> Hi,
>
> From the list of alternatives
>
> http://design.xwiki.org/xwiki/bin/view/Proposal/AppBar#HImplementationConsiderations
>
> Var 2 and Var 4 have the greatest potential.
>
> Var 1: The only interesting aspect is the ability to reuse the Panel
> Wizard's Drag&Drop ability in order to customize your AppBar. But if we
> would go with Var 2 we could create a dedicated UI to customize the AppBar.
>
> Var 2: This means a new class used only by the Flamingo skin. Application
> Developer should offer a page containing an object of this type with their
> wanted look for the AppBar. Being a new class we could decide what
> properties we add (taking into consideration maybe rights, favorite
> aspects, etc.)
>
> Var 3: Considering UIX discussions, an UIXP is not the best decision IMO
> for this problem, a class is better suited.
>
> Var 4: seems interesting from a reusability point of view. The thing is
> that there are not that many instances of AddApplicationUIX extensions and
> also in the mail about UIXP the conclusion was that it was better to use
> classes.
> Reusing this extension is complicated also because it doesn't provide all
> the information needed by the AppBar (32px icon, etc.)
>
> -----
>
> I prefer Var 4.
>

I wanted to say Var 2: ApplicationBarEntryClass :)  but with the mention
that the 6.0M1 beta version of Flamingo is using a variation of Var 4.

Thanks,
Caty



> It would be nice to hear also other opinions. Guillaume maybe you could
> make a proposal for the ApplicationBarEntryClass properties and types.
>
> Thanks,
> Caty
>
>
>
> On Thu, Mar 13, 2014 at 7:16 AM, Ecaterina Moraru (Valica) <
> [email protected]> wrote:
>
>> On Wed, Mar 12, 2014 at 4:15 PM, Guillaume "Louis-Marie" Delhumeau <
>> [email protected]> wrote:
>>
>>> Actually, we also need to find a way to determine which is the "active"
>>> application, in order to display it differently.
>>>
>>
>> For this problem IMO the best solution would be use the space name.
>> For every space, we add in the body element a space class, like '
>> space-Main', etc.
>> We could have something like 'space-{$appSpaces}', example:
>> .space-MoccaCalendar .appBar .calendarIcon {
>>   // extend active styling
>> }
>>
>> Thanks,
>> Caty
>>
>>
>>
>>
>>>
>>>
>>> 2014-03-12 14:49 GMT+01:00 Guillaume "Louis-Marie" Delhumeau <
>>> [email protected]>:
>>>
>>> > Hi guys,
>>> >
>>> > I have pushed a first version of flamingo in platform/XE, but it is
>>> only a
>>> > prototype that need a LOT more do be ready for production.
>>> >
>>> > One of the new things brought by flamingo is the "Applications" left
>>> bar,
>>> > which is not exactly the same thing as the Applications Panel we
>>> already
>>> > have.
>>> >
>>> > We can see it more as a "dock" with a list of applications, and in the
>>> > future, we could make it customizable by the user. Caty has written a
>>> > proposal for this [1].
>>> >
>>> > Right now, for the first implementation, I need to make some choices
>>> about
>>> > the way we "populate" this bar. We can create new classes to describe
>>> the
>>> > bar entries, or new UI Extensions (maybe not the good choice regarding
>>> the
>>> > recent e-mails...), or by re-using the existing AddApplicationUIX...
>>> It is
>>> > described on
>>> >
>>> http://design.xwiki.org/xwiki/bin/view/Proposal/AppBar#HImplementationConsiderations
>>> .
>>> >
>>> > Other thing: In my draft, I have created a new VM file on the
>>> filesystem
>>> > for this concept. Maybe I should create it as an extension point
>>> stored in
>>> > the database, but it means it won't appear on an empty wiki. WDYT?
>>> >
>>> > I let you make some comments about this.
>>> >
>>> > Thanks,
>>> >
>>> > Caty & Louis-Marie
>>> >
>>> >
>>> > [1] http://design.xwiki.org/xwiki/bin/view/Proposal/AppBar
>>> >
>>> >
>>> _______________________________________________
>>> devs mailing list
>>> [email protected]
>>> http://lists.xwiki.org/mailman/listinfo/devs
>>>
>>
>>
>
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs

Reply via email to