[GRASS-dev] FW: python gis manager concept

[Michael Barton]

Forgot to copy the developer list on this.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics and Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

------ Forwarded Message
> From: Michael Barton <michael.barton at asu.edu>
> Date: Fri, 02 Feb 2007 09:46:52 -0700
> To: Jáchym Čepický <jachym.cepicky at gmail.com>
> Conversation: python gis manager concept
> Subject: Re: python gis manager concept
> 
> Jachym,
> 
> If it helps, I've got events set so that clicking on any display will
> automatically bring up it's choicebook page. Selecting a choicebook page will
> also automatically select the appropriate display.
> 
> The notebook tab works just as well as a choicebook pull-down, with a little
> less effort as you point out. They function exactly the same, except for the
> interface (tabs vs. pulldown) for selecting a page. My only concern that
> prompted the choicebook was the space needed for tabs when multiple displays
> are opened. But realistically, most people probably won't open more than 2-3
> monitors at most.
> 
> I put the notebook page tabs (for layer or console control) on the side so as
> to keep them physically separated from the interface for selecting the
> display--for better visibility, maybe reducing control 'clutter' a bit, and to
> aid clumsy clickers. They could go on top if it works better.
> 
> I could easily go either way. It only takes changing one word in the line to
> start it (wx.Notebook <-> wx.Choicebook) to change it around--a nice part of
> working with wx.Python.
> 
> Michael
> 
> 
> On 2/2/07 9:24 AM, "Jáchym Čepický" <jachym.cepicky at gmail.com> wrote:
> 
>> hi,

2007/2/2, Michael Barton <michael.barton at asu.edu>:
> Jachym,
>
> I like
>> the concept and it is close to what I've been doing. I've attached a
>
>> screenshot of it. The main difference is that after consideration, I made
>
>> the choicebook (varient of notebook) for the display at the top of the
>
>> hierarchy and added a notebook with tree controls and console for a display
>
>> to each page. This seems easier to track controls for each display. My
>
>> earlier version looked more like yours. One nice thing about using a choice
>
>> book is that you don't have to worry about space for tabs as you add more
>
>> pages (i.e., displays).

I like the idea to have direct access to each
>> monitor. Yours approach
means that you have the double click - first at the
>> choice book and
than at the desired monitor... I would prefer the panel
>> approach also
because you can add "x" (close) button to the top of each
>> panel.

Maybe this is a topic for GRASS survey?

>
> I like the idea of a
>> command line at the bottom. This should make a lot of
> people happy too.

I
>> added your screenshot to the wiki [1] , so we can compare
side-by-side each
>> proposal and maybe  piece the best peaces from all
together.

Jachym

[1]
>> 
http://grass.gdf-hannover.de/wiki/GRASS_GUI#Screenshots_with_proposed_shapes
>>

>>> On 2/1/07 8:31 AM, "Jáchym Čepický" <jachym.cepicky at gmail.com> wrote:
>
> >
>> Hi,
> >
> > things are movig slowly forward. As you might know, I started to
>> write
> > some low-level code for rednering raster, vector, graph, wms,
>> ...,
> 
>>> layers into map image. The code is avaliable in GRASSSVN-Addons
> >
>> repository [1].
> >
> > I started also to think about the GIS-Manager
>> concept. 
>> I prepared some
> > "preview" using wxglade (this is not the best tool
>> thought) - you can
> > open the file gism.wxg (attached) in wxglade and play
>> with it a bit. I
> > send also the screenshot of this try attached to  this
>> e-mail.
> >
> > In this version of gism, menubar and tool bar are missing -
>> this is
> > not intention. What I wanted to present with this is the
>> notebook
> > concept  -- each display has it's own notebook panel in which
>> the
> > layer tree is stored.
> >
> > On the bottom of gismanager, GRASS
>> command line is ready for quick usage.
> >
> > What do you think about this
>> concept? Please feel free to redesign
> > this proposal and share your
>> ideas.
> >
> > I think, we should stop for a while to code and start to
>> discuss about
> > the future design. The current Tcl/Tk gis manager has shown
>> many
> > things and we should think about it's design for a while, before
>> we
> 
>>> start to rewrite it using python.
> >
> > Looking forward to your comments
>
>>> 
> > Jachym
> >
> > [1]
> >
>> 
https://grasssvn.itc.it/grasssvn/grassaddons/trunk/grassaddons/gui/#_trunk_gr>>
a
>> 
> > ssaddons_gui_
>
> __________________________________________
> Michael
>> Barton, Professor of Anthropology
> School of Human Evolution & Social
>> Change
> Center for Social Dynamics & Complexity
> Arizona State
>> University
>
> phone: 480-965-6213
> fax: 480-965-7671
> www:
>> http://www.public.asu.edu/~cmbarton
>
>
>
>
>


-- 
Jachym Cepicky
e-mail:
>> jachym.cepicky gmail com
URL: http://les-ejk.cz
GPG:
>> http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub

> 
> __________________________________________
> Michael Barton, Professor of Anthropology
> School of Human Evolution & Social Change
> Center for Social Dynamics and Complexity
> Arizona State University
> 
> phone: 480-965-6213
> fax: 480-965-7671
> www: http://www.public.asu.edu/~cmbarton

------ End of Forwarded Message