Difference between revisions of "Kexi/Plugins/Quickforms"
(Created page with "Design page for task '''Add Qt Quick-based forms'''. *Started: piggz, Jan 2014 *{{Wish|????}} __TOC__ ==Introduction== TODO (Rationale) ==Use cases== ==Requirements==") |
m (Jstaniek moved page Kexi/Plugins/Forms/Quickforms to Kexi/Plugins/Quickforms: flatten) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
*Started: piggz, Jan 2014 | *Started: piggz, Jan 2014 | ||
| + | *Status: '''experimental''' implementation exists in kexi/plugins/quickforms, kexi_quickform_piggz branch. | ||
*{{Wish|????}} | *{{Wish|????}} | ||
__TOC__ | __TOC__ | ||
==Introduction== | ==Introduction== | ||
| − | + | ||
| + | Initial blog entry: [http://www.piggz.co.uk/?q=blog/2014/01/08/creating-fluid-powerful-kexi-forms] | ||
| + | |||
| + | Microsoft Access has powerful VBA forms allowing many tasks to be performed. Kexi forms are limited to data-bindings and macro execution. To have something as powerful as VBA it is preferential to not re-invent the wheel. QtQuick provides a extensible set of basic components, and a pwoerful scripting language that can be extended with application specific functionality. | ||
| + | |||
| + | QtQuick forms in Kexi will give us a powerful framework for allowing the user to build complex and fluid forms, backed by javascript scripting and kexi specific bindings. | ||
| + | |||
| + | Constraints: | ||
| + | *Qt Quick-based forms do not replace QWidget-based forms but complement them. | ||
| + | *They are not interchangeable and probably cannot be combined (except one can be opened using "open" action). | ||
| + | |||
==Use cases== | ==Use cases== | ||
| + | *Menu system/navigation | ||
| + | *Data Entry | ||
| + | *Data based application development using kexi locked-down mode | ||
| + | |||
==Requirements== | ==Requirements== | ||
| + | *We should build some kexi specific components to simplify building forms | ||
| + | *Examples: | ||
| + | **KexiButton | ||
| + | **KexiField | ||
| + | *We should provide bindings to control the Kexi instance (already mostly covered) | ||
| + | *We should provide bindings to the current record data and record navigation functions | ||
| + | *We could provide some file io functionality | ||
Latest revision as of 19:09, 22 September 2014
Design page for task Add Qt Quick-based forms.
- Started: piggz, Jan 2014
- Status: experimental implementation exists in kexi/plugins/quickforms, kexi_quickform_piggz branch.
- Wish #????
Introduction
Initial blog entry: [1]
Microsoft Access has powerful VBA forms allowing many tasks to be performed. Kexi forms are limited to data-bindings and macro execution. To have something as powerful as VBA it is preferential to not re-invent the wheel. QtQuick provides a extensible set of basic components, and a pwoerful scripting language that can be extended with application specific functionality.
QtQuick forms in Kexi will give us a powerful framework for allowing the user to build complex and fluid forms, backed by javascript scripting and kexi specific bindings.
Constraints:
- Qt Quick-based forms do not replace QWidget-based forms but complement them.
- They are not interchangeable and probably cannot be combined (except one can be opened using "open" action).
Use cases
- Menu system/navigation
- Data Entry
- Data based application development using kexi locked-down mode
Requirements
- We should build some kexi specific components to simplify building forms
- Examples:
- KexiButton
- KexiField
- We should provide bindings to control the Kexi instance (already mostly covered)
- We should provide bindings to the current record data and record navigation functions
- We could provide some file io functionality
This page was last edited on 22 September 2014, at 19:09. Content is available under Creative Commons License SA 4.0 unless otherwise noted.