[liblamp-developers] simple and complex objects
Status: Pre-Alpha
Brought to you by:
noah1989
From: Stefan N. <noa...@go...> - 2008-02-10 01:33:46
|
Hi folks, I just wrote down some ideas that i had about the next thing we may implement. You can also find these notes in the doc/planning directory. I really like to hear your suggestions :) What do you want to do differntly or is this okay? Here is the excerpt: 1.2.: Simple and complex objects An important idea that should be included is that you can make something complex from simple elements. However, when simulating the behaviour of such a combined object only the properties of each element are important. Altogether they describe the behaviour of the whole system. The Physical class should of course cover both of these kinds of objects. Due to their special properties respected and manipulated by simulators the elementary objects have to be handled in a special way. This will be done by deriving a class named Simplex from the Physical class. Evey Physical must provide a list of its elements, which can be easily be implemented by both the simple objects just returning themselves and the complex objects concatenating the lists of each part. The previously mentioned non-static properties are something for simplexes as they are what simulators can handle. They should provide definitions for these values but should not store the numbers because this belongs to the tasks of simulators and frames. Ideas on how to implement this are also highly appreciated :) btw: Some tests and xml documentation for the Quantity class and xml documentation for most other things must be written. Maybe i will do this tomorrow. Maybe ;-) -- Stefan Noack <noa...@go...> |