[Databionic-esom-devel] Java class discovery - BackgroundRenderers and ForegroundRenderers

[Thanassis S. <th...@no...>]

Hello everybody,

I've been examining how the application discovers renderers (after having
trouble running it in my Eclipse workbench) and noticed that it hits the jar
file it was loaded from.
Examining the jar file for classes assumes that the jar is built already
there, which is not always the case.

I would suggest adapting the run-time class discovery mechanism of the
latest Weka, which dynamically searches the classpath. 
Then both renderer types could use automatic class discovery.

Would the team be interested in integrating the proposed automatic class
discovery, if I code it?

Another (architectural) point regarding renderers that require user
interaction, like Pmatrix and SmoothedHistogram - The renderers themselves
could be providing custom panels to plug in to the appropriate frames,
instead of having the main renderer know about their names and the types of
UI controls they use. Of course this is a bigger refactoring...

Thanks,
Thanassis