[GRASS-dev] GUI platforms

[Michael Barton]

Yann

You can use the new GRASS Extensions Manager to make your code available to
others without having to recompile all of GRASS.

If your code is potentially may be integrated into the normally distributed
set of modules, the only things that those of us working on the GUI suggest
are...
1) Don't *require* interactive input via a terminal. That is, make it
possible to run your code by typing a command on the command line only.
Don't make it wait for subsequent user response to questions. This way, the
command for your code can be run from any scripting environment--including
bash or a GUI platform.

2) If your code needs to display anything, it should work through standard
GRASS display mechanisms, rather than independent calls to an X display
terminal (or any other specific display mechanism outside GRASS). This way,
as GRASS display libraries and functions change, your code will still be
able to display in multiple environments.

If your code is primarily for your use and will not be distributed with
GRASS or interact with GEM, you can do pretty much anything  you want.

Glynn, Cedric, anything else to add?

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: Yann Chemin <ychemin at gmail.com>
> Date: Wed, 24 May 2006 10:33:47 +0700
> To: <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] GUI platforms
> 
> Hello all,
> 
> I am practically a layman in terms of GUI programming,
> however i have made few C codes so far that i intend to "plug" into
> GRASS as modules.
> Most of them non-interactive, one will be interactive for sure.
> 
> The way GRASS is so far to include a new module is easy, modify a
> couple of text files, compile the module and you are done.
> I am willing to learn "THE" GRASS interface standard programming
> language that you all discuss about for many months now. But please
> make sure that we do not need something too complicated to get our
> "own" GRASS stuff done.
> 
> sincerely,
> Yann
> 
>