Thanks Cesare for the usefull infos.<div>I've just finished setting up the development evnironment for Gvsig 1.11, so you can guess my decision :)</div><div>This version will help me to dig into the Gvsig API world, then I'll face the migration issues (if necessary).</div>
<div><br></div><div>Cheers,</div><div>Giovanni<br><br><div class="gmail_quote">2011/5/30 Cèsar Ordiñana <span dir="ltr"><<a href="mailto:cordinyana@gvsig.com">cordinyana@gvsig.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
El 23/05/11 12:54, G. Allegri escribió:<br>
<div><div></div><div class="h5">> I'm evaluating the possibility to develop an extension for gvsig. It<br>
> will take a while to be completed so I was wondering wether to<br>
> implement it on the actual release (gvsig 1.11) or the next one...<br>
> 1.12, or 2?<br>
> I know that many changes and improvements are being made to the<br>
> extensions mechanism, and in general to the various APIs. Some of them<br>
> have been merged, but I don't know the APIs enough yet to easily<br>
> understand if my extension would be affected by the changes in the<br>
> next future.<br>
> Could you help me to resume the status of the cahnges going on and if<br>
> there is a release rodmap for gvisg 2? In short, should I work on 1.11<br>
> or 2 APIs?<br>
> Thanks,<br>
> Giovanni<br>
<br>
</div></div>Hi Giovanni,<br>
<br>
gvSIG 2.0 has just started the stabilization process, and our plan is to<br>
release it in september. The APIs have been freezed since some time ago,<br>
so you can develep with it now if you can wait to september, your plugin<br>
should not be affected by API changes in the meanwhile.<br>
<br>
If you can't wait or need any of the plugins that won't be initially<br>
available when gvSIG 2.0 is released, you can develop for the 1.11<br>
version. It also should not be affected when the 1.12 becomes available,<br>
as only corrections and new functionalities are allowed, not API changes<br>
(unless absolutely needed).<br>
<br>
If you work with the 1.x APIs, you will have to make changes if you<br>
migrate it to the 2.0. How many will depend on which APIs you use, for<br>
example data access and persistence are new, but user interface related<br>
ones haven't changed much. If you already plan to do so, we have made a<br>
list of things to help in the migration:<br>
<br>
<a href="http://www.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/howto-migrate-projects-to-gvsig-2-0" target="_blank">http://www.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2.0.0/howto-migrate-projects-to-gvsig-2-0</a><br>
<br>
I would like to invite anyone who is or will migrate a plugin to gvSIG<br>
2.0 to share with us any instructions or tips he has used in the process<br>
so we can enrich the migration document.<br>
<br>
Regards.<br>
<br>
--<br>
Cèsar Ordiñana Navarro<br>
gvSIG software architect<br>
DiSiD Technologies (<a href="http://www.disid.com" target="_blank">http://www.disid.com</a>)<br>
<br>
<br>
_______________________________________________<br>
Gvsig_internacional mailing list<br>
<a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
<a href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional" target="_blank">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
</blockquote></div><br></div>