Also "xyz module www times faster than GRASS 6" is a relevant
information. Certainly not every new flag should be documented
on that page but the major improvements need to be listed.
Please help (editing possible with OSGeo ID),
thanks
Also "xyz module www times faster than GRASS 6" is a relevant
information. Certainly not every new flag should be documented
on that page but the major improvements need to be listed.
Please help (editing possible with OSGeo ID),
I have added links to the respective manual pages (in trac
much uglier than in Mediawiki but perhaps useful enough) and
made some cleanup.
I am not very good in catchy intro words, but I would mention the number of new modules (44+ vector, grass and image modules + general, GUI, etc modules) and some key improvements / enhancements of existing modules (like the very significant speed improvements in vector handling)?
I guess the links are made with some kind of alias? Would it be possible to not show the ‘G7:’ as part of all links?
One question about bash the scripts. it is mentioned that all bash scrips are converted to Python. Perhaps obvious, but these concerns the scripts that are part of the GRASS installation. One can still use external bash scripts (and hopefully that will remain the case). For example, most scripts available in the grass 6 add-on repository can be used in grass 7, albeit sometimes some adaptations are needed because of syntax changes)
Cheers,
Paulo
···
On 12/27/2012 04:39 PM, Markus Neteler wrote:
On Fri, Dec 7, 2012 at 1:55 PM, Markus Neteler [<neteler@osgeo.org>](mailto:neteler@osgeo.org) wrote:
Hi all,
a lot has happened in the past months in GRASS 7 with tons of
improvements: To better showcase the improvements, please
help to update
[http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures](http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures)
Also "xyz module www times faster than GRASS 6" is a relevant
information. Certainly not every new flag should be documented
on that page but the major improvements need to be listed.
Please help (editing possible with OSGeo ID),
I have added links to the respective manual pages (in trac
much uglier than in Mediawiki but perhaps useful enough) and
made some cleanup.
Some catchy intro words would be cool!
Please edit the page, it's a wiki!
Markus
Markus
_______________________________________________
grass-dev mailing list
[grass-dev@lists.osgeo.org](mailto:grass-dev@lists.osgeo.org)
[http://lists.osgeo.org/mailman/listinfo/grass-dev](http://lists.osgeo.org/mailman/listinfo/grass-dev)
On Fri, Dec 28, 2012 at 2:46 PM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
Nice work Markus!
Thanks but it is joint work
I am not very good in catchy intro words, but I would mention the number of
new modules (44+ vector, grass and image modules + general, GUI, etc
modules) and some key improvements / enhancements of existing modules (like
the very significant speed improvements in vector handling)?
Yes, definitely.
I guess the links are made with some kind of alias? Would it be possible to
not show the 'G7:' as part of all links?
I would be more than pleased but trac has no clue about reasonable
links. We can simply take it out again, if too ugly.
Or move the page to Mediawiki.
Opinions?
One question about bash the scripts. it is mentioned that all bash scrips
are converted to Python.
Yes. Especially for portability reasons and speed.
Perhaps obvious, but these concerns the scripts
that are part of the GRASS installation. One can still use external bash
scripts (and hopefully that will remain the case).
Yes sure.
For example, most scripts
available in the grass 6 add-on repository can be used in grass 7, albeit
sometimes some adaptations are needed because of syntax changes)
OK, those links may not be pretty, but that is a minor issue if compared to the convenience of having those links there. So I would certainly keep them.
What are the plans for the Wiki vs trac? I see some articles are marked to be moved to trac (like the GRASS 7 ideas collection). What is supposed to go where (Wiki or Trac), Wiki for end-user relevant information, Trac for information more relevant for developers?
I can see some advantages in such a system, but there are bound to be cases where information is relevant for both developers and users. One example is the NewFeatures page. Especially the part about changes in libraries is mostly interesting for developers. However, all the module changes and new modules are highly relevant for the users (I guess there must be a lot of GRASS 7 users by now).
All in all, it seems to make sense to me to move the GRASS 7 ideas collection to Trac, and move the 'http://trac.osgeo.org/grass/wiki/Grass7/NewFeatures’ to the Wiki, or alternatively, give it an easy to find link on the front page of the Wiki (replace the link to GRASS 7 ideas collection in the Development box on the Wiki front page with a link to New Features perhaps).
Cheers
On Fri 28 Dec 2012 10:38:08 PM CET, Markus Neteler wrote:
On Fri, Dec 28, 2012 at 2:46 PM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
Nice work Markus!
Thanks but it is joint work
I am not very good in catchy intro words, but I would mention the number of
new modules (44+ vector, grass and image modules + general, GUI, etc
modules) and some key improvements / enhancements of existing modules (like
the very significant speed improvements in vector handling)?
Yes, definitely.
I guess the links are made with some kind of alias? Would it be possible to
not show the 'G7:' as part of all links?
I would be more than pleased but trac has no clue about reasonable
links. We can simply take it out again, if too ugly.
Or move the page to Mediawiki.
Opinions?
One question about bash the scripts. it is mentioned that all bash scrips
are converted to Python.
Yes. Especially for portability reasons and speed.
Perhaps obvious, but these concerns the scripts
that are part of the GRASS installation. One can still use external bash
scripts (and hopefully that will remain the case).
Yes sure.
For example, most scripts
available in the grass 6 add-on repository can be used in grass 7, albeit
sometimes some adaptations are needed because of syntax changes)