Manu, Am 05.04.2012 um 04:33 schrieb manu [ranga]: Great. Just did so. In general this looks good. For mid-term I think adding/deleting of individual graphs should be possible so that the user can compose his big-charts page. And of course this composition should be somehow stored (*) so that a user coming back will find this dashboard in the composition state he left it. *) This could be a client side cookie or also a server side thing; the latter would also possibly allow that other users take already created dashboards, clone them and modify them to their gusto. -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht München HRB 153243 Geschaeftsführer: Mark Hegarty, Charlie Peters, Michael Cunningham, Charles Cachera

Thanks for the prompt feedback! I have updated the proposal and following is a summary of the ‘diff’ . Yes, I was thinking of the same thing. I was just mentioning that there will be only one metric *per* graph at that stage. I added the clarifications now. In the implementation section I was mentioning a JSON object. I was suggesting, to keep all the composition/configuration sate in that. This object will be stored in the back end. Of cause it can be any other data format such as XML, but JSON will be easier to manipulate at the front end. Added this I added a section suggesting Y-axis to have three configurable types. fixed (user specifies the number of slots) growing (infinite slots, with scrolling) auto (resolution gets smaller to accommodate all points) I was thinking of additionl features but wasn’t sure I should add them to the proposal since they look more like minor implementation details. I’d like some advice on what to add. Tool tips indicating value of a point when mouse is over. Ability to select a subsection of the graph with mouse and zooming in. Showing average, cumulative. Zooming and panning using mouse. Thanks, and feedback is welcomed. -- by,             Manu (R Chathura Manuranga Perera)