The main novelty of this version is its new architecture. The way gvSIG manage the data sources has been redesigned with the objective of improving the reliability as well as the modularity, benefiting the users as well as the developers.
The main differences between gvSIG 1.x and 2.x versions are explained at the webinar given in May 7th 2013, and at the presentation given at the 7th International gvSIG Conference (both in Spanish at the moment).
However this new gvSIG Desktop version includes a series of new features:
Nevertheless it's the last version of gvSIG, it has to be taken into account that it's really a new gvSIG, so you will find that some of the gvSIG 1.12 functionalities are not included. These functionalities will be included in following and continuous updates according to their migration to the new architecture. The main functionalities that are not included are the following:
In the same way, there are several projects based on this new architecture that will allow to include new functionalities and improvements directly in gvSIG 2.0 in the next months.
In addition, this version is not translated completely to every language. These translations will be published in following updates, after solving some aspects in the source code.
Also it has to be taken into account that the level of stability of this new version is not as high as we would have wished, considering it a final version in order to be used by the community in an official way, and mainly to tackle the new developments on it.
For that, we encourage you to test it and send us any errors in order to fix them in the following updates. The known errors of this version can be consulted in http://gvsig.org/r?r=bugs200.
gvSIG 2.0:
gvSIG 2.0 rc4 (25-01-2013)
The following errors have been corrected.
gvSIG 2.0 rc3 (27-12-2012)
The following errors have been corrected.
gvSIG 2.0 rc2 (14-12-2012)
The following errors have been corrected.
gvSIG 2.0 rc1 (27-11-2012)
The following errors have been corrected.
gvSIG 2.0 beta1 (11-10-2012)
The following errors have been corrected.