Michaël Michaud a écrit : > I think that a good priority list could be : > - bug fixes > - raster support (don't know if there are blocking issues as I don't use > it much) > - (if next version of JTS is released soon, synchronize both releases - > and drop the workaround we had to do in OJ) > In my previous list, I omitted 2 points : - language files (but I know Stefan takes a great care of them) - windows exe : I recently made a proposition based on winrun4j. I remember that several testers had problems to use it. I'll try to prepare a new .exe/.ini file and submit it on this list.
Michaël > Other points from Sunburned : > - nice to hear fixing bugs is one of your priority for june/july. Do not > underestimate the time it requires. > - if your plugins are independant from the core, maybe it should not be > a constraint for a OJ release date. Or do you need some modifications in > the core to release your plugins ? > > Other points from Stefan : > - I'm not sure CSV/txt plugin should be a priority as it is available as > a plugin. The only thing is that when installed, it is quite redundant > with the native WKT import/export. If you find time to give me some > feedback, I can find time to improve it either as a separate plugin or > to include it in the core. > - Pirol grid's creation tool : it seems that it is a long awaited > feature. It would be cool if it could be added to the next release. Also > it can be delivered as an external plugin. > - Improve OpenJUMP/Sextante compatibility to benefit Sextante great > algorithms : this is probably the most important point. I have a very > little experience. Last time I tried Sextante, I get many NPE, probably > due to small differences in the feature model. > *Can you explain a bit more what is the compatibility problem > between Sextante core classes and the one you started to include in > OpenJUMP. > *About bindings, there is still the sources on Sextante project > (lastly modified about 4 months ago). I suppose the bindings has to be > modified according to the work you did in OpenJUMP to include some of > Sextante classes ? > * About 1.5/1.6 issue : I think it would be cool to release a last > java 5 compatible version of OJ. It could be run on a java 5 jvm > (without Sextante). I'm not sure if we need to compile OpenJUMP with > java 6 to make it compatible with Sextante or can we release a java 5 > compatible OJ along with a java 6 compatible Sextante for users who > already have a java 6 jvm. > > my 2 cents > > Michaël > > > > Stefan Steiniger a écrit : > >> not sure. >> I can't make promises currently. I was planning to do a bit of OJ stuff >> in June and I would like to see i) Michaels CSV/txt plugin, some ii) >> Pirol grid creation tools, and iii) my recent raster-based developments >> included - i.e. stuff that I did based on the Sextante API (in >> particular converting images to vector grids). But with respect to what >> I have planned and accomplished the last 2 months, I am not sooo confident. >> >> I am also still unsure how to keep going with Sextantes Bindings... i.e. >> the problem is that we cannot cast between the classes transferred to >> OpenJUMP now (in a proper package path) and theirs if we want to use >> their libs/functions.. or is that possible? The point is that the >> Sextante Implementation is quite nice for the whole raster/vector >> processing thing, but >> a) it has a level of abstraction that we would not need for working with >> OpenJUMP only (so I selected only the raster classes so far to transfer >> them to OJ), and >> b) the bindings for OJ are not anymore available for download on the >> sextante page (if I remember correctly), since we should deliver those >> with OpenJUMP in future (a small issue here is also that Sextante is now >> distributed for Java 1.6 while we compile with 1.5). And believe me - >> sextante provides so much functions that we want to support it. >> >> just some thoughts, >> >> stefan >> >> Sunburned Surveyor wrote: >> >> >>> I've accumulated a list of about 7 or 8 bug fixes I want to do for >>> OpenJUMP. It looks like I may be able to make some time for this work >>> in June and July. I was wondering if we might shoot for a release of >>> OpenJUMP incorporating this work at the end of July. >>> >>> I've also done some work porting about 4 of my plug-ins from BizzJUMP >>> to OpenJUMP, and I'd like to release them at the same time. (They will >>> be separate plug-ins, and not part of the core.) >>> >>> If people are agreeable to this idea of a release at the end of July, >>> I will throw up a wiki page on SourceForge where we can coordinate our >>> progress on tasks for the release. >>> >>> Let me know what you think. >>> >>> The Sunburned Surveyor >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >>> >>> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> >> >> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > > ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
