Hi Stefan, > > a good aproach would be to implement this independant of > > rrd_graph > > yes, that was as well my idea. Im still stuck currently on some > work but mainly these are the lines, Im thinking: > > - API: use Cairo or OpenGL ? Cairo is a 2D libary AFAIK. So if I > would need as well for future 3D primitives OpenGL comes handy. > ... Any comments on this ? How can we integrate then rrd_graph with > needed opengl bits - could we make this a ./configure option > during the config stage ?
you have to consider how you expect people to look at the graphs. If you manage with cairo, you get a nice abstract frontend for all sorts of different output devices ... if you are about to produces 3d animations or even models, then a different aproach may be more suitable ... in general opengl applications tend to be not 'the thing' one wants regarding portability. cheers tobi > - at some point RRD would need to go further and have better 3D > support. Whats the plan here and what API would be a better fit > for RRD ? > > - plan 1: develop independently of rrd_graph and see how it goes > > - plan 2: develop hand in hand with rrd_graph > > > I think ... or if you are into big things think of a way of > > makeing > > rrd_graph more modular ... > > > > ich you first write the documentation and discuss this on the > > rrd-developers list, your chances of success (integration) will > > be considerably higher .... > > I will see first plan 1 and estimate a bit the work. I simple > need to think what API to use and how to get started. > > Thanks, > stefan > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland http://it.oetiker.ch [email protected] ++41 62 775 9902 / sb: -9900 _______________________________________________ rrd-developers mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers
