[
https://issues.apache.org/jira/browse/FELIX-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-569:
------------------------------------
Attachment: FELIX-569-fmeschbe.patch
Attaching another proposal as FELIX-569-fmeschbe.patch:
The service PID is not attached to the configuration name in paranethesis but
is merged into the factory PID column to form a kind of an ID column.
The merger is done as follows:
* If the configuration has no factory PID, only the PID is used
* If the factroy PID is a prefix to the PID (as is the case in Apache Felix
Configuration Admin)
only the PID is used
* Otherwise the is set to factoryPID + "/" + PID
Still I am not sure, whether this is the best of all options ... The table gets
rather wide.
But cutting off the PID and/or factory PID would not allow use to order by one
of them ...
> Improve Configuration Page
> --------------------------
>
> Key: FELIX-569
> URL: https://issues.apache.org/jira/browse/FELIX-569
> Project: Felix
> Issue Type: Improvement
> Components: Web Console
> Reporter: Thierry Ygé
> Assignee: Felix Meschberger
> Priority: Minor
> Fix For: webconsole-3.0.0
>
> Attachments: config-factory-tables.patch, config-factory-tables.png,
> config-name_column-sorting.patch, config-table-update.png,
> config-table.patch, config-table.png, config-table2.png, config-tree.patch,
> config-tree.png, FELIX-569-fmeschbe.patch
>
>
> At the moment the way to select the Configuration page is not so user
> friendly.
> The more component you have , the more it get difficult to find in the drop
> down list.
> So to make it more easy I would suggest to introduce some kind of "Tree"
> browse with categorized component configuration eventually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
