I agree with Martin and the rest. Backporting is a good idea. It will make for a better final GRASS 6 (i.e., whatever 6.5 becomes) and it will be minimal disruption to users since we already made the wxPython GUI the default at the last minute for 6.4.0.
+1 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 Oct 13, 2010, at 10:23 PM, <[email protected]> wrote: > Date: Wed, 13 Oct 2010 21:12:07 +0200 > From: Martin Landa <[email protected]> > Subject: Re: [GRASS-dev] wxGUI in GRASS 6.4.1 > To: Markus Metz <[email protected]> > Cc: GRASS developers list <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > 2010/10/13 Markus Metz <[email protected]>: >>> For my 2c, I don't object to backporting it (I sort of expected >>> we would do GUI updates in the 6.4.x line) but again I'll mention >>> that 'File->Quit GRASS completely' has never worked properly for > > right, removed in r43887 > >>> Backporting means >>> - throwing away that year of testing and restarting the testing >>> cycle. (not completely of course, but not without risk either) >> >> Hmm, I think that any wxGUI-related bugs are rather fixed in the 6.5 >> GUI than in the 6.4 GUI. Major and critical bugs have been backported, >> but minor bugs may not have made it into 6.4. > > MarkusM is right. > >>> - bad luck for anyone who already started on writing courseware, >>> tutorials, or books for GRASS 6.4. Since we are so soon after >>> original release we may get away without too much damage on that. >>> I am not so worried about backwards compatibility otherwise, as >>> GUI changes will not harm user scripts and the C/Python APIs. >>> >> My impression is that the look and feel of the 6.5 wxGUI is very >> similar to the 6.4 wxGUI, although quite a bit has changed under the >> hood; therefore I think this would not be a complete disaster for any >> courseware, tutorials, or books. > > I also agree with Markus here. > >> The problem I see is with translations, I don't know how much of the >> 6.5 wxGUI has been translated to how many languages, and I guess that >> the 6.4 wxGUI translations are often not working with the 6.5 wxGUI (I >> hope I'm wrong). > > Seems to be not so big problem. See comparison bellow (first 6.4, second 6.5). > > If you don't mind I will start with backporting wxGUI 6.5 to 6.4.1. > > Martin _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
