ymore in this field (Java GIS), I still
follow your mailing lists
and the fantastic job of the OpenJUMP community, bravi!!! :-)
Bye
Paolo Rizzi
Bugs item #1716059, was opened at 2007-05-09 12:01
Message generated for change (Comment added)
mand like "Add datastore" Layers have.
Also "Run Datastore" Layers should be saved inside OJ Task/Project, so
you don't have to manually reenter them each time.
Bye
Paolo Rizzi
> Hi,
>
> I use "Run datastore query panel " a lot and your suggestion se
e contrary Datastore layers coming from a "Run Datastore Query" are
read and stored inside OpenJump's memory only once, hence they're more
similar to Layers coming from, for example, a Shapefile, that is Layers
obtained from the "old" Datasource interface, I belie
Just a thought...
What your doing is, to me, very interesting, because it could lead to a
complete modularization of OJ.
If OJ could be splitted into separate and independent parts (Data
access, Catalog, Rendering, GUI, etc.) this can give the opportunity of
developing independent application w
t;> not that I know off.
>> However, we once figured that using OJ on a mobile devise with a small
>> screen would require to make a complete new gui (just due to sizes of
>> GUI elements)
>>
>> However, if you are in need for a free mobile GIS I would recommend to
s from a server...?!?
Bye
Paolo Rizzi
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core app
onfiguration and deployment of custom version of OpenJump
.) easier development of a server-side version of OpenJump
.) easier to replace the current plugin loading system with a more
powerful third-party container code, if necessity arises
So, again, thank you for your continued efforts!!!
Bye
P
Yes, any subfolder and sub-sub-folder, etc. of the ext directory is
scanned and inner files are added to the PlugIn ClassLoader.
See:
http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/src/com/vividsolutions/jump/workbench/plugin/PlugInManager.java?revision=1210&view=markup
Bye
Pa
Inside a plugin:
public void initialize(PlugInContext context) throws Exception {
super.initialize(context);
context.getWorkbenchContext().getRegistry().createEntry(
DataStoreDriver
Option 1 is intriguing, because it would be a very good mean of
exchanging geo data, a single file with everything inside, very good!!!
Maybe an ibrid solution were the project is itself store inside the H2
database, while each Layer can be internal or external would be even
better. Also you co
I'm sorry but it's been quite a long time since I worked on this,
expecially on the Oracle side, so I can't 100% garantee what I'm saying...
Anyway a NUMBER column with no precision/scale in Oracle correspond to a
38 digit number with variable precision, see:
http://download.oracle.com/docs/cd/B
However you decided to implement it, I'm sure it's going to work well!!!
But please, throw in whatever methods are needed for client code to
force both the mod-status and the init-status to true or false, so that
any client code, present or future, that doesn't follow your assumptions
will stil
nt
will get the automatic assumption that each and every attributes has to
be set at least once before init can be considered ended. While
mod-aware clients can, if they want, set the init status explicitely.
>
> regards,
> Larry
Bye
Paolo
>
>
> On Thu, Apr 30, 2009 at 6:24 A
an
>> Integer.
>>
>> I appreciate all of the clever solutions, but I will remain convinced that
>> BasicFeature can detect modification without any need for explicit client
>> methods to set it, until someone shows me proof that it can not.
>>
>> regards,
The previous sample code I posted was foolish, I'm sorry!!!
Find attached a better version that uses a single Object reference to
track both initialization and modify state.
During initialization this Object references a byte[] where each element
tracks the init state of the corresponding att
In the code inside my previous post I used the value "this" as a flag
but maybe that was bad!!! That way the BasicFeature could live forever,
or maybe not if garbage collectors are smarter these days...???
Anyway the point was to use a reference to any already existing Object
as a flag, so to n
Good job done!!!
But what if the initial value for a certain attribute was indeed NULL???
Data coming from a database can contain NULLs...
I thought about this problem, but to me there's no way for a Feature to
reliably know when it's initialization ends.
Maybe client code, for its own purposes,
Maybe it would be possibile to add explicit init methods like:
beginInit()
endInit()
or even a single "atomic" method:
init(Object[])
So that mod-aware calling code could call them to let the Feature "know"
it is being initialized.
Still the Feature could manage a disposa
> Thanks Stefan. Also, as far as the best database base class to
> consider, we have DataSource which loads the layer into memory, and
> DataStore which doesn't but is read-only, and IMHO has problems with
> multiple layers due to threading. I guess, if I was starting the task
> of implementi
> Hi,
>
> We play with WFS-T at work, where the mechanism of what really happens
> finally is hidden behind datastore drivers of WFS server like Geoserver or
> others. Anyhow, the problem is still the same than with direct connections
> to database. For example this document is handling rathe
may also come handy if one wanted to implement some form of undo!!!
>
> >
> > Your idea about detecting spatial conflicts is visionary. I see no
> > reason this couldn't be done, probably with database triggers.
> Thank you, I like the term
ture.
This may also come handy if one wanted to implement some form of undo!!!
>
> Your idea about detecting spatial conflicts is visionary. I see no
> reason this couldn't be done, probably with database triggers.
Thank you, I like the term "visionary"!!!
to be resolved, or at least signalled.
I hope this didn't sounded like a rant, it is not by any mean!!! :-)
Just trying to summarize all problems, even if now it's not the time to
solve them.
Bye
Paolo Rizzi
>
>
> -Alkuperäinen viesti-
> Lähettäjä: Larry Bec
K over a period of time.
So the best solution is letting user "A" generates a new PK "by hand"
and resolve an eventual conflict at insert time.
Even if the system is not multi-user garanteed, the
Modified/Inserted/Deleted reasoning is still valid.
Bye
Paolo Rizzi
> Rahkonen
, etc. are correct!!!
Is just they miss a little of the meaning of "Feature", that comprises
the non graphical attributes of the "Objects" too, but in this context
they should be the right terms.
Thank you for your work!!!
Bye
Paolo Rizzi
>
>> Reagarding the diffe
like an "Item" of that list
or collection.
Could it be this way that the two terms are currently used in OJ???
Bye
Paolo Rizzi
> Hi all,
> thanks for your answers.
> Indeed the terms "feature" and "item" are used into the OJ menu with the same
&g
Seems very interesting!!!
You may also consider the existing standards for photo metadata (XMP,
EXIF, IPTC).
Bye
Paolo Rizzi
> I put up a short post about a little tool I'm currently working on for
> my OSM mapping efforts. It's called "Feature Photo Manager" and
>
27 matches
Mail list logo
