You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2012/12/28 16:34:12 UTC

[jira] [Resolved] (FELIX-3769) Improve the way Web Console UI manages growing number of plugins.

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

Felix Meschberger resolved FELIX-3769.
--------------------------------------

    Resolution: Fixed

Resolving this issue as fixed with the open issues being handled by follow-up issues.
                
> 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
>    Affects Versions: webconsole-4.0.0
>            Reporter: Henry Saginor
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: webconsole-4.0.2
>
>         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