Re: [Development] The place of QML

> I thought the KDE dudes were already testing it against Qt 5. Anyone > on this list in a position to comment as to the current state of > things? Well, we have been using Harmattan, Plasma Components and so forth for experiments. QML and the component theory are way immature for using this KDE w

Re: [Development] Build failed use MinGW-TDM or MinGW-w64 on Windows

Build failed with the same errors. 2012/5/18 > Just try to do > %QTSOURCE%\configure -opensource > -prefix D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase -confirm-license > -platform win32-g++ -debug-and-release -fast -nomake examples >>config.log > 2>&1 > Instead, and see if that helps. >

Re: [Development] Mutex future directions

On Friday 18 May 2012 23:25:47 Thiago Macieira wrote: > > > QBasicMutex is an internal POD class that offers non-recursive locking. > > > It's incredibly efficient for Linux, where the single pointer-sized > > > member variable is enough to execute the futex operations, in all cases. > > > For othe

Re: [Development] The place of QML

Hey, On Fri, May 18, 2012 at 3:40 AM, Иван Комиссаров wrote: > And what about KDE? It is all based on QWidgets. And it took them many years > to make stable release for KDE 4 (KDE 4.4 was the first release i could > use). You want them to reimplement whole KDE using QML? I thought the KDE dudes

Re: [Development] The place of QML

> Just look at what can be done on the Raspberry Pi with scene graph + > wayland, and tell me you can do the same with QPainter + X11 through the > Pi's main CPU! >    http://www.youtube.com/watch?v=HItv4HX5r3k - Qt 5 and Wayland on the > Raspberry Pi This succinctly summarizes our sentiments; We

Re: [Development] The place of QML

> QML may be revolutionary, but it does not target the right camp. It > targets the designer/amateur-coder audience. "Awww, poor baby. C++ too > hard for you? Here's some meta-descriptive-GUI language where you can > use simple javascript statements/code to implement all your back-end > (and subseq

Re: [Development] The place of QML

This; Widgets is stable API and we will not break your code if you rely on it. Rejoice! Qt 4.6 was a performance release; From Qt 4.5 -> Qt 4.6 we focused on making Qt as performant as possible rather than introducing new functionality. We reached the point of diminishing returns, QWidget is very

Re: [Development] The place of QML

Wayland with shared memory: http://qt-project.org/wiki/RaspberryPi and you are golden. If you are seriously a QWS user, you are a thousand times better off now than you ever were before, Qt/Embedded has an order of magnitude more visibility/resources working on it now. Qt for resource constrained

Re: [Development] Mutex future directions

On sexta-feira, 18 de maio de 2012 22.45.22, Olivier Goffart wrote: > On Friday 18 May 2012 20:34:51 Thiago Macieira wrote: > > Hello > > > > I've just completed a review of the QMutex & family internals, as well as > > the Intel optimisation manuals about threading, data sharing, locking and > > t

[Development] Compiler errors with clang 3.1

I tried both MacPort clang 3.1 and Apple's so-called LLVM 4.0 to build Qt and create apps with C++11 turned on. Both failed with constexpr errors. On the other hand, compiling using gcc 4.7 is successful. I am not sure if gcc is more lex on

Re: [Development] Mutex future directions

On Friday 18 May 2012 20:34:51 Thiago Macieira wrote: > Hello > > I've just completed a review of the QMutex & family internals, as well as > the Intel optimisation manuals about threading, data sharing, locking and > the Transactional Memory extensions. > > Short story: I recommend de-inlining Q

Re: [Development] Mutex future directions

On sexta-feira, 18 de maio de 2012 20.34.51, Thiago Macieira wrote: > (P1) expand the size of QBasicMutex and QMutex to accommodate more data, > for Mac and Windows. On Windows, the extra data required is one pointer (a > HANDLE), whereas on Mac it's a semaphore_t. Depending on the next task, we >

[Development] Mutex future directions

Hello I've just completed a review of the QMutex & family internals, as well as the Intel optimisation manuals about threading, data sharing, locking and the Transactional Memory extensions. Short story: I recommend de-inlining QMutex code for Qt 5.0. We can re-inline later. I also recommend incr

Re: [Development] The place of QML

Hello, I've been following this thread since it started. My impression is that Qt people believes we (users-devs) want to force you into further developing a C++ toolkit (which might or might not be outdated). But I understand that you will do work on what are *ordered* to work on, by your boss. I

Re: [Development] Using Transifex for handling Qt localization?

Hi all, I also neglected to introduce myself -- I'm the chief ninja at Transifex and its original developer. I'd be happy to answer any questions. ## More information to help create a better picture Using the common instance on Transifex.net allows you to re-use existing open-source translators

Re: [Development] Using Transifex for handling Qt localization?

On 05/18/2012 01:46 AM, ext Oswald Buddenhagen wrote: > one thing to consider is that some translators may not particularly like > the idea of using a proprietary web app for their work, so gerrit would > still need to be the authoritative repository with "normal" submissions > enabled. i think tha

Re: [Development] QWindowSystemInterface::handleMouseEvent() relative or absolute?

On 05/18/2012 05:22 PM, ext Girish Ramakrishnan wrote: > Related: eglfs currently is just a "graphical" plugin and has no input > support out of the box. eglfs (from it's background as a reference for > qpa) has however become the gold standard for practically all devices > using Qt5 in the absenc

Re: [Development] Help: Qt CS pre-scheduled sessions

On 05/18/2012 12:03 AM, Di-Flora Cristiano (Nokia-MP/Tampere) wrote: > Hi Quim, > > I can (and would be happy to) arrange a session about QtPim APIs > (Contacts, Organizer, Versit) in 5.0 and changes / evolution of those APIs > from the QtMobility ones. Pre-scheduled for Friday morning. http://qt

Re: [Development] QWindowSystemInterface::handleMouseEvent() relative or absolute?

Hi Laszlo, On Tue, May 15, 2012 at 10:45 PM, Laszlo Agocs wrote: > > Hi, > > Because windowing systems will usually provide absolute coordinates in > their pointer events, hiding all the cursor management, raw event > translation, etc. hassle from the clients. Also the Qt events contain > absolut

[Development] Avoiding 'random' app.quit() in QtQuick applications.

Hi there, The issue raised in this thread: http://thread.gmane.org/gmane.comp.lib.qt.user/1880 Can be simplified to this example: QWindow window; QWidget widget; window.show(); widget.show(); // This should not quit the application, because // the QWindow is still op

Re: [Development] qtphonon's status.

On Friday, May 18, 2012 10:43:18 you wrote: > Right, no attention from us and no attention from the phonon developers, at > least with respect for Qt 5 end-users. So, by it receiving 'attention' from > us now by simply removing the old "fork" from the repo, it would only hurt > the end-user, makin

Re: [Development] The place of QML

On 05/18/2012 09:07 AM, marius.storm-ol...@nokia.com wrote: > Often it's hard to beat the performance of the main CPU(s for most people > these days) filling in a polygon directly, rather than handing it off to a > GPU. Guess this is the reason behind the decision why in Qt 4.8 raster has become

Re: [Development] The place of QML

Kate: > > Often, the proponents arguing for "new and improved" are > > simply arguing for the position they think will be most fun > > to work on; after all, it's always more fun to break exciting > > new ground than it is to have trod the same old sod yet again. > > But many of these new app

Re: [Development] qtphonon's status.

On 5/18/12 12:02 PM, "ext Stephen Kelly" mailto:stephen.ke...@kdab.com>> wrote: On Friday, May 18, 2012 08:41:13 marius.storm-ol...@nokia.com wrote: > We did promise a minimal migration path from Qt 4 to Qt 5, and removing > the phonon module from qt5.git,

Re: [Development] The place of QML

You need users who will use Qt to survive. And those are desktop developers. Show me lot of not "hello world" apps writte using qml. Where are they? On symbian? Maybe in MeeGo? I don't see any on the desktop. But i see Guitar Pro right now which is based on QWidgets. About O-notations. Article

Re: [Development] qtphonon's status.

On Friday, May 18, 2012 08:41:13 marius.storm-ol...@nokia.com wrote: > >Until the Phonon maintainers speak up and let us know what their plans > >for Qt > >5 are, we should consider our qtphonon.git module a disservice to > >everyone. If > >none of them speak up, I recommend removing the module fro

Re: [Development] Build failed use MinGW-TDM or MinGW-w64 on Windows

Just try to do %QTSOURCE%\configure -opensource -prefix D:/qpSOFT/Projects/BuildQt5-x86-tdm/qtbase -confirm-license -platform win32-g++ -debug-and-release -fast -nomake examples >>config.log 2>&1 Instead, and see if that helps. -- .marius On 5/18/12 11:37 AM, "ext Loaden" mailto:loa...@gma

Re: [Development] Build failed use MinGW-TDM or MinGW-w64 on Windows

What is the time to merge the origin/buildsystem into origin/master? When it's ready? or have a plan? I am do not set the QTDIR env value as the wiki says. The mean the 'QTDIR' env does not exist. The configure command on Windows: > %QTSOURCE%\configure -opensource -prefix %CD%\qtbase -confirm-l

Re: [Development] Using Transifex for handling Qt localization?

On Wed, May 16, 2012 at 03:55:41PM -0700, ext Quim Gil wrote: > - How valuable is to have an efficient tool for handling translations > between teams - as opposed to whatever process we have now? Are we happy > with the current system? Do we believe we would improve significantly > with a tool l

Re: [Development] qtphonon's status.

On 5/18/12 10:14 AM, "ext Thiago Macieira" wrote: >On sexta-feira, 18 de maio de 2012 05.54.10, marius.storm-ol...@nokia.com >wrote: >> This probably means we should keep the old repo there for backwards >> compatibility, and with documentation stating that the module is old and >> out-of-date, a

Re: [Development] The place of QML

On Thu, May 17, 2012 at 1:35 PM, Atlant Schmidt wrote: > Peter, et al.: > >> We don't wanna use obsolete stuff with a "architecture from >> the 90s" in times where "graphical technology has moved on" (Thiago). > >  Computer architectures don't necessarily "become obsolete". >  Oh, trends come and

Re: [Development] qtphonon's status.

On sexta-feira, 18 de maio de 2012 05.54.10, marius.storm-ol...@nokia.com wrote: > This probably means we should keep the old repo there for backwards > compatibility, and with documentation stating that the module is old and > out-of-date, and where and how they can get a more recent version. I

[Development] QtCS: Calling all Qt/Qt SDK maintainers

Hi, on QtCS, we will have a session on Qt and Qt SDK packaging. The exact details are can be found at http://qt-project.org/groups/qt-contributors-summit-2012/wiki/Packaging-Qt. If you want to attend or have any addition to the program, feel free to amend the wiki page. If you have questions. a

Re: [Development] The place of QML

On 5/15/12, BRM wrote: > It would probably be good for a statistically significant poll to be > officially done. > I'd expect that it would probably have a 50/50 split, or may be a 60/40 > split in favor of QML > as I do expect there is still a lot of momentum behind the QWidgets and > QGraphics*

Re: [Development] The place of QML

On 5/18/12 8:22 AM, "ext Uwe Rathmann" wrote: >I would be careful with terms like "outdated". In the end the desktop is >the concept of the 90s ( widget are much older ) and the current >desktops are the part that doesn't work on smartphones alike devices. >But are keyboard and mouse outdated - on

Re: [Development] Help: Qt CS pre-scheduled sessions

Hi Quim, I can (and would be happy to) arrange a session about QtPim APIs (Contacts, Organizer, Versit) in 5.0 and changes / evolution of those APIs from the QtMobility ones. Gerrit / Git history for qtpim repo shows that the number of contributors has been quite limited so far, so definitely a sm