On Wed, 21 Apr 1999, Thomas McKay wrote:
> prompt% set o [createRect 0 0 10 10]
> java0xc7
> prompt% java::info methods java0xc7
> {equals java.lang.Object} ..
> prompt% rename java0xc7 poly1
> prompt% java::info methods poly1
> java::info: unknown java clas
You need to do a "package require java" before running java::*
commands inside Jacl. This changed from 1.1 but it makes Jacl
work the same way as TclBlend so it is a good thing.
later
Mo DeJong
dejong at cs.umn.edu
On Wed, 21 Apr 1999, Thomas McKay wrote:
> Yikes! I've been using v1.1a1 and am
Yikes! I've been using v1.1a1 and am now trying to use 1.2.2: None of
the "java::" commands are available. Do I need to do something with
BlendExtension?
Tom
The TclJava mailing list is sponsored by WebNet Technologies.
To subsc
On Wed, 21 Apr 1999, Thomas McKay wrote:
> Hi!
>
> In my Jacl application, users may write Tcl scripts to manipulate
> database objects:
>
> prompt% set o [createRect 0 0 20 30]
> java0xcf
I am not sure if this is exactly what you are asking but there is a
new feature/bug fix in Jacl
Hi!
In my Jacl application, users may write Tcl scripts to manipulate database
objects:
prompt% set o [createRect 0 0 20 30]
java0xcf
However, if a script is to be written that is associated with a specific
object, then that objects id (the java0xcf name) must be persistent and
stored when the db