Thanks for you answer.

> Exactly. This is due to the reason that all data loaded from the server or in 
> general used for creating a model will be converted to >qooxdoo objects which 
> define setter and getter for its properties. This means, that in your case 
> the getter needs to be name like >"getFirst-name" which is not a valid 
> JavaScript identifier. So the restriction comes from JavaScript, not really 
> from qooxdoo itself.
Maybe it will be a good idea to add some warinning about that in the
jsdocs of qx.data.array.

> Thats only half true. It doesn't fail because we are aware of that problem. 
> Thats why we build in a remove of "-" before creating the >model. Try to 
> access your data without the - in it and see its working.

About the "silent" failling. I thik i will be easier if the controller
complains when it get a model that does match all the items of the
target. Not failing because it woulb be impossible to set a null
model, but if it send a warning messageor log message. It will be
helpfull, i think.

Regards

-- 
Benjamin Dreux
Analyste-Programmeur
Chaire de logiciel libre-Finance Social et solidaire
UQAM
Montréal

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to