[Biojava-dev] bjv2 alpha 3

[Matthew Pocock]

Queue brain-dump... Utility methods are primarily intended for dumb 
users - dumb coder users. A different mechanism may be more appropreate 
for dumb drag-n-droppers. I am assuming from what you have said that 
bean editors let you do quasi-illegal things like invoking static 
methods relative to instances. I've no problem with 'skinning' bjv2 for 
a different user group. What if we had some magic like this:

Object tool = new ToolFactory().makeTool(Utility.class)

This returns a 1st class object with non-static methods that alias to 
the static tools methods on Utility.class and is serializable - would 
this help?

What's the standard pattern for exposing processes through beans? I'd 
feel much happier if this level of logic was handled in a workflow 
language e.g. Taverna could be adapted so that all utility classes 
become processors. That way dumb d-n-d users realy don't have to look at 
any of the code.

>It would be nice if more of BioJava could be made into valid beans. 
>Unfortunately this does render all of the elegant singletons invalid. If 
>only java had a keyword for a constructor that could be called only by the 
>VM to create a bean. I suspect such a thing would cause all kinds of 
>security problems though.
>
>- Mark
>
>
>_______________________________________________
>biojava-dev mailing list
>biojava-dev at biojava.org
>http://biojava.org/mailman/listinfo/biojava-dev
>
>  
>