alexeid
commented
10 years ago So a minimal annotation class would look something like this:
// package beast.core;
import java.lang.annotation.*;
/**
- An annotation used for specifying a BEAST object without needing to extend BEASTObject directly.
- Useful when one wants to extend a different object, since there is no multiple inheritance in Java. */ @Target({ElementType.TYPE}) @Retention(RetentionPolicy.RUNTIME) @Inherited public @interface BEASTObjectAnnotation {} //
And I think we could add the static methods we need directly to the existing BEASTObject class, instead of adding to a new Core class. It is an existing class and a natural place to have it. The static methods would include:
public static void init(Object beastObject, final Object... inputValues); public static void initByName(Object beastObject, final Object... inputValues); public static String getDescription(Object beastObject); public static Citation getCitation(Object beastObject); public static String getCitations(Object beastObject);
et cetera
On 26/05/2014, at 11:47 am, rbouckaert notifications@github.com wrote:
If the requirement of deriving from BEASTObject could be relaxed, while still having BEASTObject like behaviour (Inputs as members, initAndValidate to initialise, Description annotation, etc) a class could derive from existing classes (like JComponent) while still having the benefits of the BEAST framework.
Implementation ideas: o Add annotation to indicate a class is a BEASTObject. o Use introspection to create objects o Have a static beast.core.Core class to manage these changes, so changes to existing code is limited to XML and others Parsers/Producers. o Deprecate BEASTObject?
— Reply to this email directly or view it on GitHub.
rbouckaert
tgvaughan
If the requirement of deriving from BEASTObject could be relaxed, while still having BEASTObject like behaviour (Inputs as members, initAndValidate to initialise, Description annotation, etc) a class could derive from existing classes (like JComponent) while still having the benefits of the BEAST framework.
Implementation ideas: o Add annotation to indicate a class is a BEASTObject. o Use introspection to create objects o Have a static beast.core.Core class to manage these changes, so changes to existing code is limited to XML and others Parsers/Producers. o Deprecate BEASTObject?