This shows you the differences between two versions of the page.
|
ca:discussion:component_system [2009/06/30 12:52] 127.0.0.1 external edit |
ca:discussion:component_system [2010/02/16 17:40] (current) 82.243.209.240 |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| * **out: getters** (allow to pull a value). | * **out: getters** (allow to pull a value). | ||
| * **out: output** signals (send a value to a set of listeners) | * **out: output** signals (send a value to a set of listeners) | ||
| - | * **in: sockets** its not very clear whats their difference with properties, other than properties which can just be written to, and might not have any state (no real input other than just a trigger -void-). | + | * **in: sockets** it's not very clear what's their difference with properties, other than properties which can just be written to, and might not have any state (no real input other than just a trigger -void-). |
| - | In general also, we need knowledge of all typing information, and how a type can be converted into another. A component can be assumed to have no inputs (or static inputs) to the constructor, so its always known how they are built. | + | In general also, we need knowledge of all typing information, and how a type can be converted into another. A component can be assumed to have no inputs (or static inputs) to the constructor, so it's always known how they are built. |
| Components need to be nested, so one can create abstractions. The abstractions become new components, with the inputs and outputs from the underlying scope the user chooses. | Components need to be nested, so one can create abstractions. The abstractions become new components, with the inputs and outputs from the underlying scope the user chooses. | ||
| - | The communication with signals and sockets can be just in one direction, in both, or even require some kind of complex protocol. Normally, at least one return value is needed, to know if the action succeded or not, or, support some kind of notification system. Also it is good for easy sequencing to know when an action finishes. | + | The communication with signals and sockets can be just in one direction, in both, or even require some kind of complex protocol. Normally, at least one return value is needed, to know if the action succeeded or not, or, support some kind of notification system. Also it is good for easy sequencing to know when an action finishes. |
| //-- What do you want to use components for ?// | //-- What do you want to use components for ?// | ||
| Line 26: | Line 26: | ||
| A good api for a component, means we can treat everything as a component. | A good api for a component, means we can treat everything as a component. | ||
| - | A shell, a command, they can all be represented as one of this components in a way that will allow to use generic interface widgets (like the property editor) to work on them, or connect them with higher level tools (like the graph tool). | + | A shell, a command, they can all be represented as one of these components in a way that will allow to use generic interface widgets (like the property editor) to work on them, or connect them with higher level tools (like the graph tool). |