On 2015-05-21 22:14-0400 Jim Dishaw wrote:

> Bad news.  I searched for my old Windows driver and I have lost it
to the ether.  I found some remnants, but not enough to compile.  I
can a recreate it without too much difficultly.  The driver version
that I had created was a merge between the X11 and the Windows GDI
drivers because I wanted to have a common UI between the two platforms
(e.g. menubar, crosshairs for picking points, printing).

> Is it worthwhile for me to recreate this driver?  It should not
interfere with the plbuf/plmetafile cleanup; in fact, digging into a
driver might help in clarifying some concepts.

Hi Jim:

That is mostly up to you although I do take your point it could be a
useful exercise for you.  Also, I don't use the xwin menubar or
printer feature at all so cannot properly evaluate their capabilities,
but from comparisons I have done with the -locate feature of
examples/c/x01c.c, running the 3rd (interactive) page of example 20,
and running special octave interactive examples, the xwin crosshairs
capability is the best of all our devices, and it would well be worth
copying what it does to xcairo, qtwidget, wxwidgets, wingcc, and the
new windows device.

Just in case you decide it would be worthwhile to recreate that driver,
I searched through the plplot-devel archive I have collected over
the years and found some references to your Windows driver but
no specific attachments of your source code except possibly part
of your driver that was introduced by you back in 2008 in the following
discussion with Werner:

"
I think it is a good idea.  In fact, I have created an abstract driver
for an interactive device.  I wanted to create a consistent user
interface for both X11 and MS Windows.  In order to achieve that, I
split the driver into two parts:  The real device driver and the
abstract driver.

The real device driver defines the dispatch setup function (and the
dummy function if it is disabled).  The dispatch table is configured to
point to functions in the abstract driver.  The abstract driver calls
the underlying API calls through a function pointer.

I have attached my  abstract driver as a strawman.  It is a work in
progress, so it is a bit crude still.
"

I could send that attachment along to you if you lost the original
that you sent out.

You also might want to search the plplot-devel archives yourself
for any descriptions you gave of your device driver, if you
have not done that already.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to