On 15 November 2013 20:49, Heikkinen Jani wrote:
> Hi all,
>
> According to plan we should have Qt5.2 RC1 during next week. So please start
> updating the known issues page for RC1
>
>
>
> And please inform me immediately if you know something is blocking the
> release and not listed in
> https://
On Fri, Nov 15, 2013 at 2:17 PM, Kevin Krammer wrote:
> [...]
>> Quoting your latest post:
>> > I can understand that you'd like to have the same script engine evaluate
>> > both types of script, but since the decision was to make an optimized
>> > version for QML, you can either try to shoehorn y
On Fri, Nov 15, 2013 at 1:58 PM, Richard Moore wrote:
> On 15 November 2013 19:51, Alan Alpert <4163654...@gmail.com> wrote:
>> On Fri, Nov 15, 2013 at 2:00 AM, Kevin Krammer
>> wrote:
>>> On Thursday, 2013-11-14, 21:20:25, Topi Mäenpää wrote:
>>>
>>> I also wouldn't consider widgets to be depre
On Friday, 2013-11-15, 23:04:40, Topi Mäenpää wrote:
> > That could have been a miscommunication. What they probably meant was that
> > the standard QtQuick module would not have a QML type for QScriptEngine.
> I didn't need to be told this. I mean, who would really suggest having a
> JavaScript en
On 15 November 2013 19:51, Alan Alpert <4163654...@gmail.com> wrote:
> On Fri, Nov 15, 2013 at 2:00 AM, Kevin Krammer wrote:
>> On Thursday, 2013-11-14, 21:20:25, Topi Mäenpää wrote:
>>
>> I also wouldn't consider widgets to be deprecated, at least not yet. And
>> nicely use QML with widgets as th
On Fri, Nov 15, 2013 at 1:04 PM, Topi Mäenpää wrote:
> [...]
> In Qt4, widgets were still the main UI technology. Nowadays, widgets are
> "deprecated". (I'm putting quotes due to the comments to my last post,
> but it is really not hard to see where the development is heading.)
> Prior to QML apps
> That could have been a miscommunication. What they probably meant was that the
> standard QtQuick module would not have a QML type for QScriptEngine.
I didn't need to be told this. I mean, who would really suggest having a
JavaScript engine inside a JavaScript engine? I could see the reason if
On Friday, 2013-11-15, 21:51:37, Topi Mäenpää wrote:
> > I think the existence of JavaScript context in QML should be considered a
> > feature of QML, not of Qt or the application itself.
>
> Sure, as far as the Qt application is not a QML application. If you run
> the app with qmlscene, the "Qt a
On Friday, 2013-11-15, 11:51:43, Alan Alpert wrote:
> On Fri, Nov 15, 2013 at 2:00 AM, Kevin Krammer
wrote:
> > On Thursday, 2013-11-14, 21:20:25, Topi Mäenpää wrote:
> >> I considered the options carefully before switching to Qt5. I talked to
> >> Digia engineers and they told me the same you a
On Fri, Nov 15, 2013 at 11:51 AM, Topi Mäenpää wrote:
>> I think the existence of JavaScript context in QML should be considered a
>> feature of QML, not of Qt or the application itself.
>
> Sure, as far as the Qt application is not a QML application. If you run
> the app with qmlscene, the "Qt ap
On Fri, Nov 15, 2013 at 2:00 AM, Kevin Krammer wrote:
> On Thursday, 2013-11-14, 21:20:25, Topi Mäenpää 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, whic
> I think the existence of JavaScript context in QML should be considered a
> feature of QML, not of Qt or the application itself.
Sure, as far as the Qt application is not a QML application. If you run
the app with qmlscene, the "Qt application" is a pure QML application.
> There is a module sp
On Fri, 15 Nov 2013 15:53:46 +
wrote:
> I think issue https://bugreports.qt-project.org/browse/QTBUG-34624 should get
> a higher priority.
Naaa... this is only an iOS problem. Absolutely not important. ;-)
And if you think, it is more important... vote for it.
Guido
__
I think issue https://bugreports.qt-project.org/browse/QTBUG-34624 should get a
higher priority.
发自 Windows 邮件
发件人: Heikkinen Jani
发送时间: 2013年11月15日, 星期五 20:49
收件人: development@qt-project.org
Hi all,
According to plan we should have Qt5.2 RC1 during next week. So please start
Hi all,
According to plan we should have Qt5.2 RC1 during next week. So please start
updating the known issues page for RC1
And please inform me immediately if you know something is blocking the release
and not listed in https://bugreports.qt-project.org/browse/QTBUG-33863
Br,
Jani
---
I am sorry, it was thinking of backporting object_parallel_to_source :>
Regards,
--
Adam
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Thursday, 2013-11-14, 21:20:25, Topi Mäenpää 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
On Thursday 14 November 2013 21:20:25 Topi Mäenpää wrote:
> Qt is heading to a JavaScript-based future. Widgets are deprecated and
> replaced by QML.
This is not true, Widgets are _not_ deprecated. It's true that more and more
people adapt QML for UI designing, but you are free to choose.
htt
On Monday, 2013-11-11, 10:38:28, Topi Mäenpää wrote:
> I've been using Qt's JavaScript engines to provide a scripting interface
> to Into about ever since QScriptEngine was introduced. It provided
> fairly good extension interfaces and I was able to implement almost
> everything I wanted using the
On quinta-feira, 14 de novembro de 2013 23:41:12, Stephen Kelly wrote:
> On Thursday, November 14, 2013 08:49:04 Thiago Macieira wrote:
> > First of all, you seem to be linking statically to glibc. Don't.
>
> You seem to start with an assumption that I changed something. Don't.
>
> This is using
On 15 Nov 2013, at 09:37, Martin Smith wrote:
>
> On Nov 15, 2013, at 9:32 AM, Sorvig Morten
> wrote:
>>
>> (and someone needs to port tools/qdoc/qmlparser)
>
> I just did that a couple weeks ago. Has there been a more recent update?
No, it’s ok. I was looking at a stale checkout of qtbase.
On Nov 15, 2013, at 9:32 AM, Sorvig Morten
wrote:
>
> On 14 Nov 2013, at 09:39, Stephen Kelly wrote:
>
>>
>> Hello,
>>
>> I get build errors when trying to build qtbase dev branch for raspbian.
>> /home/stephen/dev/src/qtbase/src/tools/qdoc/qmlvisitor.cpp:51:0:
>> /home/stephen/dev/src/qt
On 14 Nov 2013, at 09:39, Stephen Kelly wrote:
>
> Hello,
>
> I get build errors when trying to build qtbase dev branch for raspbian.
> /home/stephen/dev/src/qtbase/src/tools/qdoc/qmlvisitor.cpp:51:0:
> /home/stephen/dev/src/qtbase/src/tools/qdoc/qmlvisitor.h:78:29: error:
> ‘QQmlJS::AST::Ui
23 matches
Mail list logo
