Hello,
I don't know whether this the right place to get some answers but I have
a question on the source of openJUMP and didn't found a clear, well
arranged developer-forum.
I am developing a small information system based on openJUMP. I do some
manipulations on the core-source of openJUMP and
Based on input from Jukka, I have agreed to work on a function that will
allow the user to define a custom draw tool. The basic use case for this
tool is to make it easier to enter special features while in the field. I
think the example he gave was entering the location of trees, utility poles,
Hei Nils,
this is the right list to ask these questions.
Unfortunately, for me, it is not clear what you are trying to do - so no
simple question... can you specify?
However, we have methods to add tools/plugins to the toolbox (see class
OpenJumpConfiguration.java for examples) and to the
keeps going - but I like the thread (sadly for Paolo)
Original Message
Subject:[jump-pilot - Problems with PlugIns] RE: Problems getting
Oracle Connection
Date: Wed, 03 Dec 2008 13:45:08 +
From: SourceForge.net [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Read
Well, kind of funny anyway... :-)
I can't understand why you wrote:
select SDO_TUNE.EXTENT_OF('SCHEMA.MYTABLE','MYUSERNAME') from dual t;
it's the 'MYUSERNAME' part that makes me wonder...
The syntax is supposed to be:
SDO_TUNE.EXTENT_OF(
table_name IN VARCHAR2,
column_name IN VARCHAR2
Original Message
Subject:[jump-pilot - Problems with PlugIns] RE: Problems getting
Oracle Connection
Date: Wed, 03 Dec 2008 19:02:18 +
From: SourceForge.net [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Read and respond to this message at:
Hi Nils,
To get the toolbox you can do:
ToolboxDialog toolbox = ((EditingPlugIn)
context.getWorkbenchContext().getBlackboard().get(EditingPlugIn.KEY)).getToolbox(context.getWorkbenchContext());
I'm not sure what you are going to do after that. It is pretty unusual to
change the selected tool.
I tryies using the '-' so I got access to the default schema for the
logged-in user.
Maybe it's this the culprit, something in how your server/database/schena/user,
etc. are configured...???
Try with this SQL from any Oracle client:
select sys_context( 'userenv', 'current_schema' ) from dual
