Re: [Plplot-devel] Fwd: Deprecated wxWidgets error

2016-12-09 Thread Pedro Vicente 
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
>> ___

Re: [Plplot-devel] Fwd: Deprecated wxWidgets error

2016-12-09 Thread Phil Rosenberg 
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  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

Re: [Plplot-devel] Fwd: Deprecated wxWidgets error

2016-12-09 Thread Alan W. Irwin 
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

[Plplot-devel] Fwd: Deprecated wxWidgets error

2016-12-09 Thread Pedro Vicente 


Hi Phil

so, it seems that the cmake option is really needed
-DOLD_WXWIDGETS=ON

I only found out this by reading the script

I tried in Linux

cmake ..  -G "Unix Makefiles" -DBUILD_SHARED_LIBS:BOOL=OFF 
-DENABLE_f95:BOOL=OFF -DENABLE_tcl:BOOL=OFF -DENABLE_tk:BOOL=OFF 
-DCMAKE_INSTALL_PREFIX:PATH=/data/data127/pvicente/install/plplot-5.11.1do 
-DPL_HAVE_PTHREAD:BOOL=OFF -DPLD_xwin:BOOL=OFF -DPLD_wxwidgets:BOOL=ON 
-DwxWidgets_ROOT_DIR:PATH=/data/data127/pvicente/install/wxwidgets-3.1.0 
-DwxWidgets_LIB_DIR:PATH=/data/data127/pvicente/install/wxwidgets-3.1.0/lib 
-DwxWidgets_CONFIGURATION=mswud -DENABLE_MIX_CXX=ON 
-DwxWidgets_EXCLUDE_COMMON_LIBRARIES:BOOL=OFF 
-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DOLD_WXWIDGETS=ON >& cmake.txt &


and deprecated_wxPLplotDemo.cpp runs perfectly
It even has an option to change the background which is exactly what I 
needed

I have a request, would it be possible to have the "deprecated" 
wxWidgets code and the templated one at the same time?
This would allow us to try either one or the other without the need to 
recompiling with the -DOLD_WXWIDGETS flag.
I think some classes have the same name now in the old/new code, is 
that correct ?
If that's the case maybe you could give them different names

thanks much





 Original Message 
Subject: [Plplot-devel] Deprecated wxWidgets error
Date: 2016-12-09 14:39
 From: Pedro Vicente 
To: 

Hi Phil

Is the deprecated wxWidgets still functioning?

I gave it a try am I'm getting an error
This is Windows Visual Studio, wxWidgets 3.1, plplot 5.11.1

what I did

used the commented code in the sample wxPLplotDemo.cpp

that starts with

//class MyPlotwindow : public wxPLplotwindow

I did not run any cmake flag to use the old code (is there one?),
so my shortcut was to rename

deprecated_wxPLplotstream.h.in
to
deprecated_wxPLplotstream.h

and set this
#define WX_TEMP_PL_HAVE_FREETYPE_IS_@PL_HAVE_FREETYPE@
to either
#define WX_TEMP_PL_HAVE_FREETYPE_IS_ON
#define WX_TEMP_PL_HAVE_FREETYPE_IS_OFF

my error call stack is

wx_plplot.exe!plParseDrvOpts(DrvOpt * acc_opt) Line 1521C
wx_plplot.exe!plD_init_wxwidgets(PLStream * pls) Line 167   C++
wx_plplot.exe!plP_init() Line 144   C
wx_plplot.exe!c_plinit() Line 2341  C
wx_plplot.exe!plstream::init() Line 1008C++
wx_plplot.exe!wxPLplotstream::Create(wxDC * dc, int width, int
height, int style) Line 85  C++
wx_plplot.exe!wxPLplotstream::wxPLplotstream(wxDC * dc, int width,
int height, int style) Line 36  C++
wx_plplot.exe!wxPLplotwindow::wxPLplotwindow(wxWindow * parent, int
id, const wxPoint & pos, const wxSize & size, long style, int pl_style)
Line 60 C++
wx_plplot.exe!MyPlotwindow::MyPlotwindow(wxFrame * frame, wxWindow *
parent, int id, const wxPoint & pos, const wxSize & size, long style,
int pl_style) Line 58   C++
wx_plplot.exe!MyFrame::MyFrame(const wxString & title) Line 95  C++
wx_plplot.exe!wxAppPlot::OnInit() Line 210  C++



so the error comes from this function

plParseDrvOpts( DrvOpt *acc_opt )

and the exit is this code

if ( !fl )
  {
  snprintf( msg, sizeof ( msg ) - 1, "Option '%s' not
recognized.\n\nRecognized options for this driver are:\n", drvp->option
);
  plwarn( msg );
  plHelpDrvOpts( acc_opt );
  plexit( "" );
  }

where
drvp->option
is "backend" at this point


thanks

-- 
Pedro Vicente
pedro.vice...@space-research.org
http://www.space-research.org/

--
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

-- 
Pedro Vicente
pedro.vice...@space-research.org
http://www.space-research.org/

-- 
Pedro Vicente
pedro.vice...@space-research.org
http://www.space-research.org/

--
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