Florent, I'm not sure we really want to duplicate existing constants.
I like that the bindings look similar in languages. If I must do GDAL code in C, C++, Java or Python, it's pretty much all the same everywhere... But the truth is that most non C/C++ folks hate their GDAL bindings, whatever the language. Python'ists hate the Python bindings because they don't look like Python. Java'ist the samthing. etc... What about just improving the doc... ? In the GDAL source tree, there's a huge file swig/java/javadoc.java that contain all the javadoc comments that appear in gdal.org/java There's a hacky script, swig/java/make_doc.sh, that extracts comments from javadoc.java and put them into the SWIG generated java files, so that the javadoc utility can make sense of all that. The generated docs are in swig/java/java. You could add missing javadoc for non documented constants, and improving existing doc, for example by mentionning which constants can be used as a parameter of a method. For a GDAL 2.0, we could perhaps split the gdalconst module into several ones to replicate what you've done in a more straightforward way and that would also benefit to other languages. Even > Hi all, > > Gdal is a very powerfull project and I use the Java binding. However, even > with the Javadoc, sometimes I need to read the source of the project to > understand how it works. That's why I try to make a parser to help people > (and me) to use Gdal with Java. > > The question is I don't really know how to publish my code. Because it's > all based on Gdal, is it possible to publish it on your SVN or do i need to > make a project on Github or Sourceforge ? > > The first step of my project is to organize gdal constants in enum : I put > all constants of the same type (color interpretation, error type, data > type, ...) in one enum class. I took all comments from the Javadoc (when > they were available). Here the sources. > > I need some advices to improve the code and comments, and maybe how to > organize my whole project. Next I will to list all drivers in enum or maybe > to create a class for each driver. > > Florent -- Geospatial professional services http://even.rouault.free.fr/services.html _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
