Structure, Musical [Str]  >  Formalism  ]

Object-oriented programming is organised around "objects" rather than "actions", data rather than logic. Historically, a program has been viewed as a logical procedure that takes input data, processes it, and produces output data. The programming challenge was seen as how to write the logic, not how to define the data. Object-oriented programming privileges the objects we want to manipulate rather than the logic required to manipulate them.

The first step in OOP is to identify all the objects you want to manipulate and how they relate to each other, an exercise often known as data modelling. Once an object is identified, you generalise it as a class of objects and define the kind of data it contains and any logic sequences that can manipulate it. Each distinct logic sequence is known as a method. A real instance of a class is called an "object" or, in some environments, an "instance of a class." The object or class instance is what you run in the computer. Its methods provide computer instructions and the class object characteristics provide relevant data. One communicates with objects - and they communicate with each other - with well-defined interfaces called messages. (Source - http://searchwin2000.techtarget.com/sDefinition/0,,sid1_gci212681,00.html)



English - Español - Français - Deutch - Italiano

Alphabetical order - Chronological order

Bukvic, Ivica Ico (2002). {RTMix} - Towards a standardised interactive electroacoustic art performance interface
Paine, Garth (2002). Interactivity, Where to from here?
Pope, Stephen Travis (1996). Object-oriented Music Representation
Rodet, Xavier (1991). What Would We Like to See Our Music Machines Capable of Doing?
Sedes, Anne (2005). Aspects of Time in the Music of Horacio Vaggione
Solomos, Makis (2005). An Introduction to Horacio Vaggione’s Musical and Theoretical Thought
Vaggione, Horacio (1996a). Morphological Transformations Though Analysis and Resynthesis