I understand the desire not to waste effort. However, it seems that it will still be some time before Phoenix is completely stable and we have code that works with it. Issues 1 and 2 seem to be easily fixable things in the current code. Are any other platforms using wxPython 3.0.2 yet? If so, do they have the same issues?
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 Jan 17, 2018, at 3:14 AM, Anna Petrášová <[email protected]<mailto:[email protected]>> wrote: Hi Michael and Eric, that's great indeed! What are the plans to document the entire process? Probably creating a GRASS wiki page? I would like to eventually switch to wxPython Phoenix, because I don't want to invest energy into fixing issues for wxpython 3 in case some of these things already work in Phoenix. The current state of wxGUI and Phoenix is that it roughly 90% of GUI works on Linux, if I remember correctly on Mac too, but I didn't have that much time to test it. Thank you, Anna On Tue, Jan 16, 2018 at 11:37 PM, Michael Barton <[email protected]<mailto:[email protected]>> wrote: Hi Helena, I am very glad that it works for you so easily. A HUGE thanks is owed to Eric Hutton of the Community Surface Dynamics Modeling System (CSDMS), an NSF facility and scientific network for modeling in the earth sciences. It was Eric's idea to try this through Anaconda. He provided guidance and I worked though a lot of testing it as an Anaconda build last summer, but was unable to get it to a point where GRASS could reliably be compiled and then distributed. Over the last couple months, Eric has worked out how to solve those problems, including making a launchable app and packaging it all in a dmg. There is a bit of fine tuning left to do in the workflow, but it is essentially distributable now--making it the first time I've been able to create a stable and easily installable binary in a year and a half. Parallel to this, Eric proposes (and has worked out the protocol) of also making GRASS available as an Anaconda package. He has created an Anaconda 'recipe' to do this. After getting the app/dmg distributed, I will follow his lead to test how this works as an alternative for those who use Anaconda for Python. This new build has a couple of characteristics quite different from previous Mac versions. Most importantly, all needed dependencies are bundled inside the app. This makes for a bigger app, but hopefully eliminates any conflicts among dependency versions. No more separately installed "frameworks". No more conflicts if you (or a program) install another version of Python or wxPython somewhere. And hopefully, no more issues with Apple's 'system integrity protection' (SIP). This test version does not include gettext for internationalization or libLAS. I wanted to test it as we've been developing the workflow, without adding anything else until I can confirm that it works. However, I think it will be easy to include gettext because there already is an Anaconda version available. LiDAR support may be trickier. I have previously compiled libLAS. I think it may be possible to work out how to link and bundle it in this Anaconda version. That said, there seems to be work in the dev team for substituting PDAL as a LiDAR support library, and Anaconda already supports PDAL. So if we can substitute PDAL functionality for libLAS functionality, we can do it all within an Anaconda environment. This is also a full 64 bit version of GRASS. No more need to compile it dual architecture 32/64 bit. This solves a number of compiling and running issues, and means that the GUI now must run in wxPython 3 and above (still Python 2.7). There are several GUI bugs that show up in switching from wxPython 2.8 to 3+. I've created tickets on the 3 I know of. The most annoying 2 of these should be pretty easy to solve for the people who are actively managing the GUI (the menu button bar does not properly revert back to 2D buttons after displaying 3D, and a custom pull-down list control does not recognize mouse clicks). I don't know if the 3rd one is easy or difficult to solve (the interactive supervised classification module crashes GRASS). Please feel free to distribute and get back in touch with me and Eric if you run into any issues. Cheers 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: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton&d=DwIFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=soaI1YnedAZn-bBIj8hBdwwQbPT6gkE2Ghh35K5Wcno&s=7aE7xW3GGw_2VoQncxTzK8k44D-5jjpMPESNe0qkyAQ&e=, https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu&d=DwIFaQ&c=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ&r=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0&m=soaI1YnedAZn-bBIj8hBdwwQbPT6gkE2Ghh35K5Wcno&s=88KAjNWJyflzwDgKb0vlpORWaPKZfyifl42YveYAaxc&e=
_______________________________________________ grass-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-dev
