Non visual components
A non-visual component is a component that is only visible during design time. After generating the application, the component has no rendering.
Non-visual components work behind the scenes to perform specific programming tasks. Examples include system timers, database components, and emailing. When you place a nonvisual component on a form, PHsPeed displays an icon representing the component on the form. This icon is used to access the component at design time in order to change the component's properties, but the icon does not show up when the program runs. Nonvisual components have properties, methods, and events just like visual components do.
|
|
Description |
|
Component for enabling HTML5 animations |
|
|
Under development. Module to consume API functions |
|
|
Under development. Implement an API function in an API module. |
|
|
Specifies a module without a form, but is runnable. It can use invisible components for database access and can be used for processing, or API implementations |
|
|
A series of x/y pairs that specify an element in a chart |
|
|
Reference to your database specification |
|
|
Dispatcher between database table and form fields |
|
|
See Chartserie, only now based upon database data |
|
|
SQL statements to be used in a crud situation. Use in conjunction with DBQuery. |
|
|
Basic database table component |
|
|
Simple Query component for executing SQL statements |
|
|
Query component, based upon DBTable, but with customizable SQL |
|
|
EMail module, based upon PHPMailer |
|
|
Specifies a module to be reusable. It inherits the form of the parent that is using this one. |
|
|
Basic PDF component. Required if you want to work with PDF's. Also for PDF components. You only need one. |
|
|
Specifies a module to be a regular web form. The Root is responsible for theming, basic margins, backgrounds, etc. |
|
|
Component for generating content based upon a template file and variables. |
|
|
A component that triggers configured times. |