[GRASS-dev] wxGUI in GRASS 6.4.1

[Markus Metz]

Hamish wrote:
> Martin wrote:
>> wxGUI in GRASS 6.5 is mostly in sync with GRASS 7.0. In
>> opposite wxGUI in GRASS 6.4.0 has been frozen due to long
>> RC stage for one year and more. I am starting to think to
>> backport wxGUI from GRASS 6.5 to 6.4.1. What do you think
>> about that? It will bring new GUI features to 6.4.1 and make
>> live easier when backporting bug-fixes.
>
+1 from me for backporting

> 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
> me

For me neither. For 6.4.1, we could disable features known to not work
properly, as done already with the wx digitizer and wxnviz.
>
>
> 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.

> - 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.

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).

my 0.2c

Markus M