Thanks for the answers.
After thinking more about this, I came to the conclusion that a
generic controller for all the components should be enough, so I'll go
with the second option, based on associated property objects. This way
a generic controller should be enough for all the components, and
moin,
okay, here is what I’ve done on this topic. It just shows, how the properties
will be permanently stored to be re-used by our users, later. Of course there
can (and most likely will) be some classes to collect all the information
needed.
Am Donnerstag, 28. Oktober 2010, 23:31:11 schrieb
Am Donnerstag, 28. Oktober 2010, 23:53:07 schrieb Alan Grimes:
> > Currently I don't know which way of implementation is better. Any ideas
> > on this?
>
> Hmm, let's compare circuit and component:
>
>
> A circuit is a collection of interconnected components in a circuit
> document.
>
> A compo
> Currently I don't know which way of implementation is better. Any ideas on
> this?
Hmm, let's compare circuit and component:
A circuit is a collection of interconnected components in a circuit
document.
A component can be thought of as a hard-coded sub-circuit that contains
zero, one or man
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
