Martin,
the discussion here is not about whether to write NEW scripts as
shell scripts
but whether anybody who has many shell scripts will have to rewrite
them into Python to be able to run them in GRASS7. Imagine you have
20 old,
stable, well tested scripts doing complex workflows and a lot of new
work
to do, would you want to spend your time rewriting these old shell
scripts
into Python or rather develop new capabilities? Some scripts may be
worth
rewriting, some not. I think this is what Hamish had in mind.
BTW I am not the person who has lost of shell scripts so for me it
does not matter,
but there are many people who do.
It may slow down adoption of GRASS7 and people may prefer to stick with
GRASS6*, rather than rewrite.
just a few words to support Hamish's view,
Helena
On Jul 3, 2009, at 12:26 PM, Martin Landa wrote:
Hi,
2009/7/3 Hamish <hamis...@yahoo.com>:
In GRASS7 there is no extra support for shell scripts.
This is IMO a huge, huge mistake.
I do not claim that it shouldn't be possible to run shell scripts in
GRASS7. Most of the restrictions in our lives are bad at the end;-)
Anyway I highly suggest to write new scripts in Python, see [1].
Probably it's personal point of view, but writing shell scripts was
always pain for me and I can hardly imagine person (without previous
scripting experience) who prefers to learn how to write shell scripts
rather then to learn Python. Python is quite easy language to learn
for newcomers. Shell scripts are simply not good choice for writing
sometimes quite complicated GRASS scripts.
Martin
[1] http://download.osgeo.org/grass/grass6_progman/pythonlib.html
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
