2009/5/28 Yaron Koren <yaro...@gmail.com>: > If I understand the question correctly, you're asking about how the form > knows what input type a certain field should be. If so: when the user goes > to the form, the form page parses the relevant template(s), and tries to > find the property corresponding to each template field. If it can't figure > it out, it just assumes it's a normal string; unless something else is > specified in the form definition, such as "property=" or "input type=", etc.
Wow, in that case its more advanced than I thought. It traces the parameter through the template call to find the assigned property and then its associated property type? I thought it was all via input type. Will that setting take precedence, or is it ignored if a property is discovered through through the process above? > -Yaron > > On Thu, May 28, 2009 at 12:37 PM, Dan Bolser <dan.bol...@gmail.com> wrote: >> >> How does a field type get associated with a property type? Is that >> strictly when the form is created from scratch and the property is >> specified? Are those links encoded strictly in the 'field' definition >> within the form? >> >> I'm just a bit confused because I'm adding fields to a form and >> wondering how the link between field type and property type was ever >> established and where it gets encoded. If the answer to the above two >> questions is YES, then I think I understand it. >> >> Cheers, >> Dan. >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Semantic Forms" group. To post to this group, send email to semantic-forms@googlegroups.com To unsubscribe from this group, send email to semantic-forms+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/semantic-forms?hl=en -~----------~----~----~----~------~----~------~--~---
