Re: Scheme Debugging in Eclipse...WORKS!

[Jim White <jim at pagesmiths dot com>]

Thanks!

Endured a few bumps to get it running.

The build(**) apparently doesn't copy resources.properties from src to 
bin and SchemeScriptPlugin ignores the MissingBundle exception setting 
resourceBundle to null.  That results in a NPE a long while later when 
the editor is created (Eclipse just says "Unable to create part" with no 
trace or log output or anything!).  Fortunately being able to 
source-level debug the whole environment enabled me to track the problem 
down.

SchemeScriptPlugin's constructor should probably log the MissingBundle 
exception somewhere that it's visible rather than silently ignoring it.

Also I had to fiddle the classpath a wee bit as you moved kawa.jar to 
lib but didn't check in the classpath change (also the old is still in CVS).

I'm up and running on Eclipse 3.0.1 on Max OS X and off to figure out 
how to use it now.

Thanks again! Super work!

Jim

(**) That's just the automatic build as I just said "run as workbench" 
or "debug as workbench", maybe something different happens if I were to 
export the plugin?  Not sure how this is supposed to work, I just copied 
the file to bin to make it go.

Dominique Boucher wrote:

> Jim,
>
> All my new experimentations are now under CVS. Tell me if you are able to
> build SchemeScript now. 
>
> If you have any question regarding the new (undocumented/unstable/not well
> designed) feature, feel free to contact me.
>
> Cheers,
>
> Dominique