Hi,
2008/2/12, Hamish [EMAIL PROTECTED]:
Paul Kelly wrote:
Yes, and don't all the new features include many usability
improvements and feature enhancements to the Tcl/TK GUI parts
since the last stable release? I would worry that with all the talk
about wxgui these are going to be a bit
On Feb 11, 2008, at 11:41 PM, [EMAIL PROTECTED] wrote:
Date: Mon, 11 Feb 2008 18:53:13 -0800 (PST)
From: Hamish [EMAIL PROTECTED]
Subject: Re: [GRASS-dev] Re: include wxgrass or not in 6.3.0
To: Paul Kelly [EMAIL PROTECTED]
Cc: grass-dev@lists.osgeo.org
Message-ID: [EMAIL PROTECTED]
Content
Hi,
2008/2/11, Hamish [EMAIL PROTECTED]:
Martin:
http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS#Issues
to quote that here:
-
Issues
1. rename $GISBASE/etc/wx to $GISBASE/etc/wxpython
done, http://trac.osgeo.org/grass/changeset/30075,
Hi,
2008/2/11, Martin Landa [EMAIL PROTECTED]:
[snip]
4. write g.gui module (draft)
g.gui now in trunk (not compiled by default)
5. copy wxgui script to $GISBASE/etc/wxpython (not to
$GISBASE/scripts)
I think we can do this step too (before 6.3.0/1), just to test now g.gui module.
(I have taken liberty to replace the funky
Re: [GRASS-dev] Re: grass-dev Digest, Vol 22, Issue 33
subject)
On Feb 9, 2008 7:40 PM, Michael Barton [EMAIL PROTECTED] wrote:
On Feb 9, 2008, at 5:58 AM, [EMAIL PROTECTED] wrote:
From: Martin Landa [EMAIL PROTECTED]
2008/2/9, Martin Landa
I'd suggest having the *good* wxPython code included, no change to
configure. Without the configure change, it does no harm to the
existing code and can be ignored if desired. For people who want to
try it, it would be there.
Michael
C. Michael Barton, Professor of
Hi,
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
unfortunately, it has been included, even worse the old wxPython code!! see
http://trac.osgeo.org/grass/browser/grass/tags/release_20080109_grass_6_3_0RC4/gui/wxpython
Strange. In my local copy it isn't present.
I also checked the
On Feb 10, 2008 5:59 PM, Martin Landa [EMAIL PROTECTED] wrote:
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
unfortunately, it has been included, even worse the old wxPython code!!
see
http://trac.osgeo.org/grass/browser/grass/tags/release_20080109_grass_6_3_0RC4/gui/wxpython
tar
Hi,
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
On Feb 10, 2008 5:59 PM, Martin Landa [EMAIL PROTECTED] wrote:
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
unfortunately, it has been included, even worse the old wxPython code!!
see
Hi,
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
On Feb 10, 2008 5:59 PM, Martin Landa [EMAIL PROTECTED] wrote:
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
unfortunately, it has been included, even worse the old wxPython code!!
see
Hi,
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
On Feb 10, 2008 6:59 PM, Martin Landa [EMAIL PROTECTED] wrote:
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
On Feb 10, 2008 5:59 PM, Martin Landa [EMAIL PROTECTED] wrote:
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
unfortunately,
Right. I agree.
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution Social Change
Center for Social Dynamics Complexity
Arizona State University
Phone: 480-965-6262
Fax: 480-965-7671
www: www.public.asu.edu/~cmbarton
On
On Feb 10, 2008 6:59 PM, Martin Landa [EMAIL PROTECTED] wrote:
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
On Feb 10, 2008 5:59 PM, Martin Landa [EMAIL PROTECTED] wrote:
2008/2/10, Markus Neteler [EMAIL PROTECTED]:
unfortunately, it has been included, even worse the old wxPython
correction: Should be wxGUI included in 6.3.0?
From my point of view: -0
So:
6.3.x - no wxgui
6.4.x - wxgui included
I think that wxPython GUI *should* be included in 6.3.0.
Markus:
What about doing it in 6.3.1? We had 4 release candidates now and
it wasn't
Markus:
Copying over wxpython from SVN trunk would work without extra
changes in other places? Then it should not harm...
Michael:
Right. I agree.
Including it is fine with me then.
Hamish
On Feb 10, 2008 9:09 PM, Martin Landa [EMAIL PROTECTED] wrote:
2008/2/10, Hamish [EMAIL PROTECTED]:
...
Apparently removing old wxpython stuff from releasebranch6_3 before
releasing 6.3.0 was mistake. This code has been included in all RC's.
I am afraid there is no good solution.
* to re-add
Hi,
2008/2/10, Hamish [EMAIL PROTECTED]:
[snip]
Markus:
What about doing it in 6.3.1? We had 4 release candidates now and
it wasn't included. I would like to see at least one RC with that
included before officially publishing it.
I agree.
Martin:
unfortunately, it has been
Martin:
http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS#Issues
to quote that here:
-
Issues
1. rename $GISBASE/etc/wx to $GISBASE/etc/wxpython
2. rename switch 'wx' to 'wxpython', e.g. grass63 -wxpython, g.gui
type=wxpython
3. rename 'wxgrass' script to 'wxgui' (this
On Feb 10, 2008, at 4:31 PM, Hamish wrote:
Martin:
http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS#Issues
to quote that here:
-
Issues
1. rename $GISBASE/etc/wx to $GISBASE/etc/wxpython
2. rename switch 'wx' to 'wxpython', e.g. grass63 -wxpython, g.gui
Michael Barton wrote:
I (and a few students here) are using the wxPython GUI as is right
now, without worrying about issues 1-5. I agree that these should be
fixed. I guess I don't see them as a hold up to including it in
6.3.0.
I am not worried *at all* about the actual coding quality,
20 matches
Mail list logo
