Michael,
You wrote: "I don't know how you want to use the featureCache. As I imagined
it
until now, it was just used to keep a part of your features in memory,
most of the data staying in the original file. But another solution
(yours ?) is to entirely copy the original data file in your own
inde
Hi,
all right, all right, I can do pt_BR.
@Pedro: can't you take care of pt_PT?
Cheers,
Ugo
Stefan Steiniger wrote:
> Dear Developer and User,
>
> This is second call (but first on the jump-user list) for helping to
> translate the language files. The following files need an updated in the
thanx a lot,
i actually forgot your migration backgound ;o) cause we either talk
english or german
stefan
Ugo Taddei schrieb:
> Hi,
>
> all right, all right, I can do pt_BR.
>
> @Pedro: can't you take care of pt_PT?
>
> Cheers,
>
> Ugo
>
> Stefan Steiniger wrote:
>> Dear Developer and User,
-- Forwarded message --
From: Frank Warmerdam <[EMAIL PROTECTED]>
Date: Mar 30, 2007 9:32 AM
Subject: Re: [Freegis-list] Binary Format For Features
To: Sunburned Surveyor <[EMAIL PROTECTED]>
Sunburned Surveyor wrote:
I'm currently talking with some of the other OpenJUMP developer
-- Forwarded message --
From: Sunburned Surveyor <[EMAIL PROTECTED]>
Date: Mar 30, 2007 9:15 AM
Subject: Re: [Freegis-list] Binary Format For Features
To: Frank Warmerdam <[EMAIL PROTECTED]>
Frank,
Thank you for your comments. I am going to forward your e-mail to the JPP
Develope
I'll get on that English translation today after work...
On 3/30/07, Stefan Steiniger <[EMAIL PROTECTED]> wrote:
thanx a lot,
i actually forgot your migration backgound ;o) cause we either talk
english or german
stefan
Ugo Taddei schrieb:
> Hi,
>
> all right, all right, I can do pt_BR.
>
> @P
Sounds a lot like some similar problems that have been addressed, and
for the most part solved. For most cases you could probably use an
indexed shapefile reader (not in OJ) or leverage a container such as
Pico or Hibernate (think Geotools has some code, or atleast a design in
this space - talk to
Hey Hugo,
Yes, I'll help, although I am *extremely* busy at the moment.
So the translation won't happen overnight. I'll do it after April, 19th.
Um grande abraço para ti! ;-)
Pedro.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ugo
Taddei
Sent: sexta
David,
There are some reasons why I would like to stay away from a system based on
an existing file format like ESRI's Shapefile, or on a system that requires
an external database. I'm looking for a simpler solution that can be used
to suck in and store Features from numerous file formats. In es
What about using a Java embedded database like HSQL or Derby???
They already can manage in-memory / persistence of any kind of data
and they do it very well I believe...
You should only keep each Feature's primary keys and, probably, it's bounds.
The db engine will take care of everything else.
Als
Paolo,
There were a couple of reasons why I wanted to avoid using a database for
this system. The first reason is complexity. As soon as we start using a
database we begin to deal with things like SQL, JDBC, and database
configurations. We are really attempting to integrate a second peice of very
Hi Paolo,
Nice to hear you, you surely have a good experience about database-access.
I like the idea of an embedded database.
I have made some tests in the past with jump+hsqldb, but I didn't get
any memory improvement (I have not much dbms knowledge and I may have
done mistakes leading to some
12 matches
Mail list logo
