> > 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? Tony --------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
