--- Michaël Michaud <[EMAIL PROTECTED]> ha
scritto:
> Hi Giuseppe,
>
> I just want to point out another method to change OJ
> language (at least
> for window users).
> You can change the regional parameters (in the
> windows configuration
> panel) to the language you choose (ex. english),
> st
Hi SS,
and thanks for your review.
Some functions really required a better explanation.
Good job!
Peppe
> I did some more work on the "Edit" top-level menu
> functions today
> after work, although I'm not quite finished. I
> changed some of bold
> funtion names on the wiki to match the actual
> E
I have just found and corrected some minor errors in
the Italian language file. I also translate the new
Tools fom English to Italian.
I send the file as an attachment of this mail
Peppe
___
L'email della prossima generazione? Puoi averla con la nuova Yahoo
Hi Larry
> Perhaps Peppe's use case can be handled by simply
> including all of these
> scripts in the release.
I only check if it is possible with a simple Jar tool
> I think switching languages
> after the program is
> running would require a lot of rework.
. users can be invited to res
Sounds fine to me.
Larry
On 10/8/07, Sunburned Surveyor <[EMAIL PROTECTED]> wrote:
>
> I think that will be just fine Larry. Do you have any problem with me
> changing the last check box label for the English translation?
>
> SS
>
> On 10/8/07, Larry Becker <[EMAIL PROTECTED]> wrote:
> > Hi SS,
>
Hei Eric,
ok...If you commit then add it to the "plugins" folder
http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/plug-ins/
stefan
Eric Lemesre wrote:
> Hi Stefan,
>
> Thank for your intervention with Uwe,
> I rebuild directory structure and commit in a new directory this plug in.
>
> pr
I wouldn't try and set quantitative upper limits, just let them be
dictated by available memory and processor size.
But it seems reasonable to state that the architecure is primarily
designed for in-memory datasets (although that isn't strictly true,
since the DataStore framework shows how the
Makes sense to me. The selection handler design is one thing that
really doesn't scale all that well. It's a tough problem - how do you
keep track of an arbitrary set of things without actually keeping
references to them?
Actually, this problem was the motivation behind my developing the
Geo
Martin Davis a écrit :
>I wouldn't try and set quantitative upper limits, just let them be
>dictated by available memory and processor size.
>
>But it seems reasonable to state that the architecure is primarily
>designed for in-memory datasets (although that isn't strictly true,
>since the Data
>At one point I was
>thinking it would be nice to have a Set Fence from Geometry menu item as
>well.
>
>
Yes, this is a feature I missed sometimes.
That makes me remember that trying to copy/paste geometry from an
existing layer to the fence,
I get strange things like having 2 geometries in t
10 matches
Mail list logo
