FWIW, the plot.py patch is easy to apply. If this is the only one that we really need, then we can fix 3.02 and use that. But I agree that this is disappointing news.
Michael
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
On Jul 14, 2016, at 12:00 PM, grass-dev-request@lists.osgeo.org wrote:
From: Martin Landa <landa.martin@gmail.com>
Subject: Re: [GRASS-dev] [wxPython-users] 3.0.3 ?
Date: July 14, 2016 at 11:49:13 AM MST
To: wxpython-user <wxpython-users@googlegroups.com>
Cc: GRASS developers list <grass-dev@lists.osgeo.org>
Hi,
2016-07-14 20:26 GMT+02:00 Dietmar Schwertberger <maillist@schwertberger.de>:
Is Phoenix an option for you?
Douglas is currently doing a lot of work on lib.plot for Phoenix.
Maybe you should test the latest snapshot whether the fix is in already. If
not, please comment on the pull request at
https://github.com/wxWidgets/Phoenix/pull/117may be, I was speaking with one colleague of mine, she mentioned that
Phoenix probably lacks PseudoDC. This would be absolute blocker for
us. We use PseudoDC for rendering data. There is also question how
much time it can take to get Phoenix into distributions like Debian. I
would vote for releasing classic as it is now as 3.0.3 at least.Or is Phoenix not an option?
Then it might be the best to take the classic version, apply the patch and
build it yourself.Hm, we are trying to support wide range of platforms. It’s impossible
for us to build every dependency on our own, sorry. We must relay on
official packages.I’m not aware of plans for a new build.
That’s VERY VERY bad news for us
Martin
–
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
