On Friday 14 November 2014 09:08:11 Thiago Macieira wrote:
> All of those you listed are true, but you're asking for us to work around a
> structural problem in X (which we usually do). And in fact, we're already
> doing the necessary changes to support high DPI. I don't think the DPI is an
> issue
Hi Harri,
Our measurements with Qt Quick Compiler 1.0 with different kind of projects
indicate that a typical mid-sized Qt Quick application startup is 30-40% faster
with compiled Qt Quick. This is an excellent improvement and we believe we can
improve this even more in the future. The highest
On 15 November 2014 03:58, André Pönitz wrote:
>
> On Fri, Nov 14, 2014 at 10:06:32AM +0100, Yann Levreau wrote:
> > Hi everybody!
> >
> > I am starting a new project and I am looking for some advice about what
> > kind of Qt/QML controls I should use. The purpose is to develop an rich
> > text e
On Friday 14 November 2014 22:23:52 Genghis Khan wrote:
> Hello,
>
> I was wondering if anyone on this list knows of a trusted source where
> one can achieve Slackware binary package of Qt5.
>
> Alternatively, provide me with a solution for overcoming the following
> error during compilation (see
On Friday 14 November 2014 22:27:11 René J.V. Bertin wrote:
> On Friday November 14 2014 13:01:47 Thiago Macieira wrote:
> >#include
> >
> >when using frameworks will look for QtCore.framework/Headers/qglobal.h,
> >which is a shared name between Qt 4 and Qt 5. Since you can't have the
> >same
> Ye
Hello,
I was wondering if anyone on this list knows of a trusted source where
one can achieve Slackware binary package of Qt5.
Alternatively, provide me with a solution for overcoming the following
error during compilation (see file attached).
sed: can't read /tmp/SBo/package-qt5/usr/lib/pkgconf
On Friday 14 November 2014 21:44:51 René J.V. Bertin wrote:
> On Friday November 14 2014 11:04:29 Thiago Macieira wrote:
> >But we can't and won't. That breaks both source and binary compatibility.
>
> Wasn't saying you should but I don't see why it would break anything ... for
> those who build t
On Friday 14 November 2014 18:30:18 René J.V. Bertin wrote:
> > Therefore, you need to install them in separate prefixes.
>
> Yes, Apple's support for multiple versions in a single framework is limited
> to backward compatibility; the linker will always pick the newest version.
> Python allows you
On Friday November 14 2014 09:14:47 Thiago Macieira wrote:
Hi and thanks,
> In framework builds of OS X, Qt 4 and Qt 5 are not co-installable, since they
> claim the same names like QtCore.framework. We decided early on in the Qt 5.0
...
> Therefore, you need to install them in separate prefix
On Friday 14 November 2014 16:52:09 René J.V. Bertin wrote:
> Hi,
>
> My main work environment is under OS X, based on MacPorts. It is currently
> not possible with that framework to have Qt4 and Qt5 installed in parallel;
> it's one or the other, installed into ${prefix} (usually /opt/local).
>
On Friday 14 November 2014 12:41:08 Stanislav Baiduzhyi wrote:
> > > 2. Read 'dpi' config value from fontconfig.
> >
> > Disagreed. The DPI value comes from the windowing system, not from
> > fontconfig.
>
> There are multiple issues with that. I'm talking about X right now:
[cut]
All of those y
Hi,
My main work environment is under OS X, based on MacPorts. It is currently not
possible with that framework to have Qt4 and Qt5 installed in parallel; it's
one or the other, installed into ${prefix} (usually /opt/local).
I don't know why the Qt4/5 port maintainer didn't set things up from t
El Friday 14 November 2014, Harri Pasanen escribió:
> A related question, has anyone tried to coax QML, or rather the
> javascript components through the Closure Compiler?
> https://developers.google.com/speed/articles/compressing-javascript
>
> It might help a little, especially with javascript
Actually I was less interested in the compilation time than what it is
the return for the investment.
Reading the compiler docs, they recommend disabling the compilation for
debug builds, as it can interfere with debugging. So through configure
the build/deploy cycle should stay the same for de
AFAIK, you need to turn it on by qmake option CONFIG, eg:
qmake CONFIG+="release qtquickcompiler"
On Fri, Nov 14, 2014 at 8:24 PM, rpzrpz...@gmail.com
wrote:
> Then that would make the benchmarks that Harri requested a mute point.
>
> Unless you "make clean", the incremental build would not care
El Friday 14 November 2014, ashish dabhade escribió:
> No need to click even. It happens during load. Loading locally works as
> expected. The JS file is proper. Just a single function in it
I have to admit my ignorance respect network transparency with Qt Quick, but
I've searched a bit and I've
Probably lack of similar problems with my screens (both notebook and
desktop) made me over-optimistic. :)
On 11/14/2014 03:20 PM, Stanislav Baiduzhyi wrote:
> On Friday 14 November 2014 15:10:05 Constantin Makshin wrote:
>> On 11/14/2014 02:41 PM, Stanislav Baiduzhyi wrote:
>>> - when you're using
On Friday 14 November 2014 13:20:32 Stanislav Baiduzhyi wrote:
> forcing proper DPI resolution is one of major world problems at the
moment.
*kopfschüttel*
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/in
Then that would make the benchmarks that Harri requested a mute point.
Unless you "make clean", the incremental build would not care about
10,000 lines of QML code. It would only "slow" down on the changed QML.
Is there an option to turn off the Quick Compiler for beta builds and
only kick it on
On Friday 14 November 2014 15:10:05 Constantin Makshin wrote:
> On 11/14/2014 02:41 PM, Stanislav Baiduzhyi wrote:
> > - when you're using some brand new laptop your physical screen dimension
> > may not be present in X db yet, which means that X just takes your screen
> > resolution, assumes 96dpi
On 11/14/2014 02:41 PM, Stanislav Baiduzhyi wrote:
> - when you're using some brand new laptop your physical screen dimension may
> not be present in X db yet, which means that X just takes your screen
> resolution, assumes 96dpi and calculates physical dimensions based on that,
> which usually
On Thursday 13 November 2014 20:12:46 René J.V. Bertin wrote:
> > solve the majority of issues:
> ... fontconfig ... XDG
>
> > That's all that needed to make Qt5 look bearable on
> > unconfigured/unsupported desktop.
>
> There you go ... Linux is the new MS Windows? :)
> Fontconfig is present on
On Thursday 13 November 2014 14:59:19 Thiago Macieira wrote:
> > Which means that we should not use Qt5 apps on less supported desktop
> > environments and we should not use Qt5 apps launched under another user
> > with empty home folder?
> No, it means Qt 5 needs to support those desktops too, as
According to a quick test I did just now, with Qt 5.4-beta (Qt Quick Compiler
2.0) on msvc2013, it only re-compiles the changed qml files.
Best regards,
Alessandro Portale
Betreff: Re: [Interest] Qt Quick Compiler
Does the quick compiler only re-compile t
24 matches
Mail list logo
