Please, someone, point me to the directory containing the ncurses code
interface. Again, I'm looking through directories, but I don't find just
where it's stored.
I've set myself the task of re-writing the CLI using the latest
ncurses-5.x and taking advantage of the panels, forms and menus. I also want
to expand the variable sizes for the data directory fields to accommodate
more than 14 chars.
This new interface will not be added to the CVS repository. I'm doing it
for me. Of course, once I get it all working -- and looking the way I want
it to look -- I'll make it available as a separate module for anyone who
wants it.
Thanks,
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Thu, Feb 22, 2001 at 07:20:30PM -0800, Rich Shepard wrote:
Please, someone, point me to the directory containing the ncurses code
interface. Again, I'm looking through directories, but I don't find just
where it's stored.
it is in src/libes/vask/
I've set myself the task of re-writing the CLI using the latest
Mhhh, what is "CLI"?
ncurses-5.x and taking advantage of the panels, forms and menus. I also want
to expand the variable sizes for the data directory fields to accommodate
more than 14 chars.
This new interface will not be added to the CVS repository. I'm doing it
for me. Of course, once I get it all working -- and looking the way I want
it to look -- I'll make it available as a separate module for anyone who
wants it.
Thanks,
Rich
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
> I've set myself the task of re-writing the CLI using the latest
Mhhh, what is "CLI"?
Command Line Interface. As opposed to tcl/tk and other GUI (Graphic User
Interfaces). That's what we see when we start GRASS in "text" mode.
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Fri, Feb 23, 2001 at 05:35:45AM -0800, Rich Shepard wrote:
On Fri, 23 Feb 2001, Markus Neteler wrote:
> it is in src/libes/vask/
Thank you.
> > I've set myself the task of re-writing the CLI using the latest
> Mhhh, what is "CLI"?
Command Line Interface. As opposed to tcl/tk and other GUI (Graphic User
Interfaces). That's what we see when we start GRASS in "text" mode.
I see (just the abbreviation was unclear to me).
You can see CLI at work in src/raster/r.agnps50/ if you need an
example.
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
You can see CLI at work in src/raster/r.agnps50/ if you need an
example.
Again, thanks, Markus.
I've grep'd the files in src/libes/vask/ and haven't found the names of
the variables used to store the input (GISDBASE. location and mapset). Is
there any guide in the programmer's manual to the organization of the start
up code and the user interface? I don't recall seeing that the last time I
looked.
I'll look at the tcl/tk code, too, and see if I can find these variable
names there.
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Fri, Feb 23, 2001 at 09:44:33AM -0800, Rich Shepard wrote:
On Fri, 23 Feb 2001, Markus Neteler wrote:
> You can see CLI at work in src/raster/r.agnps50/ if you need an
> example.
Again, thanks, Markus.
I've grep'd the files in src/libes/vask/ and haven't found the names of
the variables used to store the input (GISDBASE. location and mapset). Is
there any guide in the programmer's manual to the organization of the start
up code and the user interface? I don't recall seeing that the last time I
looked.
The vask library is just a simplified wrapper for curses. The GISDBASE,
LOCATION and MAPSET are written to the ~/.grassrc5 file. If you're
interested in the session start-up code, have a look in
src/general/init/, which among other things sets the environment
variables above. Also good to poke around src/libes/gis/ to see how
many things are handled regarding database management, I/O, etc... Don't
rely on the Programming manual. It's helpful, but doesn't document a
lot of stuff (some things just aren't documented).
I'll look at the tcl/tk code, too, and see if I can find these variable
names there.
It gets them from the environment...
--
Eric G. Miller <egm2@jps.net>
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
The vask library is just a simplified wrapper for curses. The GISDBASE,
LOCATION and MAPSET are written to the ~/.grassrc5 file. If you're
interested in the session start-up code, have a look in
src/general/init/, which among other things sets the environment
variables above. Also good to poke around src/libes/gis/ to see how
many things are handled regarding database management, I/O, etc... Don't
rely on the Programming manual. It's helpful, but doesn't document a
lot of stuff (some things just aren't documented).
Thank you, Eric. That's just the information I need.
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc. (TM)
Making environmentally-responsible mining happen. (SM)
--------------------------------
2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'
On Fri, Feb 23, 2001 at 07:45:05PM -0800, Eric G. Miller wrote:
On Fri, Feb 23, 2001 at 09:44:33AM -0800, Rich Shepard wrote:
> On Fri, 23 Feb 2001, Markus Neteler wrote:
>
> > You can see CLI at work in src/raster/r.agnps50/ if you need an
> > example.
>
> Again, thanks, Markus.
>
> I've grep'd the files in src/libes/vask/ and haven't found the names of
> the variables used to store the input (GISDBASE. location and mapset). Is
> there any guide in the programmer's manual to the organization of the start
> up code and the user interface? I don't recall seeing that the last time I
> looked.
The vask library is just a simplified wrapper for curses. The GISDBASE,
LOCATION and MAPSET are written to the ~/.grassrc5 file. If you're
interested in the session start-up code, have a look in
src/general/init/, which among other things sets the environment
variables above. Also good to poke around src/libes/gis/ to see how
many things are handled regarding database management, I/O, etc... Don't
rely on the Programming manual. It's helpful, but doesn't document a
lot of stuff (some things just aren't documented).
We should collect the missing stuff in a Programming manual "TODO".
Please send input or directly feed the
progmangrass50/TODO
(outside GRASS source code, inside CVS)
> I'll look at the tcl/tk code, too, and see if I can find these variable
> names there.
It gets them from the environment...
They are documented/listed here:
documents/envVars.txt
Markus
----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'