[commits] [Wiki] changed: Project/HordeForm
Wiki Guest
wikiguest at horde.org
Sat Dec 31 00:58:32 UTC 2016
guest [80.187.118.173] Sat, 31 Dec 2016 00:58:32 +0000
Modified page: https://wiki.horde.org/Project/HordeForm
New Revision: 39
Change log: Rethink forms
@@ -971,5 +971,5 @@
Some types might need extra handlers like datepicker
Php
-The ajax handler must be explicitly registered in ajax application.
It guesses prefix_formname_fieldname classname for an injectable
object. The field class has a backend and a list of validators and
change propagators which are each only defined by interface to allow
flexible backends with existing inheritance trees. Otherwise rdo and
friends wont work here. A field class also references a type class and
horde view templates for active and readonly rendering. Defaults from
type, overridable. The form class might be superfluous for fields as
any combination of fields may be displayed anytime.
+The ajax handler must be explicitly registered in ajax application.
It guesses prefix_formname_fieldname classname for an injectable
object. The field class has a backend and a list of validators and
change propagators which are each only defined by interface to allow
flexible backends with existing inheritance trees. Otherwise rdo and
friends wont work here. A field class also references a type class and
horde view templates for active and readonly rendering. Defaults from
type, overridable. The form class might be optional for fields as any
combination of fields may be displayed anytime. A form or collection
with a common save trigger might still be needed to bootstrap new
domain items with more than one required field... and we need some
context where to store a record's key for ajax interaction. Form may
change or unhide more fields depending on valid state
More information about the commits
mailing list