[GRASS5] Proposed process for GRASS reorganization (please read)

Malcolm Blue mblue at nb.sympatico.ca
Tue Mar 27 02:33:47 EST 2001


Have you tried?
Have you worked in a production environment?

I think that most grass users do appreciate the advantage of scripting 
and command line languages.  GUI is nice, but when working with large 
data sets I don't like to have to keep waiting for the last command to 
finish.  I like scripting when the job warrants and having the ability 
to switch to a GUI when I need to. 

 From your response, I guess you have no real experience.  I gather that 
you have no basis to judge either scripting or GUI.  Otherwise you could 
tell us why you feel this way. 

You lack credibility my friend. 

Malcolm.

strobe anarkhos wrote:

>> I would like grass to be different in a lot of ways, but most of all I want the functionality that grass provides now and the functionality proposed for the future.  Also, I don't want to lose any of the advantages that grass provides.  The ability to use the power of Unix scripting or a GUI interface as required, the ability to use multiple programming interfaces, the ability to interface grass with the countless other GPL software packages, etc. These are important to me, but might not be to everyone.
> 
> 
> GRASS's scripting and GUI are it's weakest features by far. The new model would make high level scripting a lot easier to implement and wouldn't have to rely on the command line. The GUI is so poor and the grassgui list so clueless I don't want to even talk about it.
> 
> ---------------------------------------- 
> If you want to unsubscribe from GRASS Development Team mailing list write to:
> minordomo at geog.uni-hannover.de with
> subject 'unsubscribe grass5'
> 
> 
> 


---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'



More information about the grass-dev mailing list