[GRASS-dev] 6.4.0 blocker bugs

[Michael Barton]

While I echo some of Helena's sentiments, I find that (surprisingly) even some of my students still prefer the TclTk interface of the wxPython one. That aside, it doesn't bother me if TclTk comes as a default on Mac and Linux, as this gives people a very smooth transition into the new GUI. They can easily turn it on as the default when they are ready, but they can start out with what they are more used to with prior versions. 

For MS Windows there really hasn't been a widely used prior version. So starting out with wxPython will make future updates easier.

Beyond this, the Mac version works fine. TclTk nviz is a richer environment than the embedded wxPython one. The wxPython digitizing module works well. AFAICT, the rest works fine too.

Michael
____________________
C. Michael Barton
Director, Center for Social Dynamics & Complexity 
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University

voice: 	480-965-6262 (SHESC), 480-727-9746 (CSDC)
fax:          480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu











On Aug 18, 2010, at 11:58 AM, Helena Mitasova wrote:

> 
> as Hamish has noted the choice of the default GUI is decided by whoever does the binary package (?).
> So my plea was pretty much for William to make wxGUI default in his Mac binary.
> People who run linux or compile GRASS from source are generally used to customizing so that is 
> not so much an issue. It is really for newcomers who download GRASS binary and start GRASS
> and then the first thing they have to deal with is to change GUI.
> The biggest issue that the newcomers had with the TclTk GUI (and that was solved in wxGUI) was 
> - "why the map is not displayed when I load it into gis manager?"
> All of this made starting with GRASS on Mac unexpectedly more difficult than on MSWindows.
> 
> At this point our semester has already started so I will have to deal with it , and if I understand
> the process correctly, 6.4 can be released with TclTk as default but with MSW and Mac binaries packaged 
> with wxGUI as default. Of course, I would much prefer if the release was with wxGUI as default. 
> 
> I don't have enough expertise on ctypes but we have troubles with it on our enterprise linux
> when compiling, but that is just a local problem,
> 
> Helena
> 
> 
> On Aug 18, 2010, at 2:29 PM, Markus Neteler wrote:
> 
>> On Wed, Aug 18, 2010 at 7:39 PM, Michael Barton <Michael.Barton at asu.edu> wrote:
>>> On Aug 17, 2010, at 11:24 PM, <grass-dev-request at lists.osgeo.org> <grass-dev-request at lists.osgeo.org> wrote:
>> ...
>>> 
>>> I have to agree with Hamish here. We have delayed for over a year. Getting GRASS to run robustly on Windows is worth it. But I'm not convinced that moving ctypes into 6.4 would be all that easy. Watching the issues for Windows compiling of GRASS 7 is worrisome in this regard. 6.4 works fine as is now. Let's release it and make it a bit better with 6.4.1
>> 
>> Please also post your opinion about (Mac, Linux):
>> - Release 6.4.0 with TclTK default GUI and switch in 6.4.1 to wxGUI as default;
>> - Do first RC7 with wxGUI as default, then release 6.4.0, don't change
>> with 6.4.1.
>> ?
>> 
>> Markus
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>