Sounds like marketing?
It might be a 'constant' in the grand scheme of big-O notations. However,
if the result is that you can only get 24 fps on low-end HW with large
power footprint vs. 60 fps with HW acceleration, lower power footprint and
leaving the main CPU to do more important tasks, what w
On 05/18/2012 07:36 AM, Иван Комиссаров wrote:
> Btw, you're saying that painter technology is outdated?
Well it is also the API for rendering PDF ( and other paint devices )
documents. Having common code for screen and PDF rendering is absolutely
not outdated - and is possible using QSGPaintedI
Based on the output below, I think there might be a path invariance between
prefix and QTDIR, if you have that set.
So, make sure that $$QTDIR is the same as $$[QT_HOST_PREFIX]. If you have QTDIR
set, then qmake will pass '-qtdir ' to syncqt on invocation. Check that
against what 'qmake –query
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.
We shouldn't mix build systems in qt5.git itself. If other add-ons decide
to use cmake as
Btw, you're saying that painter technology is outdated? What speedup provides
QML scene graph? According to this
http://labs.qt.nokia.com/2011/05/31/qml-scene-graph-in-master/ article, speedup
is 2.5 times. As for me, it's just a constant optimization, it is not reduces
complexity very much, as
1. It successful use MSVC2010 for shadow (out-of-source) , no need 'make
install' things
2. In-Source-Build also failed with MinGW-TDM
2012/5/15
> You need to make install after building each module to copy the output to
> the prefix directory you specified in configure.
>
> The top level makefi
On Thursday 17 May 2012 21:42:03 Thiago Macieira wrote:
> On quinta-feira, 17 de maio de 2012 19.03.30, lars.kn...@nokia.com wrote:
> > >What's the difference between webkit and phonon in this regard?
> >
> > Webkit isn't hosted on qt-project neither, so removing it from qt-project
> > is the righ
> Off-Topic
> -
>
> I don't see this email in j...@qt-project.org mailing list. So that's
> maybe why you haven't gotten any answer yet.
>
> http://lists.qt-project.org/pipermail/jeg/2012-May/thread.html
I am unsure what is wrong with me to clearly explain the significance
of this issue, a
On quinta-feira, 17 de maio de 2012 19.03.30, lars.kn...@nokia.com wrote:
> >What's the difference between webkit and phonon in this regard?
>
> Webkit isn't hosted on qt-project neither, so removing it from qt-project
> is the right choice if it's being developed somewhere else.
The "qt5-module.
On quinta-feira, 17 de maio de 2012 14.46.16, Atlant Schmidt wrote:
> Girish:
> > Substantial recoding on the application side? What features
> > of QWS are you relying on that is missing in QPA?
>
> The ability for multiple processes to share a single
> display device (framebuffer).
Have you
On 5/17/12 8:36 PM, "ext Stephen Kelly" wrote:
>On Thursday, May 17, 2012 18:31:43 lars.kn...@nokia.com wrote:
>> I don't want to maintain a fork of phonon on qt-project if the
>>developers
>> decided they want to continue within the KDE infrastructure. phonon
>>should
>> have one upstream place
On 05/16/2012 03:55 PM, ext Quim Gil wrote:
> On 05/15/2012 01:54 AM, ext Oswald Buddenhagen wrote:
>> On Mon, May 14, 2012 at 03:31:34PM -0700, ext Quim Gil wrote:
>>> Dimitris Glezos from Transifex saw
>>> http://qt-project.org/wiki/Qt-Localization . This is the page where we
>>> explain how to l
Girish:
> Substantial recoding on the application side? What features
> of QWS are you relying on that is missing in QPA?
The ability for multiple processes to share a single
display device (framebuffer).
Atlant
-Original Message-
From: Girish Ramakrishnan [
Hi Atlant,
On Thu, May 17, 2012 at 11:18 AM, Atlant Schmidt
wrote:
> Peter:
>
>> Then Qt Widgets is perfect for you: mature, stable API. You
>> only would have a problem when you have to implement features
>> which are much better supported by QML.
>
> Did I mention that we're also coded to depe
On Thursday, May 17, 2012 18:31:43 lars.kn...@nokia.com wrote:
> I don't want to maintain a fork of phonon on qt-project if the developers
> decided they want to continue within the KDE infrastructure. phonon should
> have one upstream place where it is being developed.
>
> I'd say let's deprecate
I don't want to maintain a fork of phonon on qt-project if the developers
decided they want to continue within the KDE infrastructure. phonon should
have one upstream place where it is being developed.
I'd say let's deprecate the module and remove it from qt5.git. We can keep
the code around for s
Peter:
> Then Qt Widgets is perfect for you: mature, stable API. You
> only would have a problem when you have to implement features
> which are much better supported by QML.
Did I mention that we're also coded to depend upon QWS, the
QT Embedded Window System? ;-)
That feature is no longe
On Thu, May 17, 2012 at 7:37 PM, Stef Bon wrote:
> Then contacted Thiago Macieira for suggestions about howto test
> notifyfs (that’s the name of it) as backend of QFileSystemWatcher. He
> suggested me posting a message here, since QFileSystemWatcher is
> “flawed by design” (his words) and a repla
Hi,
I’ve been working on a filesystem event watcher for some time now. As
user of KDE I contacted first the developers of kDirWatch. They send
me to developers of Qt, because the KDirWatch is being deprecated, as
the same is done already in Qt.
Then contacted Thiago Macieira for suggestions about
On 17.05.2012 12:35, 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 trends go
On 17.05.2012 14:42, Иван Комиссаров wrote:
> Well, i do care about what happen to QWidgets. Maybe i'm old-fashioned (i'm
> 23 years old, heh), but i do have lot of code based on QWidgets. And that
> code works. So, you suggest me to thow away all code i've made, because
> QWidgets have bad desi
On Thursday 17 May 2012 14:46:27 Pier Luigi wrote:
> 2012/5/16 Thiago Macieira :
> > [cross-posting to kde-multimedia]
> >
> > On quarta-feira, 16 de maio de 2012 18.55.52, Olivier Goffart wrote:
> >> Hi,
> >>
> >> Why do we mantain an outdated fork of phonon in qt5.git
> >> I am talking about th
I favour proposal 2.
The legacy URL schemes (ftp and file for what we implement) need to deal with
fully decoded fragments.
The less discoverable con is not so much of a con as this API is mainly
required to implement a protocol rather than to use it.
--
> -Original Message-
> From: de
This has been said before, but for the sake of clarity:
On 05/17/2012 05:42 AM, ext Иван Комиссаров wrote:
> i do have lot of code
> based on QWidgets. And that code works. So, you suggest me to thow
> away all code i've made, because QWidgets have bad design?
No, we suggest you to run that code
This has been said before, but for the sake of clarity:
On 05/17/2012 05:42 AM, ext Иван Комиссаров wrote:
> i do have lot of code
> based on QWidgets. And that code works. So, you suggest me to thow
> away all code i've made, because QWidgets have bad design?
No, we suggest you to run that code
> Yes, that's the idea.
Practice has disagreed so far.
Best Regards,
Laszlo Papp
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi Pier,
On Thu, May 17, 2012 at 5:46 AM, Pier Luigi wrote:
> 2012/5/16 Thiago Macieira :
>> [cross-posting to kde-multimedia]
>>
>> On quarta-feira, 16 de maio de 2012 18.55.52, Olivier Goffart wrote:
>>> Hi,
>>>
>>> Why do we mantain an outdated fork of phonon in qt5.git
>>> I am talking about
2012/5/16 Thiago Macieira :
> [cross-posting to kde-multimedia]
>
> On quarta-feira, 16 de maio de 2012 18.55.52, Olivier Goffart wrote:
>> Hi,
>>
>> Why do we mantain an outdated fork of phonon in qt5.git
>> I am talking about the qtphonon repository.
>>
>> The Phonon team maintains phonon under t
Well, i do care about what happen to QWidgets. Maybe i'm old-fashioned (i'm 23
years old, heh), but i do have lot of code based on QWidgets. And that code
works. So, you suggest me to thow away all code i've made, because QWidgets
have bad design? And whst i got? Unfinished yet QML? Thanks, i'd
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 trends go, but the fundamental concepts
go on forever. For exa
30 matches
Mail list logo
