Hi Phil I agree, it does not make much sense going back to the old wxwidgets. My usage of it is inside a wxWidgets GUI app, so I don't need any special features. In fact it has been working well for me in the last couple of months, but last week I started having errors so I just gave a try to the old wxWidgets out of curiosity.
thanks -Pedro ----- Original Message ----- From: "Phil Rosenberg" <p.d.rosenb...@gmail.com> To: "Alan W. Irwin" <ir...@beluga.phys.uvic.ca> Cc: "Pedro Vicente" <pedro.vice...@space-research.org>; <plplot-devel@lists.sourceforge.net> Sent: Friday, December 09, 2016 6:49 PM Subject: Re: [Plplot-devel] Fwd: Deprecated wxWidgets error > Hi Pedro > As Alan said, we can't have both working together. Well, I suppose we > could, but the effort required would be large and time is finite. If > you are interested in the usage differences then: > > The new wx backend discarded use of AGG and freetype as wxWidgets now > has much better support for antialiased graphics and text. This also > massively simplifies support. > > For calling from a wxWidgets application the wxPlplotwindow class is > now template, meaning it can inherit from any wxWindow - so as well as > having a plplot panel, you can have anything from a plplot frame to a > plplot button should you wish. > > For calling wxWidgets from a console application all the rendering is > performed in a separate utility which has commands sent from the > console application. This removes some problems we had with large > amounts of almost duplicated, but subtly code, plus possible threading > issues. Unfortunately there at performance issues that I haven't been > able to get to the bottom of yet. > > Lastly, some of the less well used features of Plplot are not yet > supported, like maybe changing the fill algorithm. But certainly all > the well used things are there. > > So basically, unless you really want to use AGG or FreeType, then I > don't see much need to use the deprecated version. I certainly won't > be going back and fixing any bugs in the deprecated version. If, > however, there is some feature that is still missing from the new > version then let me know and I'll try to prioritise. > > Phil > > On 9 December 2016 at 21:45, Alan W. Irwin <ir...@beluga.phys.uvic.ca> > wrote: >> On 2016-12-09 15:39-0500 Pedro Vicente wrote: >> >>> so, it seems that the cmake option is really needed >>> -DOLD_WXWIDGETS=ON >>> >>> I only found out this by reading the script >> >> Reading the script is an excellent idea so I encourage you to keep doing >> that. However, we also document such changes in our release notes. >> In this case you won't find that documentation in README.release >> because OLD_WXWIDGETS was introduced in a previous release. So >> instead you have to look in the cumulated old release notes, >> OLD-README.release for the relevant documentation of >> -DOLD_WXWIDGETS=ON. >> >> [...] >> >>> I have a request, would it be possible to have the "deprecated" >>> wxWidgets code and the templated one at the same time? >> >> No. If you want access to both for comparisons, use separate build >> trees (and install trees). Also, -DOLD_WXWIDGETS=ON is deprecated >> because it is an emergency measure which gives you access to the old >> frozen wxwidgets code. There is no further support for >> -DOLD_WXWIDGETS=ON beyond that because that old wxwidgets code was not >> Phil's responsibility and there are lots of known issues with it. So >> Phil is focussing exclusively on development of the new wxwidgets. >> Thus, if you find some features you like with -DOLD_WXWIDGETS=ON, then >> ideally you should make changes to your local _new_ wxwidgets to add >> that feature and send patches (ideally generated by "git >> format-patch") to this list for Phil to evaluate. N.B. it is a >> virtual certainty your patch will be rejected if it contains fixes for >> multiple issues. So instead each of your individual patches should >> focus on just one logical issue at a time. And sometimes we do reject >> ideas such as yours above to have both old and new wxwidgets in the >> same build tree. But so long as your patches are focussed on one >> thing at a time (and not necessarily limited to just the new >> wxwidgets) and otherwise acceptable, then such development help with >> PLplot would be much appreciated. (Note, we recommend "git >> format-patch" for generating patches because that gives you full >> credit for your work in the git log.) >> >> 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 >> __________________________ >> >> ------------------------------------------------------------------------------ >> Developer Access Program for Intel Xeon Phi Processors >> Access to Intel Xeon Phi processor-based developer platforms. >> With one year of Intel Parallel Studio XE. >> Training and support from Colfax. >> Order your platform today.http://sdm.link/xeonphi >> _______________________________________________ >> Plplot-devel mailing list >> Plplot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/plplot-devel > ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
