<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 9, 2014 at 6:26 PM, Mojca Miklavec <span dir="ltr"><<a href="mailto:mojca@macports.org" target="_blank">mojca@macports.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
<br>
I'm sorry, but I forgot my password.<br>
<br>
I wanted to reply to this ticket:<br>
<a href="http://trac.osgeo.org/grass/ticket/2167" target="_blank">http://trac.osgeo.org/grass/ticket/2167</a><br>
but I'm sending you an email as figuring out how to recover the<br>
password will take a while and then I'll forget to update the ticket<br>
etc.<br>
<br>
Yes, wxPython 2.8 *works* on OS X 10.9, but only if someone compiles<br>
it for you (if you download binaries from somewhere else) and even<br>
then it's some kind of a pain because Python needs to be started in<br>
32-bit mode and all the dependencies need to be fixed properly etc.<br>
etc. One cannot compile wxPython 2.8 on 64-bit mac and so GRASS<br>
*cannot* work on MacPorts (which compiles everything from source) or<br>
with any other package manager that might support GRASS (I didn't<br>
check if other package managers support it or not).<br>
<br>
Basically it boils down to this:<br>
<a href="http://lists.osgeo.org/pipermail/grass-dev/2013-January/061635.html" target="_blank">http://lists.osgeo.org/pipermail/grass-dev/2013-January/061635.html</a><br>
Citing the user criticising the usage of wxPython:<br>
<br>
> I'm a mac user as well and i will be happy to help,<br>
><br>
> … i built grass weekly (if not daily) in the past,<br>
> but unfortunately now i'm on mac 10.8.x using 64bit python,<br>
> all my python packages numpy scipy etc etc etc .. are 64 bit and ...<br>
><br>
> WX gui unfortunately doesn't works on mac in 64 bit mode …<br>
> i'm waiting the 2.9.x to be stable that is 2 years now ...<br>
><br>
> This IMO can be one of the major reason of "lack of mac-man-dev-power"<br>
<br>
There have been a lot of bug reports about problems with Grass in<br>
MacPorts, but if users aren't able to use software at all, they go<br>
away, switch the OS, find other software etc. So users are lost.<br>
<br>
<br>
> I have Mac OS X 10.9 where GRASS runs with wxPython 2.8.<br>
<br>
Yes. But you need to fetch binaries from elsewhere and install all the<br>
dependencies yourself, manually. That's not acceptable for MacPorts<br>
and other package managers.<br>
<br>
> Besides, GRASS 6.4 and 7 should work with wxPython 3,<br>
> although it's not well tested and you can expect some problems<br>
> which can be fixed when someone reports them.<br>
<br>
The tickets asks for fixing these problems exactly. Grass 6.4.3 keeps<br>
causing constant problems with wxPython 3.0, at least on Mac it's<br>
nearly useless. I didn't test the nightly yet, but to be honest I'm<br>
not even sure how to use the software, so there's not much I can test.<br>
It asks for a file. I don't have any file to start with, so it's a bit<br>
difficult. I was just trying to fix some build problems in MacPorts,<br>
I'm not really a GRASS user.<br></blockquote><div><br></div><div>I don't really have time to fix the problems in GRASS 6.4 GUI, the code differs a lot from GRASS 7 where all the development now goes on and hopefully there will be some stable release soon. I always try to fix the problems related to wxPython 3 there as long as someone reports them. And I would say that wxGUI in G7 mostly works, but I tested it only on Linux. I would like to try it on Mac too but I don't have much time, that's the main problem. I understand it's difficult to test GRASS for you, the quickstart [1] is not exactly quick and you have to download the sample data first.</div>
<div><br></div><div>Anna</div><div><br></div><div><br></div><div>[1] <a href="http://grass.osgeo.org/grass70/manuals/helptext.html">http://grass.osgeo.org/grass70/manuals/helptext.html</a></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
(And I wasn't too serious about Phoenix. Yes, it make sense to take a<br>
look, but it's not a huge priority at the moment.)<br>
<span class=""><font color="#888888"><br>
Mojca<br>
</font></span></blockquote></div><br></div></div>