On Wed, Dec 10, 2008 at 03:51, <[EMAIL PROTECTED]> wrote: >> IMO the graphs are already to cluttered for a quick overview >> and I have ideas for adding even more clutter (that matters >> to me, like the date the graph was produced :-). But if >> clutter doesn't matter, why not do both? I do not believe >> that the additional overhead is such a problem. > > I believe the graphs should be template driven, somewhat like the > template pages.
While this would be nice, it would be very using the current web front end. The HTML template system currently in use is basically a "one-way" deal: the various PHP scripts process various things (.rrd files, taling to gmetad, etc), and stuff the results into pre-existing HTML template files. The templates themselves do not do anything besides presentation. Specifically, nothing in the templates are used as "input" for these calculations. > However, the choice of templates would replace the choice of graph sizes > - so the user would be able to choose which template they want. > > Each template could specify: > - graph size This is only possible because of clever (ab)use of HTML forms and URL parameter processing. The other ideas you mentioned (show stats, fonts, hostnames) cannot be driven explicitly at the template level, given the current code. > There are probably other things that could be configured too. Of course! :) > One related issue is that the HTML pages should specify the height and > width in the IMG tags for graphs - maybe a function is needed to > generate IMG tags. This is slightly circular, since rrdtool will take height and width arguments for the size of the chart--*not* including the border, title, legend, etc--and return the total image size on the command line. However, since we use passthru(), this information is currently lost. A further complication is that crafting the various reports is not always easy. Trying to make them flexible enough to be truly template driven will make the code much more complicated. Now, all of that said, I actually don't object to the idea of making the web frontend more flexible. In fact, I think that it is a great idea. But there's very much a tradeoff between making/keeping the code sane, and doing everything that we'd like. I propose something of a middle ground: make the various parts of the frontend generic enough that building a new template is straight forward. Specifically, make graph creating simpler, and in such a way that it is easy to specify a number of these different parameters--sizes, titles, etc. If things are set in the conf.php file, perhaps we could let a different .php file override some of the settings on a per-template basis? -- Jesse Becker GPG Fingerprint -- BD00 7AA4 4483 AFCC 82D0 2720 0083 0931 9A2B 06A2 ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
