Periodically, there are complaints about ‘screen clutter’ with GRASS. I realized yesterday that a big cause of this is that each time a module is called, a new instance of its dialog opens. So if you use v.buffer but don’t close the dialog, and then call v.buffer again GRASS opens a second v.buffer dialog…and a third and a fourth, etc. So there seems to be the need to have the wxPython parser module to just bring the window for a module to the front if it is already open instead of opening another instance. Sounds simple but is probably somewhat complicated of course. But it would help the clutter problem a great deal.
Michael
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
Maybe we can modify the GUI preferences:
Default: All dialog boxes close after a run is complete
In Preferences: Tick this box if you want the dialog boxes to be closed manually (i.e. stay after a run)
something that direction might meet both edges.
From: grass-dev-bounces@lists.osgeo.org [grass-dev-bounces@lists.osgeo.org] on behalf of Michael Barton [michael.barton@asu.edu]
Sent: Thursday, May 24, 2012 3:49 PM
To: GRASS developers grass-developers
Subject: [GRASS-dev] reducing screen clutter
Periodically, there are complaints about ‘screen clutter’ with GRASS. I realized yesterday that a big cause of this is that each time a module is called, a new instance of its dialog opens. So if you use v.buffer but don’t close the dialog, and then call v.buffer again GRASS opens a second v.buffer dialog…and a third and a fourth, etc. So there seems to be the need to have the wxPython parser module to just bring the window for a module to the front if it is already open instead of opening another instance. Sounds simple but is probably somewhat complicated of course. But it would help the clutter problem a great deal.
Michael
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
On 24/05/12 12:25, Chemin, Yann (IWMI) wrote:
Maybe we can modify the GUI preferences:
Default: All dialog boxes close after a run is complete
In Preferences: Tick this box if you want the dialog boxes to be closed
manually (i.e. stay after a run)
The tick box already exists, so you are suggesting to make closing the dialog the default ? I find it quite useful, especially for newbies, to have the dialog open and be able to correct wrong input, instead of having to fill the whole dialog out again... But I can confirm that it takes some teaching to make them aware of that feature and avoid that they open the same command ten times. 
Moritz
This is one way, but not exactly what I was talking about. In fact, sometimes it is very useful to keep a dialog box open to rerun the same module repeatedly with different parameters.
What I meant is that once it is open, GRASS should not open additional dialogs for the same module but simply reuse the one that is open. That way you never get 5 windows for v.distance, only 1--even if you leave it open.
Michael
On May 24, 2012, at 2:26 PM, Moritz Lennert wrote:
On 24/05/12 12:25, Chemin, Yann (IWMI) wrote:
Maybe we can modify the GUI preferences:
Default: All dialog boxes close after a run is complete
In Preferences: Tick this box if you want the dialog boxes to be closed
manually (i.e. stay after a run)
The tick box already exists, so you are suggesting to make closing the dialog the default ? I find it quite useful, especially for newbies, to have the dialog open and be able to correct wrong input, instead of having to fill the whole dialog out again... But I can confirm that it takes some teaching to make them aware of that feature and avoid that they open the same command ten times. 
Moritz
_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
True that having the same dialogue open several times can be annoying. But not always, it may come in handy if you want to run the same module several times with different parameters (run at the same time, or prepare one while the other is still running; btw, I actually never checked how it is handled if you run the same function twice in parallel, are they run at the same time on different cores?).
On Thu, May 24, 2012 at 4:18 PM, Michael Barton <Michael.Barton@asu.edu> wrote:
This is one way, but not exactly what I was talking about. In fact, sometimes it is very useful to keep a dialog box open to rerun the same module repeatedly with different parameters.
What I meant is that once it is open, GRASS should not open additional dialogs for the same module but simply reuse the one that is open. That way you never get 5 windows for v.distance, only 1–even if you leave it open.
Michael
On May 24, 2012, at 2:26 PM, Moritz Lennert wrote:
On 24/05/12 12:25, Chemin, Yann (IWMI) wrote:
Maybe we can modify the GUI preferences:
Default: All dialog boxes close after a run is complete
In Preferences: Tick this box if you want the dialog boxes to be closed
manually (i.e. stay after a run)
The tick box already exists, so you are suggesting to make closing the dialog the default ? I find it quite useful, especially for newbies, to have the dialog open and be able to correct wrong input, instead of having to fill the whole dialog out again… But I can confirm that it takes some teaching to make them aware of that feature and avoid that they open the same command ten times.
Moritz
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
This sounds like a familiar problem. Most file/web
browsers let the choose whether to stay in the same
window or open a new one when browsing to a new
location.
So perhaps there should be an option in the GUI to
"allow multiple windows per module" which could be
set to "false" by default?
Ben
On 05/24/2012 05:34 PM, Paulo van Breugel wrote:
True that having the same dialogue open several times can be annoying.
But not always, it may come in handy if you want to run the same module
several times with different parameters (run at the same time, or
prepare one while the other is still running; btw, I actually never
checked how it is handled if you run the same function twice in
parallel, are they run at the same time on different cores?).
On Thu, May 24, 2012 at 4:18 PM, Michael Barton <Michael.Barton@asu.edu
<mailto:Michael.Barton@asu.edu>> wrote:
This is one way, but not exactly what I was talking about. In fact,
sometimes it is very useful to keep a dialog box open to rerun the
same module repeatedly with different parameters.
What I meant is that once it is open, GRASS should not open
additional dialogs for the same module but simply reuse the one that
is open. That way you never get 5 windows for v.distance, only
1--even if you leave it open.
Michael
On May 24, 2012, at 2:26 PM, Moritz Lennert wrote:
> On 24/05/12 12:25, Chemin, Yann (IWMI) wrote:
>> Maybe we can modify the GUI preferences:
>>
>> Default: All dialog boxes close after a run is complete
>> In Preferences: Tick this box if you want the dialog boxes to be
closed
>> manually (i.e. stay after a run)
>
> The tick box already exists, so you are suggesting to make
closing the dialog the default ? I find it quite useful, especially
for newbies, to have the dialog open and be able to correct wrong
input, instead of having to fill the whole dialog out again... But I
can confirm that it takes some teaching to make them aware of that
feature and avoid that they open the same command ten times.
>
> Moritz
_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: http://www.public.asu.edu/~cmbarton
<http://www.public.asu.edu/~cmbarton>, http://csdc.asu.edu
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org <mailto:grass-dev@lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Benjamin Ducke
{*} Geospatial Consultant
{*} GIS Developer
benducke@fastmail.fm
So long as this does not impair my ability to process the same command for multiple data layers in multiple ways simultaneously.....
Doug
Doug Newcomb
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb@fws.gov
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.
-----grass-dev-bounces@lists.osgeo.org wrote: -----
To: GRASS developers grass-developers <grass-dev@lists.osgeo.org>
From: Michael Barton <michael.barton@asu.edu>
Sent by: grass-dev-bounces@lists.osgeo.org
Date: 05/24/2012 05:19AM
Subject: [GRASS-dev] reducing screen clutter
Periodically, there are complaints about 'screen clutter' with GRASS. I realized yesterday that a big cause of this is that each time a module is called, a new instance of its dialog opens. So if you use v.buffer but don't close the dialog, and then call v.buffer again GRASS opens a second v.buffer dialog...and a third and a fourth, etc. So there seems to be the need to have the wxPython parser module to just bring the window for a module to the front if it is already open instead of opening another`` instance. Sounds simple but is probably somewhat complicated of course. But it would help the clutter problem a great deal.
Michael
_____________________
C. Michael Barton
Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research &
University Consortium for Atmospheric Research
303-497-2889 (voice)
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
www: [http://www.public.asu.edu/~cmbarton](http://www.public.asu.edu/~cmbarton), [http://csdc.asu.edu](http://csdc.asu.edu)
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
[http://lists.osgeo.org/mailman/listinfo/grass-dev](http://lists.osgeo.org/mailman/listinfo/grass-dev)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 24/05/12 17:57, Benjamin Ducke wrote:
This sounds like a familiar problem. Most file/web browsers let the choose whether to stay in
the same window or open a new one when browsing to a new location.
So perhaps there should be an option in the GUI to "allow multiple windows per module" which
could be set to "false" by default?
This would be a good (and intuitive) suggestion.
Cheers,
Rainer
Ben
On 05/24/2012 05:34 PM, Paulo van Breugel wrote:
True that having the same dialogue open several times can be annoying. But not always, it may
come in handy if you want to run the same module several times with different parameters (run
at the same time, or prepare one while the other is still running; btw, I actually never
checked how it is handled if you run the same function twice in parallel, are they run at the
same time on different cores?).
On Thu, May 24, 2012 at 4:18 PM, Michael Barton <Michael.Barton@asu.edu
<mailto:Michael.Barton@asu.edu>> wrote:
This is one way, but not exactly what I was talking about. In fact, sometimes it is very
useful to keep a dialog box open to rerun the same module repeatedly with different
parameters.
What I meant is that once it is open, GRASS should not open additional dialogs for the same
module but simply reuse the one that is open. That way you never get 5 windows for
v.distance, only 1--even if you leave it open.
Michael
On May 24, 2012, at 2:26 PM, Moritz Lennert wrote:
On 24/05/12 12:25, Chemin, Yann (IWMI) wrote:
Maybe we can modify the GUI preferences:
Default: All dialog boxes close after a run is complete In Preferences: Tick this box if
you want the dialog boxes to be
closed
manually (i.e. stay after a run)
The tick box already exists, so you are suggesting to make
closing the dialog the default ? I find it quite useful, especially for newbies, to have the
dialog open and be able to correct wrong input, instead of having to fill the whole dialog
out again... But I can confirm that it takes some teaching to make them aware of that feature
and avoid that they open the same command ten times.
Moritz
_____________________ C. Michael Barton Visiting Scientist, Integrated Science Program
National Center for Atmospheric Research & University Consortium for Atmospheric Research
303-497-2889 (voice)
Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human
Evolution & Social Change Arizona State University www: http://www.public.asu.edu/~cmbarton
<http://www.public.asu.edu/~cmbarton>, http://csdc.asu.edu
_______________________________________________ grass-dev mailing list
grass-dev@lists.osgeo.org <mailto:grass-dev@lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________ grass-dev mailing list
grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+/OAYACgkQoYgNqgF2egoOywCdHAl1MxCI4Fi4Ituw2IDQL5TU
0r4An3TpuTLw2450rv56I9i9U4hh9vL2
=FSsI
-----END PGP SIGNATURE-----