[commits] [Wiki] changed: Project/HordeForm

[Wiki Guest]

guest [80.187.118.173]  Sat, 31 Dec 2016 00:25:57 +0000

Modified page: https://wiki.horde.org/Project/HordeForm
New Revision:  38
Change log:  More ajax field-centric ideas

@@ -957,4 +957,19 @@
  * Fields may be invisible of readonly for some users based on  
application state or permissions
  * apps may break into popup/redbox windows for some cases of "choose  
existing or create new related item" or load-on-demand dialogues  
instead of pre-defined conditional subdialogs
  * support relations (Rdo or domain context) with little repetitive coding
  * support on-the-fly validation while typing
+Less coupling.
+
+
+Js/dom
+
+Anything that has a data-edit attribute is an edit trigger. A parent  
must have data-field (field name) and data-form (form name)
+ is it sufficient to have any parent of parent to have data-form attribute?
+
+Anything that has data-save is a save trigger.
+
+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.