AW: AW: [geclipse-dev] milestone build

["Stuempert, Mathias IWR" <mathias.stuempert@xxxxxxxxxx>]

Hi Sylva,

> But to keep everyone informed, this might be a good time to announce a

> new plugin for testing that I finally checked in: eu.geclipse.vtk.test
> It can actually be used as a quick test to see if the VTK libraries
are 
> loadable with your setup. If the tests fail, it should tell you that 
> it's because of being unable to load them.
> There are only two tests but they test the whole VTK model - i.e. all 
> the VTK classes that one can select in the editor.
> To run it you must change the string specifying FileSystem.localdir in

> message.properties file in the eu.geclipse.test.internal package to 
>direct to your workspace and of course on linux don't forget to add
your 
> LD_LIBRARY_PATH variable when you run each test.

Sounds very good, so we have a quick test if VTK is working on a system.
Nevertheless at least if these tests are PDE tests there is an easier
way to obtain the workspace location than specifying it in the
properties. Don't know if this applies to your use case, but if so it
would prevent everybody of us to change property files individually:

IPath path = ResourcesPlugin.getWorkspace().getRoot().getLocation();

Or if you prefer URIs over paths:

URI uri = ResourcesPlugin.getWorkspace().getRoot().getLocationURI();

Of course you should check for potential NPE ;-)

Cheers, Mathias