Hi, After analyzing the source code of the old simulator, I've come to the conclusion that currently the best way to abstract the simulator, is to use the following abstraction:
- the cicuit elements should be added as the existing Component subclasses - the Circuit itself could be extended to have a list of components - the elements (or components) have Pins - Pins can be connected with Wires We need the component level abstaction, becasue some components might be formed by have more than one element. All the above mentioned classes should be models. The controllers should be separate classes, I guess. The classes derived from Components can have properties. A quiestion is, how should be the properties implemented. I see two options here: - as traditional C++ properties, with setter and getter methods; the property should be set by the controller and it should have associated property classes/objects. - as propery object associated with each component object. The component shows only the list of its properties, and those properties can be handled by the controller. Currently I don't know which way of implementation is better. Any ideas on this? Zotltan ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Ktechlab-devel mailing list Ktechlab-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
