Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <1269735562.264891268657787138.JavaMail.jira@brutus.apache.org>
Date: Mon, 15 Mar 2010 12:56:27 +0000 (UTC)
From: "Felix Meschberger (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Issue Comment Edited: (FELIX-569) Improve Configuration Page
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/FELIX-569?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12845=
297#action_12845297 ]=20

Felix Meschberger edited comment on FELIX-569 at 3/15/10 12:54 PM:
-------------------------------------------------------------------

Ok, for removing the PID part (your exaplanation makes sense)

I am not so sure about the factory PID column: I didn't understand yet why =
you want to group by factory PID ?

I wonder, whether it would be an option to merge the two tables:

  * Each Configuration (without factory PID) occupies a row with name, bund=
le and action buttons
  * Each Factory (template) occupies a row with name, bundle, and just the =
create buttons
  * Each Configuration instance of a factory is a "child row" of the corres=
ponding
         Factory(template) row providing the PID (name is the same as for t=
he factory) and buttons


Something like

| A Config      |   Bundle A    |  [Edit] [Undind] [Delete] |
| A Factory     |   Bundle B    |  [Create] [Unbind] |
|         <pid1>                          |  [Edit] [Delete] |
|         <pid2>                          |  [Edit] [Delete] |
| Config 2       |  ---                 |  [Edit] [Undind] [Delete] |


      was (Author: fmeschbe):
    Ok, for removing the PID part (your exaplanation makes sense)

I am not so sure about the factory PID column: I didn't understand yet why =
you want to group by factory PID ?
 =20
> 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=C3=A9
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: webconsole-3.0.0
>
>         Attachments: config-factory-tables.patch, config-factory-tables.p=
ng, 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 fri=
endly.
> The more component you have , the more it get difficult to find in the dr=
op down list.
> So to make it more easy I would suggest to introduce some kind of  "Tree"=
 browse with categorized component configuration eventually.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.