|
Research meeting report - 22 March
This meeting was a follow up of the points raised from last weeks meeting. The Requirements Document changes were confirmed and extended into a component based Requirements Documents, which are available for download.
Several key issues were resolved and a few new functions were added to the overall design. The layout of the interface and the structure of both major components was discussed.
The breakdown follows:
Sequencer - the timeline is seperated and is self-contained for each individual track/channel, each part on a channel has its own command properties such as length of loop, loop length, etc. and can run independant of all other parts.
Sequencer - Event / Logic structure, where events are triggers, either internal or external and logic is the process that follows. IF event, THEN logic. These are plug-in functions.
Generator - output.swf, which is a duplicateMovie() of the virtual stage (display.swf), sized to match native res of a projector, and positioned on the extended desktop, solves mouse cursor visibility issue.
Generator - sequencer.swf, which is a modest control interface for the Sequencer, mainly used to display events and cue points and indicate various logic variables. Provides the comms layer to the Sequencer.
Global - create Environmental Variables, such as whether stage is to have impenetrable or bouncy "walls", gravity, wind, etc. Each Object can choose to ignore Environmental Variables if so desired.
A plan to involve a performer at this earlier stage of Planning so that any input regarding functions and useability is factored into the development process.
Confirmation that all Logic should be contained within the Sequencer component to minimise external communications. A further refinement and integration of the timeline and logic was discussed.
Setting of agendas for future planning meetings was mentioned in light of the increasing complexity of the project.
|