Hey All,
This thread kind of got warnocked. Perhaps a re-post will help? :)
-Brian
Brian Cassidy wrote:
I decided to start with a simple auto-complete element. I can envision
the yaml file looking something like this in it's simplest form:
- name: foo
type: Prototype::Autocomplete
url: /foo
Q: to set the url programatically, say, via the catalyst context, would
the best practice be to override the element with a custom one that does
just that? (in new() perhaps?)
Further to the above config, you can set the update_id, and also a
generic set of "options" to be passed along.
With respect to the update_id, if it's not specified then it is auto
generated as "${id}_auto_update" -- this element most likely does not
exist and much be created.
Q: (more of an api question...) If update_id is specified, should i
assume the user will generate that element themselves?
Q: What's the best practice for injecting elements into the form from
custom elements?
I see the the Dojo::Repeatable element, you're adding some elements to
_custom_elements() -- should i copy that practice?
_______________________________________________
HTML-FormFu mailing list
HTML-FormFu@lists.scsys.co.uk
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/html-formfu
