Hi Jim: On 2017-01-30 10:45-0500 Jim Dishaw wrote:
> I will rebaseline my driver with the newest release and push to the git repository. I now have a Windows Vista and a Windows 10 build environments setup for development and testing. I also have a high DPI machine that will help test out the implementation on the environment. I look forward to seeing that push. > I have not been using Freetype—I have been keeping it as pure windows API as > I can. Excellent. >> I highly recommend that you use the same device driver (called >> windows?) to implement both devices similarly to the way that the >> cairo device driver implements so many different devices. And I can >> certainly help with all the CMake aspects of discovering whether the >> current Windows platform supports GDI/Uniscribe and/or >> Direct2D/DirectWrite and enabling/disabling these two devices and >> their non-Hershey handling of fonts accordingly. But we can work out >> all those details later after an initial development with these >> (experimental) devices disabled by default. >> > > I have to think about this recommendation. It sounds like a good idea. > [out of order] I was planning on using wingdi.c as the filename. That is fine for now for the driver name, and using "wingdi" for the device name (in perpetuity) is fine as well. I now realize that the above recommendation from me was premature so let's just say the one driver two devices possibility (along with a driver name and also source code filename change but not the wingdi device name) is a possibility to be considered in the future when you start developing the Direct2D/DirectWrite device. But for now the focus should be on finishing the GDI/Uniscribe wingdi driver with just one device implemented named "wingdi". 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 __________________________ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
