Assets

Among other attributions, Assets converts schema objects into engine objects.

Relation between schema objects and engine objects are defined into config file bindings.json, which have the following format:

[
    [es.eucm.ead.schema.actors, es.eucm.ead.engine.actors],
    [SceneElement, SceneElementActor],
    [Scene, SceneActor],

    [es.eucm.ead.schema.renderers, es.eucm.ead.engine.renderers],
    [AtlasImage, AtlasImageRenderer],
    [Image, ImageRenderer],

    [es.eucm.ead.schema.effects, es.eucm.ead.engine.effects],
    [Transform],
    [GoScene],
    [Video],
    [ChangeRenderer],
]

There are two types of lines: those that define packages, and those that define actual bindings. Package lines are those that contain .s somewhere. They define package-lookups for all lines until the next package-line. Class-lines describe what schema-class (in the currently-active schema-package) will be bound to what engine-class (in the currently-active engine package).

Engine classes and packages can be omitted; in this case, the class-line will only be defining an alias (without any direct engine object). This is useful when the containing engine-object already does whatever is needed to render the corresponding schema object.

More information about binding schema objects with engine objects.

All engine elements must implement Engine Object. To obtain the engine element representing a schema object, you can use:

EngineObject engineObject = Engine.factory.get(schemaObject);

Inside the get, the factory calls:

engineObject.setSchema(schemaObject);

This method only sets the schema object represented by the engine object, and might or might not call the initialize method.

The initialize method should be used to build the engine object form the schema object.