On 9/8/11 3:33 PM, "ext Jason H" <[email protected]> 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. To bring the discussion to an end: Sounds like most people currently prefer keeping the separation and rather have a lib QtJS or QMLCore. Kent and Jedrzej are looking into this idea right now. Let's see how this works out and where the problems are. We can still re-evaluate later on if we find new arguments. Cheers, Lars > > > > > > >________________________________________ >From: Bjørn Erik Nilsen <[email protected]> >To: [email protected] >Sent: Thursday, September 8, 2011 7:25 AM >Subject: Re: > [Qt5-feedback] QML/JS engine in QtCore? > >On 9/8/11 12:59 PM, ext Peter Kuemmel wrote: >> JS in QtCore is not needed in headless embedded software. >> But it would be a reason to not use Qt in such a project if JS couldn't >>be disabled. >> > >Exactly. It would be a good reason to not use *Qt5* in such a project. >Qt4 is more suitable for that use case. > >> I think "Core" is a the wrong name for a library with a complete JS >>interpreter/jit compiler. >> Maybe it is possible to introduce an additional library (QtMicroCore?) >> a level below QtCore which really has only core functionality: signal >>slot, reflection, QString, ... but absolutely nothing gui related >>(QSize, QPoint, >> QState*, QAnimationGroup, QTranslation, ...) >> > >With the vision of Qt5 fresh in mind, it makes perfectly sense to move >JS into QtCore. It *is* the core of all Qt5 applications. > >-- >Bjørn Erik > Nilsen >Software Engineer >Nokia, Qt Development Frameworks >_______________________________________________ >Qt5-feedback mailing list >[email protected] >http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback > > _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
