If we could get wxPython 3.x working for the GUI, we could switch all Mac compiling to 64bit. That would make LAS libraries MUCH easier to compile and bundle with GRASS. I've posted a 64bit version of GRASS 7.1 with wxPython 3.0.2.0 for people to test and report bugs. It mostly works fine. So it may not be a big deal to fix the few remaining issues.
Related to this, is there a plan to replace liblas with the new Python alternative (the name escapes me at the moment)? This would further simplify making robust LiDAR tools available in GRASS 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 Apr 30, 2016, at 5:59 AM, [email protected]<mailto:[email protected]> wrote: From: Vaclav Petras <[email protected]<mailto:[email protected]>> Subject: Re: [GRASS-dev] grass 7.2 planning Date: April 30, 2016 at 5:59:27 AM MST To: Martin Landa <[email protected]<mailto:[email protected]>> Cc: GRASS developers list <[email protected]<mailto:[email protected]>> On Sat, Apr 30, 2016 at 8:09 AM, Martin Landa <[email protected]<mailto:[email protected]>> wrote: > > 2016-04-29 15:09 GMT+02:00 Vaclav Petras > <[email protected]<mailto:[email protected]>>: > > > I have some things in lidar modules which would be good to do before the > > branching, namely changing the layer options to flag(s) and removal of > > vector output from r.in.lidar. Ideally, some code should go from modules to > > the library but that might not be feasible in the given time frame (from my > > side). The first week of May I can't promise any commits since I'm at FOSS4G > > NA [1] > > we can wait one week or so if you wish. Thanks. This would give at least some chance to get things straight. > > From things I remember, there is the prototype of Simple Python Editor which > > needs a review but you (Martin) already did some, so I guess that's fine. > > Yes, I used the editor in lessons. Nice tool! Thanks. It took me some time to discover that this is exactly what users want. > I had only one problem, > sometimes run button was not working (I discovered why after lesson) I focused on getting the basics working but the executing is just tricky. Will try to look at it as well to see if some substantial changes are needed.
_______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
