Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 15839 invoked from network); 24 Nov 2009 09:13:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Nov 2009 09:13:03 -0000 Received: (qmail 3294 invoked by uid 500); 24 Nov 2009 09:13:02 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 3207 invoked by uid 500); 24 Nov 2009 09:13:02 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 3199 invoked by uid 99); 24 Nov 2009 09:13:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Nov 2009 09:13:02 +0000 X-ASF-Spam-Status: No, hits=-10.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Nov 2009 09:12:59 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AA8C4234C1F0 for ; Tue, 24 Nov 2009 01:12:39 -0800 (PST) Message-ID: <1906524836.1259053959697.JavaMail.jira@brutus> Date: Tue, 24 Nov 2009 09:12:39 +0000 (UTC) From: "Chi Runhua (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Updated: (GERONIMO-4950) Improve usability of Geronimo Console In-Reply-To: <1814222931.1257925599886.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/GERONIMO-4950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chi Runhua updated GERONIMO-4950: --------------------------------- Description: 1. re-structure the navigation tree to make it collapsible, the tree level should be less than 3; 2. re-organize the available tree items into new groups, here is a sample list for implementation: * Application Server ** Geronimo Kernel (put Information, Java System Info, Thread Pool and Shutdown portlets in the same page here) ** Web Server ** JMS Server ** EJB Server ** Derby server ** New server assembly * Applications ** Deploy New (Suggest to merge in the plan creator, so that users can either choose to use an existing plan file, or create a new one using the wizard) ** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?) ** Plugins * Resources ** DB pools ** JMS Resources ** J2EE Connectors ** Jar aliases ** Repository * Security ** Users and Groups ** Keystores ** Certificate Authority ** Security Realms * Monitoring and Troubleshooting ** Monitoring ** Logs(Include server logs and Derby log) ** Debug Views *** JMX Viewer *** Classloader Viewer *** JNDI Viewer *** Dependency Viewer 3. re-construct the available portlets to improve embedded assistance information, for example, show breadcrum when user is working on a task; reduce in-line text on the current UI, and use hover-help or pop-up help page only when necessary etc... 4. for the long list on the current UI such as system modules, only show the most frequently used ones, use locate/find to display more.... {color:red}*Risks*{color} to be noticed for UI changes: 1. Doc 2. Testsuite especially for Selenium test script, if any. For more details, see http://old.nabble.com/-Discussion-Re-org-admin-console-ts26217086s134.html Further discussion on navigation items, see http://old.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2.2-to26438212s134.html was: 1. re-structure the navigation tree to make it collapsible, the tree level should be less than 3; 2. re-organize the available tree items into new groups, here is a sample list for implementation: * Application Server ** Geronimo Kernel (put Information, Java System Info, Thread Pool and Shutdown portlets in the same page here) ** Web Server ** JMS Server ** EJB Server ** Derby server ** New server assembly * Applications ** Deploy New (Suggest to merge in the plan creator, so that users can either choose to use an existing plan file, or create a new one using the wizard) ** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?) ** Plugins * Resources ** DB pools ** JMS Resources ** J2EE Connectors ** Jar aliases ** Repository * Security ** Users and Groups ** Keystores ** Certificate Authority ** Security Realms * Monitoring and Troubleshooting ** Monitoring ** Logs(Include server logs and Derby log) ** Debug Views *** JMX Viewer *** Classloader Viewer *** JNDI Viewer *** Dependency Viewer 3. re-construct the available portlets to improve embedded assistance information, for example, show breadcrum when user is working on a task; reduce in-line text on the current UI, and use hover-help or pop-up help page only when necessary etc... 4. for the long list on the current UI such as system modules, only show the most frequently used ones, use locate/find to display more.... For more details, see http://old.nabble.com/-Discussion-Re-org-admin-console-ts26217086s134.html Further discussion on navigation items, see http://old.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2.2-to26438212s134.html > Improve usability of Geronimo Console > ------------------------------------- > > Key: GERONIMO-4950 > URL: https://issues.apache.org/jira/browse/GERONIMO-4950 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console > Affects Versions: 3.0 > Reporter: Chi Runhua > Priority: Minor > > 1. re-structure the navigation tree to make it collapsible, the tree level should be less than 3; > 2. re-organize the available tree items into new groups, here is a sample list for implementation: > * Application Server > ** Geronimo Kernel (put Information, Java System Info, Thread Pool and Shutdown portlets in the same page here) > ** Web Server > ** JMS Server > ** EJB Server > ** Derby server > ** New server assembly > * Applications > ** Deploy New (Suggest to merge in the plan creator, so that users can either choose to use an existing plan file, or create a new one using the wizard) > ** User applications (merge WAR, EAR and Client, maybe bundles in the 3.0?) > ** Plugins > * Resources > ** DB pools > ** JMS Resources > ** J2EE Connectors > ** Jar aliases > ** Repository > * Security > ** Users and Groups > ** Keystores > ** Certificate Authority > ** Security Realms > * Monitoring and Troubleshooting > ** Monitoring > ** Logs(Include server logs and Derby log) > ** Debug Views > *** JMX Viewer > *** Classloader Viewer > *** JNDI Viewer > *** Dependency Viewer > > 3. re-construct the available portlets to improve embedded assistance information, for example, show breadcrum when user is working on a task; reduce in-line text on the current UI, and use hover-help or pop-up help page only when necessary etc... > 4. for the long list on the current UI such as system modules, only show the most frequently used ones, use locate/find to display more.... > {color:red}*Risks*{color} to be noticed for UI changes: > 1. Doc > 2. Testsuite especially for Selenium test script, if any. > For more details, see http://old.nabble.com/-Discussion-Re-org-admin-console-ts26217086s134.html > Further discussion on navigation items, see http://old.nabble.com/Re-categorize-the-items-in-navigation-pane-for-G2.2-to26438212s134.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.