----- Original Message ----- > From: Samuel Rødal <[email protected]> > On 09/08/2011 03:33 PM, ext Jason H wrote: >> I wholly disagree. It is the core of *your* Qt5 apps, but probably > won't >> be mine. >> It is also a poor decision to say "let them eat cake" and by cake > I mean >> Qt4. >> >> If you put JS into QtCore, then you need to make a QtKernel, however I >> also advise against this because this would create confusion between >> QtCore 4 and QtCore 5. >> >> I've been a proponent of non-gui QML, meaning JS in QCoreApplication >> apps. However as I see it, the JS should be a separate component that is >> included just as SQL is. I even think there is a better argument that >> QtNetwork be put in core, since it is rare not to have any kind of >> network connectivity in this day and age. However, please note that >> recommendation is based on actual observation, whereas your reasoning >> that Qt5 apps will all need JS is based on anticipation. I prefer not to >> be wrong, and when you guess based on supposed future behavior, you will >> very likely be wrong. Let there be a QtJavaScript or QtQMLCore module. > > From my point of view the best argument for having v8 in QtCore is to > have an as efficient as possible bridge between the QObject model and > the QML / JavaScript object model. > > I don't see why v8 couldn't be in QtCore but potentially with a > configure option to disable it for when it's not needed. At least if > it's not possible to get the optimal performance with the v8 / QML > integration outside QtCore. > > A QtKernel that doesn't include QObject also doesn't make much sense, so > > if QObject and JS need to live in the same module that wouldn't solve > anything.
What I don't get is this whole argument that they need to be in the same module to bridge the object model. I don't buy it. There is nothing preventing the QML/JS object model and the QObject model from being the same while living in different modules. QML/JS should be a very useful addition to the QtCore, much like QtSQL, QtNetwork, etc. are. The fact that there is even a valid argument for being able to disable it should it be part of QtCore underscores that it shouldn't be in QtCore to start with. And I quite agree with Lars - let's see how the two new modules for QML/JS work out. I'd add that for Qt5, QML/JS should not be part of QtCore, and rather than trying to force it into QtCore now, let's see how it gets used throughout Qt5, and if there is sufficient usage among the community where having it in a separate module in Qt5 becomes a big hurdle, then we can re-evaluate that position down the line, e.g. Qt6, and change accordingly. The big point here, is let the community and its usage of QML/JS drive the requirement for it being in QtCore. That is part of having open governance, is it not? Ben _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
