[OGo-Developer] OWFormElementName

[Helge Hess]

On Dec 13, 2006, at 09:31, St=E9phane Corth=E9sy wrote:
> OK for 'NAME', but not for 'name'... Template can contain =20
> <WEBOBJECT NAME=3D...> or <webobject name=3D...>

Of course you are right. I actually tried with the lowercase name but =20=

was too blind to see the missing element-id ;-) [only looked for two =20
name attributes getting rendered]

Should be fixed in r1389.


The 'name' is now a special attribute and always gets =20
'uppercased' (during parsing). This is necessary for

   <#abc name=3D"def"/>

style tags, because this has in fact two 'name' bindings (NAME=3Dabc =20
and name=3Ddef).


> (BTW, why does the WO parser checks only for WEBOBJECT/webobject =20
> and NAME/name? Tags should be case-insensitive); latest WOBuilder =20
> always uses lowercase tags.

I've tried:
       <WEBobject NAME=3D"Submit"></WEBOBJECT>
And this works?


>>> , then we should simply remove those (name/NAME) ones from the =20
>>> dictionary passed to addAttributes:toAssociations:.
>> Or skip them ;-)
> I remove them after adding all attributes; it's simply 2 more lines =20=

> after that call.

This breaks 'name' attributes in hash tags.

>> I absolutely agree. The 'WEBOBJECT NAME' shouldn't and has nothing =20=

>> to do with the output.
> OK, fine. So, let's fix that bug.

Done.

Thanks,
   Helge
--=20
Helge Hess
http://docs.opengroupware.org/Members/helge/