felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Saginor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-3769) Improve the way Web Console UI manages growing number of plugins.
Date Wed, 28 Nov 2012 00:32:58 GMT

     [ https://issues.apache.org/jira/browse/FELIX-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Henry Saginor updated FELIX-3769:

    Attachment: FELIX-3769.tar.gz

I am sorry for not following the correct process. Updated attachment contains patch files.
> Improve the way Web Console UI manages growing number of plugins.
> -----------------------------------------------------------------
>                 Key: FELIX-3769
>                 URL: https://issues.apache.org/jira/browse/FELIX-3769
>             Project: Felix
>          Issue Type: New Feature
>          Components: Web Console
>            Reporter: Henry Saginor
>            Priority: Minor
>         Attachments: FELIX-3769.tar.gz, FELIX-3769.tar.gz
> Something needs to be done about growing number of web console plugins. Currently the
UI displays a tab for each plugin. This makes the UI cluttered as more and more plugins are
added. To address the tabs should be replaced with a tree structure or a drop-down menu. 
> Felix Meschberger has proposed the following on the dev list to implement this.
> "* Plugins registered as services may have a "felix.webconsole.category" property
> indicating the category. Plugins not registering this property will be placed in
> the default category
> * AbstractWebConsolePlugin is ammended with a getCategory() method, which may
> overwritten by implementations. The default implementation in the
> AbstractWebConsolePlugin class returns the default category
> * A default category can be configured
> * Categories are simple strings such as "OSGi" or relative paths such as
> "Sling/Main". Relative paths define multi-level trees. I think in general a
> single level is probably enough. Maybe we can start with just supporting a
> single level (so just plain strings).
> * Translation of categories is such that each segment in the path (or the
> complete string if there is no sub-categories) is converted into a translation
> label by prefixing with "category.". So the translation for the "OSGi" category
> would be found with the translation string "category.OSGi".
> * The plugin navigation is refactored to move it to the left and render it as a
> tree structure (I assume we can use the JQuery treetable plugin)."

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message