Hi Stefan, Thanks for your detailed answers.
I still wonder if it is possible to integrate such driver as ecw/MrSid into the new framework as these drivers are based on read-only native code, but let's see. Now, you gave me good informations to investigate by myself. Michaël Le 02/10/2010 07:30, Stefan Steiniger a écrit : > Hei Michael, > > lets see if I can answer the questions: > >> You explained in a mail that these are two different tools : raster >> tools need raster loader and cannot work with images >> > correct >> Is this something definitive or do we have to migrate image loaders >> toward raster loader api in the future ? >> > I think(!) we could image migrate image loaders (i.e. the ones that work > with drag and drop). The original image loader interface was contributed > by Jon (code in vividsolutions.jump). Raster loader is based on the > Pirol code. >> Is it possible for such format as ecw to be loaded with raster loader ? >> > In theory yes... if we deal with a java image at the end. But.. thats > more or less an educated guess. However, the raster image loader loads > already png, jpg, tiff etc... so it would be more about adding mrsid and > ecw. > >> What is the main difference between both API, and what are the main >> classes to investigate if I want to learn from code ? >> > puh.. I need to check... > so...the (new) raster code is based on the classes in > org.openjump.core.rasterimage - the main classes are > AddRasterImageLayerWizard and RasterImageLayer and > OpenJUMPSextanteRasterLayer > > the image loader code is based on: > com.vividsolutions.jump.workbench.imagery, and > com.vividsolutions.jump.workbench.ui.plugin.imagery; > main class here is (I believe) AddImageLayerPlugIn > > and to your first question. Mhm i would say the main difference is that > the sextante framework is more flexible - i.e. it holds an abstract > image that can be manipulated and hence, provides functions for > imag/pixele manipulation - and access to individual pixels (also new > -empty- rasters can be created), while the image framework holds > non-modifiable images/rasters and one can not access individual raster. >> About naming of raster loader (mail subject), I would vote for not >> including Sextante name if the api and the raster menu do not need >> Sextante software to work. >> > thanx for your input on that. Yeah the latest version doesn't require > sextante libs anymore. And no worries about all the questions ;) > > now I am actually back in Calgary - for a bit (4 days). > > cheers, > stefan > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
