Hi Lars,
We've previously recommended that add-on modules should wrap their public
interface in C++ namespaces like QtBluetooth, QtOrganizer, QtJsonDb and so
on.
Should there be some guidance for the namespace macros? Especially the
macros for using the namespace, which are used in application c
On Fri, 09 Dec 2011 02:58:10 +0100, wrote:
> Exactly! And that's why I wanted to use the status for something useful
> for contributors, so they can quickly see who is what, and where to seek
> for help depending on what they need. Of course, each maintainer will
> have his/her own area of expert
On 08/12/2011 16:50, ext Thiago Macieira wrote:
> On Thursday, 8 de December de 2011 22.25.03,
> marius.storm-ol...@nokia.com wrote:
>> Anyways, my suggestion was just an idea on how to make the
>> voice/op feature _useful_.
>>
>> It's not like we actively use voice/op for anything on our channel
>
On 12/08/2011 02:14 PM, Storm-Olsen Marius (Nokia-MP-Qt/Austin) wrote:
> Are you sure you want another mailing list for something which simply
> just another platform?
... and the coordination of at least 400 owners of a Raspberry Pi with
Qt 5. See what is growing at
https://wiki.qt-project.org/
On Thursday, 8 de December de 2011 22.25.03, marius.storm-ol...@nokia.com
wrote:
> > Approvers are already given voice status and they have the right to op
> > themselves in case of trouble. There's no distinction made to maintainers.
> >
> > The channel admins are given admin rights, to be able to
On Thursday, December 08, 2011 22:14:16 marius.storm-ol...@nokia.com wrote:
> On 08/12/2011 13:50, ext Quim Gil wrote:
> > Hi, the Qt on Raspberry Pi project has now an own mailing list:
> > http://lists.qt-project.org/mailman/listinfo/qtonpi
> >
> > Anybody interested, please join.
> >
> > PS: t
On 08/12/2011 13:27, ext Thiago Macieira wrote:
> On Thursday, 8 de December de 2011 17.04.09, marius.storm-ol...@nokia.com
> wrote:
>> So, I propose that
>> Chief Maintainer + Maintainers +
>> Infra. tools Admins get Op status (@ prefix)
>> Approvers get Voice status (+ prefix)
>
2011/12/8 Thiago Macieira :
> On Thursday, 8 de December de 2011 20.48.33, Richard Moore wrote:
>> 2011/12/8 Thiago Macieira :
>> > Approvers are already given voice status and they have the right to op
>> > themselves in case of trouble. There's no distinction made to maintainers.
>>
>> Actually t
On 08/12/2011 13:50, ext Quim Gil wrote:
> Hi, the Qt on Raspberry Pi project has now an own mailing list:
> http://lists.qt-project.org/mailman/listinfo/qtonpi
>
> Anybody interested, please join.
>
> PS: this is also a precedent for other initiatives beyond the official
> Qt releases. As discusse
On 12/8/2011 2:50 PM, Quim Gil wrote:
> Hi, the Qt on Raspberry Pi project has now an own mailing list:
> http://lists.qt-project.org/mailman/listinfo/qtonpi
>
> Anybody interested, please join.
>
> PS: this is also a precedent for other initiatives beyond the official
> Qt releases. As discuss
On Thursday, 8 de December de 2011 20.48.33, Richard Moore wrote:
> 2011/12/8 Thiago Macieira :
> > Approvers are already given voice status and they have the right to op
> > themselves in case of trouble. There's no distinction made to maintainers.
>
> Actually they aren't.
Yes, they are, except
2011/12/8 Thiago Macieira :
> Approvers are already given voice status and they have the right to op
> themselves in case of trouble. There's no distinction made to maintainers.
Actually they aren't.
Rich.
___
Development mailing list
Development@qt-pro
Hi, the Qt on Raspberry Pi project has now an own mailing list:
http://lists.qt-project.org/mailman/listinfo/qtonpi
Anybody interested, please join.
PS: this is also a precedent for other initiatives beyond the official
Qt releases. As discussed in the Qt Contributors Day there is no process
f
On Thursday, 8 de December de 2011 17.04.09, marius.storm-ol...@nokia.com
wrote:
> So, I propose that
> Chief Maintainer + Maintainers +
> Infra. tools Admins get Op status (@ prefix)
> Approvers get Voice status (+ prefix)
>
> Or maybe there's other suggestions?
Approvers are alrea
On 12/8/11 6:04 PM, "ext marius.storm-ol...@nokia.com"
wrote:
>Hi,
>
>Until now, voiced users on #qt-labs have indicated Nokia personnel,
>which was useful in the "old days" when only Nokians could merge patches
>into the codebase.
>
>However, those days have passed, and I think it would be usefu
On 8 December 2011 17:04, wrote:
> However, those days have passed, and I think it would be useful to
> re-purpose the op/voice to signify Maintainers, Approvers etc, to help
> contributors know who is what.
>
> So, I propose that
> Chief Maintainer + Maintainers +
> Infra. tools Admins g
On Thursday, 8 de December de 2011 12.02.42, João Abecasis wrote:
> It should be fairly simple to add an inline templated connect function that
> takes a pointer-like type, unwraps the actual pointer and calls the "real"
> connect. (e.g., using something like boost::get_pointer and hooking our
> po
On 08/12/2011 11:04, you wrote:
> So, I propose that
> Chief Maintainer + Maintainers +
> Infra. tools Admins get Op status (@ prefix)
> Approvers get Voice status (+ prefix)
(Unfortunately, Freenode doesn't support half-op, so we only have two
levels of indicators to play with.
Hi,
Until now, voiced users on #qt-labs have indicated Nokia personnel,
which was useful in the "old days" when only Nokians could merge patches
into the codebase.
However, those days have passed, and I think it would be useful to
re-purpose the op/voice to signify Maintainers, Approvers etc,
> Disk cache:
> * Get implementation from somewhere which is good enough for most
> applications
> * Set caching on by default: no
Hi,
Although the discussion seems to have moved on to an inter-process safe disk
cache, there is a thread safe wrapper for QNetworkDiskCache attached to
https://bug
On Thu, Dec 08, 2011 at 10:18:50AM +0100, ext
dietrich.gos...@continental-corporation.com wrote:
> Sorry, the I got the wrong subject ..
>
just don't do http://wikibin.org/articles/thread-hijacking.html in the
first place.
___
Development mailing list
De
On 12/08/2011 07:01 AM, Atlant Schmidt wrote:
> One use case Stephen didn’t mention is the case where you decide
> to make some sort of global change to the project. (I don’t know if it’s
> true of the Alassian wiki, but) In a pure WYSIWIG system, you’ll get to
> make that change individual
On Thursday 08 December 2011 13:01:43 ext Atlant Schmidt wrote:
> [...] to echo and amplify what Stephen has said:
>
> WYSIWYG editors may be easier for novice wikipedians to use, but
> markup-based editors are far easier for experienced people to use
> and get the results precisely corre
Folks:
I've avoided entering this topic because, as a Wikipedia administrator,
I might be perceived as being biased in favor of Wikimedia, but I want
to echo and amplify what Stephen has said:
WYSIWYG editors may be easier for novice wikipedians to use, but
markup-based editors are far
On 7. des. 2011, at 17.22, ext Thiago Macieira wrote:
> On Wednesday, 7 de December de 2011 09.12.39, Olivier Goffart wrote:
>>> * QObject::connect needs to be able to take a QSharedPointer
>>> * QObject::connect needs to be able to take a QWeakPointer
>>
>> I don't understand this point: you can
Hi,
On 11/30/2011 06:47 AM, ext Rohan McGovern wrote:
> Hello,
>
> In Qt5, we no longer appear to have any mkspecs for cross-compiling for
> ARM or MIPS. They were tied up with qws, so they were removed when
> qws was removed.
>
> Is it intentional that we still don't have any, or has it just fal
Hi,
On 12/08/2011 10:12 AM, ext dietrich.gos...@continental-corporation.com
wrote:
Hi,
I have managed it to enable OpenGL ES 2.x and XLib during the Qt5
compilation.
Now I am recieving this error message:
xcb auto-detection... ()
/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/
Sorry, the I got the wrong subject .. Building Qt5 for embedded Linux ARM
is the correct one.
Von:dietrich.gos...@continental-corporation.com
An: thiago.macie...@intel.com
Kopie: development@qt-project.org
Datum: 08.12.2011 10:12
Betreff:[Development] Antwort: Re: Public Qt5
Hi,
I have managed it to enable OpenGL ES 2.x and XLib during the Qt5
compilation.
Now I am recieving this error message:
xcb auto-detection... ()
/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi/bin/arm-none-linux-gnueabi-g++
-c -pipe -g -Wall -W -I../../../
29 matches
Mail list logo
