Ferreteria/v1/usage/forms: Difference between revisions
Jump to navigation
Jump to search
m (Woozle moved page Ferreteria/pieces/forms/v1 to Ferreteria/usage/forms/v1: this should be a usage guide) |
m (Woozle moved page Ferreteria/usage/forms/v1 to Ferreteria/v2/usage/forms/v1 without leaving a redirect: this is all v2 documentation) |
(No difference)
|
Revision as of 14:38, 19 January 2019
Rules
- Every control (clsCtrl) belongs to a control row (clsCtrls).
- Control rows can be indexed in order to allow for multi-row editing.
- clsCtrls should eventually be renamed clsCtrlRow.
- I haven't decided if there needs to be a clsForm class for containing multiple control rows.
- Indexing is optional if you're only editing one row at a time.
Pages
- changes/1: change to Save() parameters
Files
|
ClassesThe way this is organized is a little messed up; the descendants of clsCtrls handle database interaction -- but shouldn't it be the descendants of clsFields? It works reasonably well as is, but some rethinking might be a good idea, once everything is all mapped out. collections
unitary objects
|
Significant Functions
- clsCtrls (abstract)
- function Ctrl(<name>) → clsCtrl
- function FieldsObject() → clsForm_recs_indexed
- clsCtrl (abstract)
- function Field() → clsField
- function RowObject() → clsCtrls
- clsFields
- function DefaultValues() → array of mixed
- clsField
- function ValStore() → mixed
- function ValShow() → string
- clsCtrls → clsCtrl array
- clsCtrl →