On Fri, Feb 25, 2011 at 5:56 PM, Sumedha Rubasinghe <[email protected]>wrote:
> This is still a requirement & was taken up during today's discussion as > well.. From a functional PoV, user clicks on left menu item & the dashboard > appears as a result. > > A different dashboard appears for each menu item. > Thanks for the clarification Sumedha. IMO, may be products like BAM need to have multiple dashboards OOTB? Apologies if we already have plans for such. Thanks, Senaka. > /sumedha > > > On Fri, Feb 25, 2011 at 5:34 PM, Senaka Fernando <[email protected]> wrote: > >> Nuwan, >> >> We originally had some idea of having multiple dashboards. Is that still a >> requirement? If so, I'd like to know how that works. >> >> Thanks, >> Senaka. >> >> On Fri, Feb 25, 2011 at 2:46 PM, Nuwan Bandara <[email protected]> wrote: >> >>> Hi All, >>> >>> Following are the Changes which were proposed at the GS usability review. >>> Gadget Server Portal View >>> >>> - Dashboard >>> >>> >>> 1. First impression : First few gadgets should not get user inputs: >>> should be some with information / visualization >>> 2. Have multiple tabs showing different capabilities. (maybe domain >>> specific) >>> >>> >>> - Should at least have four tabs >>> - How to track people, information (HR) >>> - Show the power of VIS: Graphs & Charts >>> - Web analytics etc. >>> - SAP Gadget kind of view >>> - ebay service monitoring kind of gadgets >>> >>> >>> 1. When adding the gadgets reload only the new gadgets : don’t reload >>> the other gadgets in the tabs. >>> 2. Newly added gadget should be balance-ly played in the dashboard. >>> At present it is added to the bottom of the first column. >>> 3. Gadgets should be only available in maximized view for certain >>> tabs. >>> >>> >>> - Add Gadgets >>> >>> >>> 1. Check boxes do not give enough information about the gadget in >>> anon mode: should have a link to a more informative page. >>> 2. Even for anon mode the same gadget repository should be shown. >>> 3. Ability to restore removed gadgets >>> >>> >>> - Gadget Repository/browser >>> >>> >>> 1. Have the same Gadget Repository for anon. mode with correct >>> permissions. >>> 2. Add-button should be disabled if no gadget is selected. >>> 3. The Gadget list should be categorized >>> 4. Good if we can show where the gadget was added (to which tab) >>> 5. Back to the dashboard should be a link (not a button) >>> 6. Implement search functionality for the repository >>> 7. The button styles should be redesigned. >>> 8. Pagination is not prominent. >>> 9. Link thumbnail of the gadget to the gadget page >>> >>> >>> - Gadget Page >>> >>> >>> 1. Need to be sleek >>> 2. Need to show related gadgets >>> >>> >>> - Tabs related improvements >>> >>> >>> 1. Should have a default name when creating a new tab >>> 2. A default tab layout should be selected >>> 3. Redesign the tab layout icons so that it is self descriptive (no >>> tool tips) >>> 4. Get rid of WSO2 carbon in message box header >>> 5. Disable the OK button if there is no tab name. >>> 6. Transferring data coming in the web browser when adding a new tab. >>> Have a look at for whats happening >>> 7. Remove the active tab should be done with a cross icon on the tab >>> 8. Tab renaming and rearranging >>> 9. Should be able to change the current tab layout >>> 10. Every tab should be removable unless its the last one. >>> 11. Admin can decide some tabs are read-only (cannot change or >>> delete) >>> 12. Redesign the add tab / clone tab icons >>> 13. Need to keep track of removed tabs and ability to restore >>> >>> >>> - Sign-in page >>> >>> >>> 1. Add Remember-me feature >>> 2. The page should not be scrolled >>> 3. The static information need to be useful in the context of GS. >>> >>> >>> Gadget Server Administrator View >>> >>> - Theme-ing page >>> >>> >>> 1. Theme-ing should also be available for normal users but admin >>> should be able to decide it >>> 2. Should have a previewing mechanism (like in wordpress maybe using >>> light box) >>> >>> >>> - Add gadget to repository form >>> >>> >>> 1. Need complete redesign >>> 2. Should follow form design conventions >>> - If there is a Cancel option it should be the last button >>> - View source should be at top >>> - Gadget thumbnail upload should be user friendly (image should be >>> in left side) >>> 3. Gadget URL should be picked from the registry >>> 4. When mandatory fields are not filled the save button should be >>> disabled. >>> 5. When uploading a large image it should be re-sized or cropped >>> >>> General Requirements >>> >>> 1. Ability to have multiple dashboards at product mode >>> 2. GS should work offline without any issue. >>> >>> >>> Regards, >>> /Nuwan >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2, Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://www.linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
