Hi Jorge, Joaquin, and Manuel: <br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">We've been discussing here Manuel, Joaquín and me and well, we think<br>
your approach is not the best way to improve the gvSIG code. When one<br>
needs to do changes or improvements on the code branching should be the<br>
last resource as you are taking the decision of work aside the rest of<br>
the developments, aren't you?<br>
<br>
IMHO it is more reasonable to try to improve the current code for<br>
everyone and maybe do some work to plug your work on a separate<br>
extension if it's only for the Mac distro.<br>
<br></blockquote><div><br>There are points where I cannot see a way, for example when loading ecw layers. At this moment we are using Gdal plugin to load this layers. gvSIG for linux and win uses a shared library present in the code. How would you face this problem? In the other side the ui changes could be sensible in other platforms, beacuse it could imply some dialog type changes. I am not supporting to branch the whole gvSIG, only a few projects, where the code is sensible to have impact over the other distributions. <br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Some time ago this kind of work was done to add flexibility to the<br>
documents gvSIG supports from the initial view/table/layout to add<br>
support for 3D documents (3d view and animation). Besides 3D, this work<br>
was nicely used at other developments (as the publishing extension)<br>
proving that the decision was perfectly right.<br></blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
For example, if you find a panel that is not well displayed on Mac,<br>
probably will be because the layout management of it is not well done.<br>
Do you think is better to just hack it to work on Mac right now or just<br>
improve it to the benefit of all the other platforms (present of<br>
future). I know it's more work, but the point here is doing the thing<br>
right or quick?<br>
<br></blockquote><div><br>As I said to you we will need to change some dialog types, and maybe we have to do changes that are sensible to other distributions. Where we can avoid to branch, we won't branch. And be sure that if we find a bug and is in our hand to send a patch we will do it. In fact we are sending patches already. <br>
<br>I think the real point is, in a short term (gvSIG 1.x), to have a distribution fully usable in Mac (yes, hacking code and whatever). And in a mid-long term (for gvSIG 2.x) to have a fully integrated and official Mac version. IMHO is a waste of time (of our spare time :) ) to do all this work in 1.x version. <br>
<br>The other point is that right now we are only two developers willing to collaborate, Rafa and me. So we think our target in a short term is to get a full usable version of gvSIG 1.x. The more developers join us, the better we can do this work. <br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Well my personal opinion is that OSOR wiki is quite crappy. I would<br>
recommend you to use Sphinx[1] so you write all your documentation in<br>
reStructuredText (wich is a great markup language). You can maintain all<br>
the docs at the SVN and then rsync the generated HTML to the static<br>
upload area of the project.<br>
<br></blockquote><div><br>Jorge you know I don't like osor too, If I proposed to use osor is to give a consistency with the rest of the project. There are a bunch of wiki frameworks and repository options that we can utilize, but it makes sense to do it in osor, or in the gvSIG plone. In fact you know I prefer to move to git, and this is not possible in osor. Anyway I will take a look to Sphinx. <br>
<br>I am agree with you to use RST. <br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
This is the way a lot of projects are moving their documentation systems<br>
(mapserver, geoserver, mapproxy, etc.) and you maintain the markup so<br>
uploading the documents in the future to the gvSIG portal would be<br>
easier.<br>
<br>
For the georesources project we did that[2][3] until we had the portal<br>
space and moving the docs was quick and easy[4].<br>
<br>
Best regards<br><br></blockquote></div><br>Finally, I want to encourage all the mac developers reading this thread to join us. Come on! <br><br>Cheers. <br clear="all"><br>-- <br>Jordi Torres Fabra<br><br>gvSIG 3D blog<br>
<a href="http://gvsig3d.blogspot.com">http://gvsig3d.blogspot.com</a><br>Instituto de Automática e Informática Industrial <br><a href="http://www.ai2.upv.es">http://www.ai2.upv.es</a><br>