|
|
Rapid Database Application Development
|
| Development |
"Microsoft Access for Linux"
|
|
|
Autoforms: Development Talksjstaniek, ccpasteur: july 2005 See also: Forms embedded inside Kexi: Autoform
Reusable components ^ tocWizard's pagesWe can reuse some wizard pages from LookupColumnWizardDocs. ^ tocAutolabelsLet editor widget be a widget which can contain editable data that usually needs a text label so user can know what (database) field it represents. Most common editor widget types can be:
We're going to implement autolabels as a pair label+editor_widget glued together. There're two types of autolabels:
[autolabel][editor]
[autolabel] [editor ] In fact, autolabels are not specifically tied to autoforms -- they can be used in any form type, but we have found them especially useful for creating autoforms, where labels, as other widgets, are always generated automatically. ^ tocOther constraints
Low priority constraints
+[editor name] [autolabel name]
Problem with layouts and autolabels
Proposed solution is to set the same arbitrary width for every horizontal autolabel (or height for vertical autolabel) within a layout column (or layout's row, accordingly). ^ tocQuestionsQ1: (jstaniek) This may be longer term TODO, but what about autolabels attached to checkbox/radiobuttons? I guess it can be usable to support well aligned autolabels for these widgets too, for instance ([x] stands for checkbox, (*) for radiobutton): [name: ][line edit ] [option1: ][x] [option2: ][x] [select1: ](*) [select2: ]( ) ^ ^ | | well well aligned aligned labels widgets Without using autolabels for checkbox/radiobuttons for above exmample we could have:
[name: ][line edit ]
[x][option1 ]
[x][option2 ]
(*)[select1 ]
( )[select2 ]
^ ^
| |
NOT SO WELL well
aligned aligned
labels widgets
|
|||||
|
||||||