[Gvsig_english] gvSIG OADE 2010 with GRASS GIS support released

[Benjamin Ducke]

Hi Simon

----- Original Message -----
> Hi Ben,
> 
> Downloaded the package tried it. A couple of points...
> 
> 1. I was disappointed that the installer defaults to the home
> directory. Early
> versions of OADE put the file in the /opt directory, which I thought
> was better. Personally I think software should be kept out of the ~
> directory.
>

One of gvSIG OADE's hallmarks is that it is fully portable, i.e. can
be installed anywhere and does not require administrator rights for
this. Accordingly, it will not touch any system-wide settings and
won't try to install into system folders by default.

If you want a system-wide install, you can still do that by starting
the administrator as a super user and picking /opt, /usr/local or
watever suits you.
 
> 2. The program also tried to copy over the existing 'Beta' version.
> This is
> not very good, especially as this latest version attempts to convert
> the project file. I renamed my install directory to reflect that this
> version was
> actually based on gvSIG 1.10 rather than gvSIG 1.9.
> 

My real mistake was not to set the installation directory name of the
beta version to something different. But too late for regrets now.
Users will have to make sure to delete any existing files before
upgrading. Normally, it does not hurt to overwrite an older version.
The only exception is SEXTANTE, which may end up with duplicate
Java class files and then not start anymore.

I have put a not on our gvSIG support page:

http://oadigital.net/software/gvsigoade/gvsigbugs

Project file versions: see below.

> 
> 4. Everything appears to be OK but every time I get into the program
> and open
> an existing project, although no message appears, I get the following
> fatal error logs in the bin directory. These errors only appear when I
> use one of my
> existing converted files! If I create a new file from scratch (adding
> any number
> of raster files and shapefiles) no comparable error log is created. I
> even tried
> to recreate the original project file that 'failed' to convert by
> adding everything again to a new project file (attempting to simulate
> memory overload)
> but failed to reproduce the error.
> 

This baffles me a little. There is virtually no difference between
the "old" and "new" project files, except that gvSIG now writes
"1.10" into the version tag instead of "1.9". This was done to comply
with the changes in the new 1.10 beta release from CIT.

I have "converted" some fairly complex project files, but never had
this problem. If you want, you could try to manually change the version
tag value of your old project files so that gvSIG won't do any resaving
on them when you open them with the new version.

I will take a look at the log you sent me. Maybe I'll get some clue
out of it.

Best,

Ben

> *** Note that a log file was also passed onto Ben privately, as
> comments in the
> file may contain relevant data. I have not attached it to this reply
> to avoid
> its content being scanned by bots and appearing in search engines.
> Although not confidential, it may provoke some need for explanation if
> clients see file
> names appearing on the Internet searches. ***
> 
> -- Cheers Simon
> 
> Simon Cropper
> Botanicus Australia Pty Ltd
> PO Box 160 Sunshine 3020
> P: 03 9311 5822. M: 041 830 3437
> W: http://www.botanicusaustralia.com.au
> 
> _______________________________________________ Gvsig_internacional
> mailing list
> Gvsig_internacional at listserv.gva.es
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional


------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.