[GRASS-dev] WxPython prototype GRASS GUI. Version 2

[Michael Barton]

Agreeing with Yann, some kind of well-thought-out keyword structure could be
the basis for automatic menu generation at compile time or even runtime.

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


> From: Markus Neteler <neteler at itc.it>
> Date: Mon, 7 Aug 2006 21:37:22 +0200
> To: Grass Developers List <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] WxPython prototype GRASS GUI. Version 2
> 
> On Tue, Aug 08, 2006 at 02:03:29AM +0700, Yann Chemin wrote:
>> I'd like to think we can make a C code to automatically create a menu
>> description file instead of making it by hand all the time. If you
>> could separate it well from the other coding, it should make that task
>> easier when we'll come to it.
>> 
>> 
>> Additionally, since Python GUI does not need recompiling, it should
>> then be possible to generate "flavors" of GRASS, i.e. for image
>> processing or for GIS analysis, etc on the fly by modifying menu
>> contents.
>> 
>> Yann
> 
> I was always thinking of having a "keyword" section in the module/manual.
> Like this commands could be easily grouped (searched). Probably this
> could be also used for autogenerating such dedicated menus more easily.
> 
> Markus
> 
>