Is there an index of those modules that are working and those that require further testing?
Ted Nebitko wrote:
Is there an index of those modules that are working and those that require
further testing?
No real index, but indications:
http://grass.gdf-hannover.de/wiki/WinGRASS_Current_Status
Feel free to add an index there.
Markus
--
View this message in context: http://www.nabble.com/-winGRASS--native-winGRASS-pre-alpha-testers-needed-tf4377512.html#a12493016
Sent from the Grass - Users mailing list archive at Nabble.com.
On 04/09/07 14:21, Ted Nebitko wrote:
Is there an index of those modules that are working and those that require further testing?
There is no such systematic index. What we know not to work at this stage:
- some modules dealing with attributes of vector data (confirmed for v.out.ogr, but others are affected): these work intermittently, but often cause deadlocks. We are currently busy trying to hunt down this bug.
- all d.* commands from the command line: there are no x-monitors in windows so none of these commands will work. All display has to happen within the GIS Manager gui.
- d.vect.thematic: this is a script which cannot easily be ported to windows as it uses d.mon commands.
- There might be other scripts that don't work.
The rest potentially works, but still needs extensive testing since whether a module works or not might depend on the parameters used.
Moritz
On 05/09/07 09:23, Markus Neteler wrote:
Ted Nebitko wrote:
Is there an index of those modules that are working and those that require
further testing?No real index, but indications:
http://grass.gdf-hannover.de/wiki/WinGRASS_Current_Status
Feel free to add an index there.
I actually think that this page needs serious revamping as at this stage it is quite chaotic and also not necessarily up-to-date. And yes, I know that I should probably be the one to revamp it. I'll try to find some time.
Moritz
In addition, GRASS shell scripts and modules should be checked
and hardened for cases where spaces may appear in file or directory names.
On a unix system, users generally don't store stuff in paths with
spaces, but Windows by its very design encourages this.
E.g. the user's home folder may well be something like
C:\Windows\Documents and Settings\Default User\
This can easily break scripts and modules that need to interact
directly with the filesystem, e.g. for reading and writing ASCII
files.
If the user installs the WinGRASS binaries into a path with spaces,
also something Windows encourages, there might be further sources of
trouble.
So I'd recommend to do just that: install WinGRASS into a dir with
spaces, create a GRASS mapset, also in a path with spaces, and
work from there to find all the vulnerable bits and pieces.
Benjamin
On 04/09/07 14:21, Ted Nebitko wrote:
Is there an index of those modules that are working and those that
require further testing?There is no such systematic index. What we know not to work at this stage:
- some modules dealing with attributes of vector data (confirmed for
v.out.ogr, but others are affected): these work intermittently, but
often cause deadlocks. We are currently busy trying to hunt down this bug.- all d.* commands from the command line: there are no x-monitors in
windows so none of these commands will work. All display has to happen
within the GIS Manager gui.- d.vect.thematic: this is a script which cannot easily be ported to
windows as it uses d.mon commands.- There might be other scripts that don't work.
The rest potentially works, but still needs extensive testing since
whether a module works or not might depend on the parameters used.Moritz
_______________________________________________
grassuser mailing list
grassuser@grass.itc.it
http://grass.itc.it/mailman/listinfo/grassuser