On Thu, Jul 22, 2010 at 8:21 PM, gilleain torrance <[email protected]> wrote: > The problem is : what? The only thing that occurs to me is what > modules are available -
Indeed, I was thinking that too... could be nice to have that information at runtime... the info could be retrieved by attempting to load the $module.javafiles from the classpath... Thinking about this in the Bioclipse context, these files might actually not be available on the CP... > but the code wouldn't compile if the module wasn't there. No, but a module that did get compiled, might not be there in practice... cdk-core.jar + cdk-standard.jar, but not cdk-qsar.jar... > In any case, you could probably use the classloader for that. Yeah, possibly... not sure about the OSGi environment, as the CDK class would be in cdk-core, so not necessarily have access to the CP of cdk-standard, etc... I need to think about that... > The CDKConstants class is a bit of a god class - if that's the right > anti-pattern - but I'm not sure it's the largest building in CDK > city... > > http://gilleain.blogspot.com/2008/11/cdk-city.html It might actually be... reducing the size might indeed also benefit e.g. the applet size... but not sure how large it really is... Egon -- Post-doc @ Uppsala University Proteochemometrics / Bioclipse Group of Prof. Jarl Wikberg Homepage: http://egonw.github.com/ Blog: http://chem-bla-ics.blogspot.com/ PubList: http://www.citeulike.org/user/egonw/tag/papers ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Cdk-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdk-user
