Larry,
Thanks for the response. This is exactly what I needed. Integration of
features from SkyJUMP into OpenJUMP should move a lot faster now.
I never ceased to be amazed by all of the functionality in Eclipse. It makes
me wonder what I would pay for it if I had to pay for it. :]
The Sunburned
Sunburned,
It's actually pretty straightforward to do the compare using Eclipse.
I use the right-click Compare With feature to synchronize features
with JUMP and OpenJump. It will open up a Compare editor that will
step you through the differences and you can use the buttons to copy
changes that
I would really like to start integrating some of the features in SkyJUMP
into OpenJUMP. I'm still trying to figure out the best way to do this.
Obviously we can't just replace the source code files, because SkyJUMP is
built from JUMP's code base, not OpenJUMP's. This means that it won't
contain th
Same goes for me, for both comments
Martin
Michaël Michaud wrote:
> All your propositions seem very reasonable to me.
>
> A big thank to both of you for site administration and project animation.
>
> Michaël
>
> Sunburned Surveyor a écrit :
>
>
>> Stefan and I have been talking a little bit ab
All your propositions seem very reasonable to me.
A big thank to both of you for site administration and project animation.
Michaël
Sunburned Surveyor a écrit :
> Stefan and I have been talking a little bit about some rules to govern
> source code contributions to OpenJUMP's core. Stefan has b
Regarding internationalized menu names, Sefan pointed us to the
MenuNames class, which holds all of the I18N menu names as public
static String types. Using these strings should effectively resolve
any issue with menu names, or am I mistaken?
regards,
Larry Becker
On 5/10/07, Sunburned Surveyor
I really hadn't given much thought to how we were integrating plug-ins into
OpenJUMP's core. Stefan usually does this work.
Paolo wrote: "If core plug-ins were initialized by some other methods,
like using some XML file or even by refactoring them inside separated
JARs you can drop inside the lib
Nice work Larry. We'll have to see if we can integrate these changes into
OpenJUMP.
SS
On 5/10/07, Larry Becker <[EMAIL PROTECTED]> wrote:
As I mentioned in the :[JPP-Devel] Rationale for Extension concept"
post, I have never gotten JUMP's -properties command line switch to
work without being
Martin,
You wrote: "Yay! I'll have to check it out - I've been missing a good DTP
app for a
while."
I think you will really like Scribus. It is one of those applications that
makes it worth the jump to Linux. They now have a version that runs great on
MS Windows, but they didn't when I started t
Stefan and I have been talking a little bit about some rules to govern
source code contributions to OpenJUMP's core. Stefan has been very patient
with me and has helped me realize that our project is still too small for a
strict or rigid contribution procedure. We've come to what I think is a good
I want to send a quick thank you note to Michael, Craig, and Bob for their
help with my JUnit test. I made the fixes that were needed and the JUnit
test is now working properly.
I'm sure I'll have more JUnit tests as I move forward.
Thanks Again,
The Sunburned Surveyor
On 5/5/07, Michaël Micha
As I mentioned in the :[JPP-Devel] Rationale for Extension concept"
post, I have never gotten JUMP's -properties command line switch to
work without being in the development environment (where all of the
classes are on the CLASSPATH by default). The problem has been
resolved. The core classes th
This was quite illuminating, thank you!!!
And it makes me think about a couple of things.
If Extensions are code capable of loading plug-ins,
the JUMPConfiguration class may be seen as a particular kind
of Extension. If we refactor it as an actual Extension,
one could choose about using it or not
> Hi Paolo,
>
> Thanks for your reply, it makes things clearer to me.
> If I may, I would like to ask 2 or 3 more questions.
> Do you mean that you cannot access mixed case table names or
> field names
> from OpenJUMP's standard plugin, even quoting the names like
> "tablename".'fieldname" ? I
I like this naming: "core plug-ins" and "add-on plug-ins",
it makes very clear that OJ is actually a container with
some core plug-ins hard plugged into it by the JUMPConfiguration
class.
I don't like arrangement too much because if you want to remove
a core plug.in, you have to change the Java c
15 matches
Mail list logo
