Hi Alan

> > There are many other examples and demos in the plplot distribution which
> > show off plplot in all its glory.  Do we really need to complicate these
> > "output driver" demos with code which essentially duplicates what's already
> > in other examples?
> 
> One purpose of the examples is to test PLplot capabilities. I am concerned
> that extXdrawable_demo.c only exercises 7 PLplot commands (counting plsdev,
> plsetopt, plinit, and plend) so there might be hidden issues in the way this
> output driver is implemented which are not encountered because PLplot
> capabilities are exercised so little.

Sure.  As a side note however, keep in mind that the extXdrawable "driver"
isn't actually a separate driver in its own right.  Its functionality is
triggered by supplying an option ("external_drawable") to the standard
xcairo driver.  This option causes the xcairo code to use a preallocated X
Drawable rather than creating its own.  Aside from that, xcairo works in
exactly the same way that xcairo normally works.

Having said that, I acknowledge your interest in wanting to exercise the API
more fully in this alternative context.

> I acknowledge I am paranoid about testing, but that paranoia got an energy
> boost today when I noticed the missing text in the ext-cairo-test results.
> :-)

I understand.  It's certainly better to catch bugs before release.

> > [out of order] For someone who just wants to see how to use these
> > specific features, they then need to trawl through all this extra
> > generic plplot code to get to the stuff they want (assuming that they
> > don't completely overlook the bits they need).
> 
> Good point which could/should be addressed by carefully segregating the
> PLplot commands (e.g., using a separate routine) from the rest of the demo
> source and documentating that segration within the code.

This I think would be very important to ensure.

Regards
  jonathan

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Plplot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to