-
improvements on the graphic engine
hi, ladies. After a long parenthesis, I’m going to continue, with the improvements on the graph engine of pandora, i.e., the code that produces all the graphs you can see in the pandora console.
Before begining to code, I would like to ask you, developers and users, which features you think that should be improved/created/researched regarding the pandora’s graph engine.
Please, answer to this post with your ideas, complains, experiences, etc.
Actually, the main goals of this branch of development are be:
– to eliminate the jpgraph library dependences. These libraries are great, but they have licence issues. As you know, we aim to the PEAR:Image_graph libraries now as a possible candidate (we accept other suggestions)
– we have begun to use the cross-browser javascript libraries to enhance the interactivity with the graphs (float menus, parameters like zoom, resolution, etc)
– we have also begun to improve the performance of the engine. Now, all the graphs are precalculated in memory tables in the database, and this data is re-used when possible.
– events of a module can be represented as coloured lines in the graphs
– graphs for generic_data_string (statistics)
– … ideas???