Difference between revisions of "Component"
(Created page with "== Tutorial 2 - Component Creator == A component can consist of two parts: *a physical part; *attached electronic devices. It can sit on the System Panel or the Dashboard ...") |
|||
| (29 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | A '''Component''' is essentially a '''library''' which is controlled by a Flowcode program, and can extend the Flowcode interface. | |
| + | [[File:Component-example.png|right]] | ||
| + | Components can interact with flowchart programs and other components to create an effective rapid prototype development system or application which can usually run both in simulation and on hardware. | ||
| − | |||
| − | |||
| − | |||
| − | + | == Overview == | |
| − | + | A Component can be ''anything'' that is self-contained, for example: | |
| + | * An electronic device | ||
| + | * A measuring instrument | ||
| + | * A packaged simulation | ||
| + | * An extension to the system | ||
| + | * A library of useful macros | ||
| + | Flowcode provides a set of [[Components]] packaged with the application. | ||
| − | + | A component always has a physical presence on the [[System Panel]] or the [[Dashboard Panel]]. This is to allow the user to easily select and identify the components they are using, and also, where graphics are used, to provide a representation of the object the Component represents. The Component object can also be used to convey useful information to the user. | |
| − | + | Components also have access to other features of Flowcode suitable for displaying data, such as the [[Data Console]] and [[Data Scope]], where a Component can create their own data feeds for reading and writing information. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ==Components structure== | |
| − | + | A Component comprises of a combination of primitive shapes, existing components, flowchart macros, [[Resource Manager|resources]] and [[Component Properties|properties]]. When the Component is exported this information is packaged into a self-contained unit, similar to an ''executable application'' which can then be no longer read or edited. | |
| − | + | Components are located in the Components toolbox. It is divided into sections such as ''Inputs'' and ''Outputs'' to help the user find what they want. | |
| + | |||
| + | Any component can be used as a building-block to create new components. | ||
Latest revision as of 12:28, 2 July 2019
A Component is essentially a library which is controlled by a Flowcode program, and can extend the Flowcode interface.
Components can interact with flowchart programs and other components to create an effective rapid prototype development system or application which can usually run both in simulation and on hardware.
Overview
A Component can be anything that is self-contained, for example:
- An electronic device
- A measuring instrument
- A packaged simulation
- An extension to the system
- A library of useful macros
Flowcode provides a set of Components packaged with the application.
A component always has a physical presence on the System Panel or the Dashboard Panel. This is to allow the user to easily select and identify the components they are using, and also, where graphics are used, to provide a representation of the object the Component represents. The Component object can also be used to convey useful information to the user.
Components also have access to other features of Flowcode suitable for displaying data, such as the Data Console and Data Scope, where a Component can create their own data feeds for reading and writing information.
Components structure
A Component comprises of a combination of primitive shapes, existing components, flowchart macros, resources and properties. When the Component is exported this information is packaged into a self-contained unit, similar to an executable application which can then be no longer read or edited.
Components are located in the Components toolbox. It is divided into sections such as Inputs and Outputs to help the user find what they want.
Any component can be used as a building-block to create new components.
