thiago.macieira at intel.com
Thu Nov 14 18:31:08 CET 2013
On quinta-feira, 14 de novembro de 2013 17:25:08, Tony Van Eerd wrote:
> > But that's a long term plan, v4vm isn't even released yet (new in 5.2
> > remember) and there's still tons of work to do. Until v4vm is ready to
> > take over from QtScript, which will still be a while, I believe the
> > recommendation is to keep using QtScript. It's deprecated and "done"
> > because we've reallocated development priorities, but until we've
> > finished its replacement it is your best option. Even though it means
> > using old or no QML, it sounds like the JS support is more important
> > for you.
> Where do value-types (ie non-QObject, copyable, etc) fit into the plan?
> I find that forcing classes to be QObjects just to make them QML accessible
> really denigrates some API designs. Any advice?
Value-type classes need adaptation to work in QML. Make them sharable,
copyable, whatever is needed, then we need to figure out how to make QML
The metatype system is a start, since it can manage those types' lifetime. I
think it can even compare them for equality these days.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 190 bytes
Desc: This is a digitally signed message part.
More information about the Development