Laurent - thanks for the bug reports. The second one is rather remarkable - it looks like I never actually wrote the code to use the field name at all, but assumed I had... these should both be fixed in the next version.
Dan - there are valid reasons to have a property name different from the template field name. For instance, I'm one of the people (though in the minority) who think that the property name should be a predicate, e.g. "Has author". -Yaron On Fri, May 29, 2009 at 3:36 AM, Dan Bolser <dan.bol...@gmail.com> wrote: > > 2009/5/29 Laurent Alquier <lalqu...@gmail.com>: > > Hi > > I used the Create Class form for the first time today and while it did > > create the classes I wanted, it also threw a couple of errors in the > > process. > > 1- I got the following PHP error for each field processed by the form: > > Notice: Undefined property: SFTemplateField::$input_type in <PATH TO > > EXTENSIONS>\extensions\SemanticForms\includes\SF_FormField.inc on > line 222 > > > > 2- The form ignored by choice for Field name (it used the property name > by > > default). > > Is there any reason the 'class' shouldn't enforce that convention? > i.e. just have two choices, property name and display name, and use > the property name as the field name. > > Seems like a logical convention to have, but it may cause problems for > reasons I haven't considered. > > > Other than that, it's a great time saver. > > - Laurent Alquier > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
