The change of property type ? I am sure of it. I will keep an eye open and let you know if it happens again. I will have other classes to create once the patch it available for the other issue I reported.
- Laurent On Fri, May 29, 2009 at 1:55 PM, Yaron Koren <yaro...@gmail.com> wrote: > Are you sure about that? I can't duplicate that error. > > On Fri, May 29, 2009 at 1:35 PM, Laurent Alquier <lalqu...@gmail.com>wrote: > >> One other observation while you are looking into these parts of the code. >> >> When I created that class, I assigned a property 'Has description' to the >> new class. >> >> The property already existed, with type text. >> >> Once the class was created, that property suddenly switched to 'Page'. >> >> It looks like the Create Class form created the property even though it >> already existed - and created it with a type 'Page' even though I selected >> 'Text' in the drop down list. >> >> - Laurent >> >> >> >> On Fri, May 29, 2009 at 1:22 PM, Laurent Alquier <lalqu...@gmail.com>wrote: >> >>> Good to hear - I have another bug report on the way regarding External >>> Data (I will send that one to you directly). >>> >>> After using SMW and Forms for a year, I am slowly settling on a personal >>> convention: >>> >>> - Use plain english for the label of the forms and templates >>> - Use the property name for the actual field name >>> >>> That way, the template uses the property names - which makes it easier to >>> automate things afterward (I found myself wanting to analyze properties at >>> the page level, without going to 'Browse date' or 'RDF'... and having >>> different values between properties and field names makes that task more >>> difficult). >>> >>> - Laurent >>> >>> >>> On Fri, May 29, 2009 at 11:33 AM, Yaron Koren <yaro...@gmail.com> wrote: >>> >>>> 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 >>>>> > > >>>>> > >>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >>> -- >>> - Laurent Alquier >>> http://www.linfa.net >>> >> >> >> >> -- >> - Laurent Alquier >> http://www.linfa.net >> >> >> > > > > -- - Laurent Alquier http://www.linfa.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
