[Qt-qml] Cannot store javascript object in property, why?

[Petrus Lundqvist]

> I guess you mean "unbindable", with "bindable" being the default.

No, he meant "bindable" with "unbindable" being the default because he
said "low-overhead solution". :)

> How about the ability to mark a property "private" - e.g.
[snip]
> This would signal that
[snip]
> - Property is not visible outside the .qml file
> - Property does not notify about changes to it. This could be used to
> speed up manipulation of more primitive objects as well (int,
> string...)

I think you are mixing two unrelated things here. Property visibility
with bindability. Bindability is equally (or even more) useful
internally. Killing bindability due to making something private is not
the right behavior IMHO.

Peppe