Paul,
That is a good tip. I'll add this information to my section of the
wiki on loading files in OpenJUMP. Thanks for implementing the
AbstractFileLayerLoader.
The Sunburned Surveyor
On Wed, Jun 11, 2008 at 11:12 AM, Paul Austin <[EMAIL PROTECTED]> wrote:
> Christopher,
>
> Have a look at the o
Christopher,
Have a look at the org.openjump.core.ui.io.file.AbstractFileLayerLoader
class for implementing a complete custom file loader.
You just have to implement the open(TaskMonitor monitor, URI uri,
Map options) method to do the actual Layerable creation.
If there are options the user
--- Sunburned Surveyor <[EMAIL PROTECTED]>
wrote:
> Let me know if you have more questions. I can help
> you with
> implementing a DataSource for TIN files if that's
> what you are
> currently working on.
>
> The Sunburned Surveyor
Hmmm, it looks like since I've gone the Layerable
route and byp
Christopher,
I just spent a couple of hours going through the code and Javadoc for
this part of OpenJUMP in response to a question asked on the mailing
list. I summarized the results of my research on the OpenJUMP wiki:
http://openjump.org/wiki/show/File+DataSource+Notes
If I understand the code
Christopher,
The data sources are more useful for database connections where you don't
load the whole file into memory at one time. Also data sources are the way
that the link to the reader is done when saving a project. The data source
is associated with the layer and then when you open the proje
Larry pretty much has it right. The DataSource concept was introduced
when we started to think about lining up the I/O design more with JDBC,
and allowing for data stores with more than one dataset in them.
Ultimately I think we abandoned this direction, and moved on with
DataStores instead.
Christopher,
I can only repeat what is in the developer's guide, which I'm sure you
have already seen:
"A DataSource is an object that mediates to move data between the Workbench
and a file or
other data source; it will replace the Readers/Writers found in earlier
versions of JUMP.
Similarly, D
That seems to be the way most of the data input output
is done. I'm just wondering why the whole datasource
bit came about if it only winds up being a wrapper for
JUMPReader & JUMPWriter.
Thank you for the feedback,
--Christopher
--- Paul Austin <[EMAIL PROTECTED]> wrote:
> Christopher,
>
> Th
Christopher,
The easiest way is to use the
com.vividsolutions.jump.io.datasource.StandardReaderWriterDataSource to
just wrap a JUMp Reader and Jump Writer.
If you then register it using
InstallStandardDataSourceQueryChoosersPlugIn it will show up in the
Open/Save dialogs.
Paul
Christopher w
mhm.. unfortunately I am not that familar with that stuff (it has been
introduced newly with Jump 1.2 - if I think about the right thing you
talk about)
however, the wiki article of the devel documentation section my give hints:
http://openjump.org/wiki/show/How+to+write+a+new+driver
Based on
10 matches
Mail list logo