From: Lukas D. <AFB...@gm...> - 2003-02-18 01:01:58
|
Hi list, Some interesting fact: AMS 2.0.0 est omnes devisa in partes tres. :-) I - AMS Framework + provides basic access to envirement resources: alsa midi, jackd audio, config and session data stored in xml files, etc. + is responsible for bootstrapping, loading/saving of patches. II - Patch + represents everything that makes up a session, i.e. everything that will be saved as session (patch) data + provides session state (after bootsrapping phase is finished) + data model for gui III - (G)ui + provides view(s) of the data/state represented/provided by the patch. + well, we all know what a gui is, don't we :-) Note: there might be cases in which the gui needs acces to Layer I. Not sure about this. For Layer II i have created an UML diagramm. There are many comments on it, so it should be possible for anyone interested to catch the basic ideas. here are the links: Dia file: http://alsamodular.sourceforge.net/ams-uml_patch.dia XFig file: http://alsamodular.sourceforge.net/ams-uml_patch.fig The layout could need some work, and you better not look to closely at the operations/attributes (incomplete or outdated in many cases). I would be happy to discuss any issue or answer any question on-list. This isn't supposed to be a one-man-show after all. ;-) I will announce any update to this files on list, if no one objects. Similar diagrams for layer I and III will follow. Everyone is invited to make suggestions or commit his/her own idea of what things should look like. Have a nice week everyone. Lukas |