Hi,
On Wed, May 23, 2012 at 11:33 PM, Jørgen Lind wrote:
> I think we should focus on keeping eglfs as small as possible, but
> keeping the readability of the code, so that the entry level for "extending"
> eglfs will be low.
>
I think this is the first thing that needs to be discussed :-)
We h
Jean had the supporting votes and it has been a couple of weeks now.
Therefore, congratulation Jean to becoming an approver.
--
Alex
> -Original Message-
> From: development-bounces+alex.blasche=nokia@qt-project.org
> [mailto:development-bounces+alex.blasche=nokia@qt-project.org
Hi
> The initial issue with our current input handling for platforms like eglfs,
> which do not handle input on its own, is, that we have input plugins for
> mouse/keyboard/touch (evdev), which are seperate from each other.
> So one needs to specify "-plugin evdevkeyboard" on the commandline in o
Hi,
Finally there is some progress with the bin packaging.
There is now jenkins creating desktop installers twice a day, if there is
change in git. Currently it detects the git 7 am and pm (GMT +2).
First it creates the beta src package
(http://origin.releases.qt-project.org/qt5.0-beta-latest/),
Hi,
Please do not merge the plug-ins. A monolithic "evdev" monster plug-in is not
desirable and would certainly not classify as "generic" anymore.
The "static device discovery" should check the supported event types from the
devices (this needs opening, an ioctl, and some bittesting so might no
Hi everyone,
I have some questions about QTSDK4.8:
1)Are the libs used in QTSDK4.8 built from qt-everywhere-opensource?
2)if 1) is yes, is there anybody can tell me the total build options for the
QTSDK4.8's libs building?
Any help will be appreciated!
Thanks!
--
-??-
--
Regards
Zhang Da Wei
A
Hi Rene,
I certainly agree that constructive discussion about the QML language and ways
that it could be improved are important. You raise a lot of important points,
some of which will be addressed in Qt5.0, some of which we still need to
consider how to fix, and what priority they should be,
> Unfortunately, for all sysadmin-related jobs, we have legal issues that need
> to be dealt with, so it's not as simple as starting to do it. I don't know how
> to go from here.
I would personally like to see as much Open Governance in the Qt
Project as possible. This is also relevant for sysadmi
As per QTBUG-25122 (https://bugreports.qt-project.org/browse/QTBUG-25122 ), I
would like to remove the obsolete overload of the QQmlEngine::importPlugin()
function.
I am not aware of any remaining users of this overload - if you are still using
it and need some time to migrate to using the impr
On Wed, May 23, 2012 at 2:00 PM, Giuseppe D'Angelo wrote:
> On 23 May 2012 20:03, Girish Ramakrishnan wrote:
>> Hi Andreas,
>>
>> On Wed, May 23, 2012 at 11:12 AM, Andreas Holzammer
>> wrote:
>>> Hi,
>>>
>>> I wanted to backport the support for Windows 8 to Qt 4.8, which is
>>> already done for
On quarta-feira, 23 de maio de 2012 23.44.57, Carsten Breuer wrote:
> Hi Thiago,
>
> thanks for clearing this :-)
>
> >> I guess it depends a bit on if you want to yield to another thread or
> >> not ;-). Of course: burning cpu time is another way to solve this ;-)
> >
> > According to the Intel ma
Hi Thiago,
thanks for clearing this :-)
>> I guess it depends a bit on if you want to yield to another thread or
>> not ;-). Of course: burning cpu time is another way to solve this ;-)
>
> According to the Intel manual, if you *don't* yield and you don't have the
> PAUSE instruction, you may m
On quarta-feira, 23 de maio de 2012 13.30.05, 1+1=2 wrote:
> In addition, this will improve the unicode handling ability of Qt
> tools with using bootstrap. Otherwise, tools such as qmake can not
> deal with UTF-8 encoded files.
That is irrelevant. qmake operates on Latin1 exclusively because it
On quarta-feira, 23 de maio de 2012 22.52.55, Carsten Breuer wrote:
> Hi Bradley,
>
> >> And I don't think they very much liked the idea of spinning while trying
> >> to
> >> acquire a lock (consumes power)... at least we have a call to
> >> QThread::yieldCurrentThread(), though it would be interes
On 23 May 2012 20:03, Girish Ramakrishnan wrote:
> Hi Andreas,
>
> On Wed, May 23, 2012 at 11:12 AM, Andreas Holzammer
> wrote:
>> Hi,
>>
>> I wanted to backport the support for Windows 8 to Qt 4.8, which is
>> already done for Qt5 in https://codereview.qt-project.org/#change,22940
>> With this c
Hi all,
I'm having a similar issue, but a bit farther off the beaten path. I'm on
VS2008, but trying to cross compile for Wince.
I can get the compile to finish after applying a number of patches and
hacks, but only if I manually add QtV8 to the include and lib paths for a
bunch of qtdecla
Hi Bradley,
>> And I don't think they very much liked the idea of spinning while trying to
>> acquire a lock (consumes power)... at least we have a call to
>> QThread::yieldCurrentThread(), though it would be interesting to see what
>> happens if we replace it with a PAUSE instruction.
> Have y
Hi all,
It might be a bit late for 5.0.
But Qt 5 have started to enforce that source code file must be UTF-8.
So perhaps it make sense to change the default codec of QTextStream to
UTF-8.
This won't break many things, as the old behavior can be obtained by
calling QTextStream::setCodec().
I have
Hi,
as we are working on better support of embedded devices in Qt, we also are
tapping into the input handling.
The initial issue with our current input handling for platforms like eglfs,
which do not handle input on its own, is, that we have input plugins for
mouse/keyboard/touch (evdev), whi
Hi Andreas,
On Wed, May 23, 2012 at 11:12 AM, Andreas Holzammer
wrote:
> Hi,
>
> I wanted to backport the support for Windows 8 to Qt 4.8, which is
> already done for Qt5 in https://codereview.qt-project.org/#change,22940
> With this change a symbol is added and therefore binary compatibility is
Hi,
I wanted to backport the support for Windows 8 to Qt 4.8, which is
already done for Qt5 in https://codereview.qt-project.org/#change,22940
With this change a symbol is added and therefore binary compatibility is
broken. I know i cannot do that for Qt 4.8, so my question if we should
do this an
All:
> W00t should have a backlog which covers the conversation,
> if it was done on our public channels :-)
If only Pierre de Fermat had had that feature!
Atlant
-Original Message-
From: development-bounces+aschmidt=dekaresearch@qt-project.org
[mailto:dev
W00t should have a backlog which covers the conversation, if it was done on our
public channels :-)
--
Sent from my Nokia N9On 5/23/12 13:44 ext Thiago Macieira wrote:
On quarta-feira, 23 de maio de 2012 14.16.12, Alberto Mardegan wrote:
> On 05/23/2012 01:25 PM, Rene Jensen wrote:
> > Question:
On quarta-feira, 23 de maio de 2012 14.16.12, Alberto Mardegan wrote:
> On 05/23/2012 01:25 PM, Rene Jensen wrote:
> > Question: How can we expose objects governed by QSharedPointer to QML
> > safely? I can guarantee the lifecycle beyond the life of my
> > QDeclarativeEngine.
>
> As neither of us k
Hi Rene,
I don't have real answers for your questions, but just a piece of
advice: KISS.
On 05/23/2012 01:25 PM, Rene Jensen wrote:
> Question: How can we expose objects governed by QSharedPointer to QML
> safely? I *can* guarantee the lifecycle beyond the life of my
> QDeclarativeEngine.
As ne
Hello qtpies.
Disclaimer 1: I have read incessantly in the Quick documents, searched
the net and also extensively used QML. Please don't LMGTFY or RTFM me
instinctively ;-)
Disclaimer 2: I started a topic at QtCentre
(http://www.qtcentre.org/threads/49059-QSharedPointer-QWeakPointer-in-QML),
hopin
Hi,
Den 23. mai 2012 09:02, skrev ext Simon Hausmann:
> Hi,
>
> I would like to nominate Peter for approver status.
>
> As part of the team in the University of Szeged he has completed the past few
> rebases of V8 in the qtjsbackend module, a task that is anything but easy,
> with a fast moving up
On quarta-feira, 23 de maio de 2012 04.54.11, bradley.hug...@nokia.com wrote:
> On May 22, 2012, at 11:01 AM, ext Thiago Macieira wrote:
> > And I don't think they very much liked the idea of spinning while trying
> > to
> > acquire a lock (consumes power)... at least we have a call to
> > QThread:
On Wednesday 23. May 2012 09.02.00 ext Simon Hausmann wrote:
> Hi,
>
> I would like to nominate Peter for approver status.
>
> As part of the team in the University of Szeged he has completed the past
> few rebases of V8 in the qtjsbackend module, a task that is anything but
> easy, with a fast m
Hi,
I would like to nominate Peter for approver status.
As part of the team in the University of Szeged he has completed the past few
rebases of V8 in the qtjsbackend module, a task that is anything but easy,
with a fast moving upstream and a very complex patch set on our side.
Based on his co
30 matches
Mail list logo
