Wayne
explanation
Moderator: Benj
-
wayne millard
- Posts: 234
- Joined: Thu May 31, 2007 2:18 pm
- Has thanked: 7 times
- Been thanked: 12 times
- Contact:
-
JonnyW
- Posts: 1230
- Joined: Fri Oct 29, 2010 9:13 am
- Location: Matrix Multimedia Ltd
- Has thanked: 63 times
- Been thanked: 290 times
- Contact:
Re: explanation
Hi Wayne.
Do you mean the advanced category with the CAL in? These were split into controls and CAL categories before and have since been moved - most of these are the underlying components that are used to prop up the 'front-end' components. For example, ButtonHelper is the component that is used during simulation on any component where you can press a switch - keypad, switch array, etc. The CAL is the direct interface into the underlying C code when downloading, so for example RS232 will package the UART CAL code in a presentable and easier to use way.
By building components in a nested way like this you can provide generic functionality for any component that uses it (such as 'all UART based components have a console') without having to re-implement each time. If, for example, you created a component called 'Press Key' which outputted a number via RS232 every time you pressed a button, you could use ButtonHelper and CAL UART to do this and your component would inherit the functionality of both components. For most uses and most people these components will never need to be added directly into a project.
Jonny
Do you mean the advanced category with the CAL in? These were split into controls and CAL categories before and have since been moved - most of these are the underlying components that are used to prop up the 'front-end' components. For example, ButtonHelper is the component that is used during simulation on any component where you can press a switch - keypad, switch array, etc. The CAL is the direct interface into the underlying C code when downloading, so for example RS232 will package the UART CAL code in a presentable and easier to use way.
By building components in a nested way like this you can provide generic functionality for any component that uses it (such as 'all UART based components have a console') without having to re-implement each time. If, for example, you created a component called 'Press Key' which outputted a number via RS232 every time you pressed a button, you could use ButtonHelper and CAL UART to do this and your component would inherit the functionality of both components. For most uses and most people these components will never need to be added directly into a project.
Jonny