Mails

• [Proposal] Having the AppBar panel in the left side column by default http://markmail.org/thread/fepivlgeunhhus7m (May 28, 2014)
• Flamingo Application Bar http://markmail.org/thread/2ftksr6bxstazg25 (Mar 12, 2014)

Description

• Related Proposals
• About AppBar
  • Colibri vs. Flamingo
  • Functionality Extensibility
  • Differences between 'AppBar' and 'Applications' panel
• Use Cases
• Implementation Considerations
  • Var 1. Using PanelClass objects to represent AppBar entries
  • Var 2. Creating a new ApplicationBarEntryClass
  • Var 3. Creating a new Extension Point for AppBar
  • Var 4. Reusing 'AddApplicationUIX' UI extensions
    • Var 4.A
    • Var 4.B
    • Var 4.C
    • Var 4.D
• Implementation Considerations about the Bar itself
  • Var A
  • Var B
  • Var C

Related Proposals

• Panels Improvements for Flamingo Skin

About AppBar

Colibri vs. Flamingo

Main difference between Colibri and Flamingo is that:

• in Colibri we have a 'Left Panels' and a 'Right Panels' zone, 
• in Flamingo we have an 'AppBar' and a 'Panels' zone.

Functionality Extensibility

One thing to consider regarding the 'AppBar' is that at some point in the future we might want to extend/replace it with something else (like 'Hierarchy' or even 'Left Panels') depending on the Flavor.

We could do this by having a 'Collapsable' mechanism that would switch through the views depending on the need. 

Differences between 'AppBar' and 'Applications' panel

Use Cases

Implementation Considerations

Var 1. Using PanelClass objects to represent AppBar entries

It would allow the customisation of AppBar with the Panel Wizard

Var 2. Creating a new ApplicationBarEntryClass

Var 3. Creating a new Extension Point for AppBar

And have new UI extensions that reference it

Var 4. Reusing 'AddApplicationUIX' UI extensions

Var 4.A

Adjust the UX and add another param that contains a link to the 32x32 icon that is needed for Flamingo

Var 4.B

Parse the parameter value and provide a different folder if skin is Flamingo that will contain 32x32 images (but that are having the same name as the ones from Colibri set)

Var 4.C

Let the application developer attach an image to the ApplicationsPanelEntry page, use that image first, then fallback on a local set

Var 4.D

We could use initially the Silk icons 16x16, but provide some styling to make them bigger, something like we have on Features

Implementation Considerations about the Bar itself

Var A

The Bar is a new left column, in addition of existing panel columns or replacing the left panels.

• Pros:
  • Do not break existing panels behaviour
• Cons:
  • Add a new concept to implement
  • Need to add a UI to select which applications the user don't want to have in the bar (a filter)

Var B

The Bar is a panel, in the left panel columns which would be resizable. It enables us to add more panels in the left columns after and before the applications panel

• Pros:
  • Reuse the existing panels mechanism
  • Could probably work with Colibri too, with minimal effort.
• Cons:
  • Need to add the ability to select the width of the panel columns
  • Need to add a UI to select which applications the user don't want to have in the bar (a filter)

Var C

Each application provides its special panel, and the left bar is the standard left panel column which would be resizable.

• Pros:
  • Reuse the existing panels mechanism
  • Easy to add/remove an application in the left bar via the drag&drop feature of the panel wizard
  • Consistency (the UIs to change the panels and the app bar are the same)
• Cons:
  • Need to add the ability to select the width of the panel columns
  • Each application should provide a panel
  • Hard to add a new panel automatically in the left bar when a new app is installed
  • Do not use the same data source as the old applications panel
  • Could become a mess in the panel wizard (too many panels)