Paul == Paul Kinnucan [EMAIL PROTECTED] writes:
I have thought of one occasion when this will work differently
from as now. Possibly better, possibly worse.
If you have just set a variable using customise, but not saved
it, and then you switch projects, it will not get reset to
Paul Kinnucan [EMAIL PROTECTED] seems to think that:
[ ... ]
The only solution to this problem that I can see is to provide a
custom-set function for JDEE variables that updates the dirty variable
list whenever the user customizes a variable during a session. Since
the custom-set function is
Phillip Lord writes:
Paul == Paul Kinnucan [EMAIL PROTECTED] writes:
I have thought of one occasion when this will work differently
from as now. Possibly better, possibly worse.
If you have just set a variable using customise, but not saved
it, and then you switch
Paul == Paul Kinnucan [EMAIL PROTECTED] writes:
I thought about this solution. It has the minor disadvantage that
it will not work for non JDE variables that use the JDE namespace
to piggy back into the project file mechanism. I seem to remember
having used this in the past when I
Phillip Lord writes:
Paul == Paul Kinnucan [EMAIL PROTECTED] writes:
I thought about this solution. It has the minor disadvantage that
it will not work for non JDE variables that use the JDE namespace
to piggy back into the project file mechanism. I seem to remember
Phillip Lord [EMAIL PROTECTED] seems to think that:
[ ... ]
This will also make it easy for third parties to piggy back into the
JDE project system I think, without having to use the jde- namespace
which the system currently depends on.
I'd be quite happy to give this a go if you'd like.
I'm trying to update RemoteEclipse to work with JDEE 2.3.3. One
thing it needs to do is include certain jars in the classpath for the
beanshell so that it can talk to Eclipse and pull various project
settings down.
In previous versions, all RemoteEclipse did was put advice around
bsh-internal
