Hi all,
As I'm starting to get somewhere with some of my recent hackery, I
thought I'd start discussing it a little more publically.
tl;dr if all goes well and I manage to actually clean up all this code
and get it reviewed, in the future, if you're on linux, hopefully the
core event processing w
Op 9-12-2011 20:18, Stephen Kelly schreef:
On Friday, December 09, 2011 20:12:05 Stephen Kelly wrote:
> This week:
>
Oops, sorry. This was not intended for the Qt mailing list.
I was compiling it for colleages.
Aren't we all, in a way? ;-)
Anyway, thanks. I think it is informative!
André
On Fri, Dec 9, 2011 at 12:49 PM, Marcus D. Hanwell <
marcus.hanw...@kitware.com> wrote:
> 2011/12/9 Stephen Kelly :
> > On Friday, December 09, 2011 20:12:05 Stephen Kelly wrote:
> >
> >> This week:
> >
> > Oops, sorry. This was not intended for the Qt mailing list.
> >
> > I was compiling it for
morten spaketh:
> Those of you that follow the commits on Gerrit closely may have noticed
> the new QPlatformTheme API and wondered what it is. In short, the
> QPlatformTheme API is there to support deeper platform integration,
> indepentently of QPlatformIntegration.
>
> ,
I am *very* interested
2011/12/9 Stephen Kelly :
> On Friday, December 09, 2011 20:12:05 Stephen Kelly wrote:
>
>> This week:
>
> Oops, sorry. This was not intended for the Qt mailing list.
>
> I was compiling it for colleages.
>
I would love to see something like this on the Qt development list,
even if accidentally dis
Hi Henry,
Thank you for your quick reply.
> The instructions were written with brand new projects in mind, but I agree we
> need to consider existing projects that move to Qt Project. The contribution
> agreement needs some special consideration here, so I'll work with Cristy on
> making that
Be that as it may, that is a /very/ useful email right there! :)
2011/12/9 Stephen Kelly :
> On Friday, December 09, 2011 20:12:05 Stephen Kelly wrote:
>
>> This week:
>
>>
>
>
>
> Oops, sorry. This was not intended for the Qt mailing list.
>
>
>
> I was compiling it for colleages.
>
>
>
> Thanks,
On Friday, December 09, 2011 20:12:05 Stephen Kelly wrote:
> This week:
>
Oops, sorry. This was not intended for the Qt mailing list.
I was compiling it for colleages.
Thanks,
--
Stephen Kelly | Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
www.kdab.com || Germany
This week:
== QSound removed ==
== Talk of removing QWorkspace ==
== QTemporaryDir arrives ==
== Building v8 on MIPS ==
== -bsymbolic-functions used by default ==
== Extend the API for touch events ==
== On screen keyboard and better Input Methods ==
== Some build-time tools separate from QtBase
On Wednesday, November 09, 2011 13:54:37 Thiago Macieira wrote:
> On Friday, 28 de October de 2011 12:38:38 lars.kn...@nokia.com wrote:
> > We've been moving this lib quite a bit already. If we move it again, I'd
> > prefer it would end up at it's final location. The move was done before
> > we had
Hi,
>>> Send your request for a new Playground project (including project name
>> and description) to the Qt maintainer from whom you have pre-approval.
>>> CC to sergio.ahumada at nokia.com and Gerrit Expert Group (email address
>> TBD).
>>
>> I think I'd prefer to see this on an infra@ type list
> From: ro...@viroteck.net [mailto:ro...@viroteck.net] On Behalf Of ext
> Just to clarify what I mean here - I don't envisage most of these will require
> much discussion. It just provides the capability for it if it's necessary.
> Just look
> at the approver nominations so far - there's not rea
On Fri, Dec 9, 2011 at 6:16 PM, wrote:
>> Having these on a list also mirrors the structure for approval nomination.
>>
>
> I think it'd be important to keep the barrier very low. It should be possible
> to start competing or crazy projects. So this approval from a Maintainer
> shouldn't usuall
Hi Robin,
> From: ro...@viroteck.net [mailto:ro...@viroteck.net] On Behalf Of ext
> Robin Burchell
> > Agree with a Qt maintainer that s/he will approve your new playground
> > project
>
> Can we agree that this approval should be done on development@? That
> way, the discussion around the sugg
Hi Laszlo,
> If a developer would like to move a project that is started as "QtX", I should
> rename it to "Y" or something like that, and then back again to "X" ?
> Practical
> example: QtOpenaL (coming for instance from a KDE
> repository) -> "3D Audio" (Qt Playground) -> QtOpenAL (Qt Final)
T
On 9. des. 2011, at 17.10, ext Denis Dzyubenko wrote:
> 2011/12/9 João Abecasis :
>> This has my vote:
>>
>>QUuid QUuid::createFromNameV3(const QUuid &, const QByteArray &);
>>QUuid QUuid::createFromNameV5(const QUuid &, const QByteArray &);
>>
>>inline QUuid QUuid::createFromName(con
On 9. des. 2011, at 13.27, João Abecasis wrote:
> Lars wrote:
>> On 12/9/11 12:28 PM, "ext liang...@nokia.com" wrote:
>>>
>>> The original task is:
>>> http://bugreports.qt.nokia.com/browse/QTBUG-23071
>>>
>>> And the change is:
>>> http://codereview.qt-project.org/10803
>>>
>>> For the API na
Den 02. des. 2011 16:27, skrev ext Kent Hansen:
>
> By the way, the suggestion on the table was to abuse fixqt4headers to
> also support updating these "Qt 4.99" includes
> (QtDeclarative/qquickitem.h => QtQuick/qquickitem.h, et al).
Done; if you're using QQuickView and friends, you can now run
On Fri, 9 Dec 2011, Friedemann Kleint wrote:
> I was wondering if the QWorkspace-widget should be removed in Qt 5. It
> has been out of maintenance for a long time.
Still heavily in use in the real world however.
Harri (representing several customer's interest).
_
> Not sure, depends on each project. When the mailing list is the only and
> transparent channel of communication for developing the project itself
> you do generate traffic. Imagine for instance all
> http://mail.kde.org/pipermail/necessitas-devel/ landing in
> development@qt-project.org - not rea
On Friday, December 09, 2011 14:00:13 Laszlo Papp wrote:
> > https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
> >
> > Choose a descriptive playground project name. The name should not
> > include "Qt". For example "Extra Effects", "Mime Types"
> If a developer would like to move a
Hi,
I was wondering if the QWorkspace-widget should be removed in Qt 5. It
has been out of maintenance for a long time.
- http://codereview.qt-project.org/#change,10862 removes the Qt Designer
support
- https://codereview.qt-project.org/#change,10867 (ActiveQt) removes the
last remaining occur
On 12/9/11 1:27 PM, "João Abecasis" wrote:
>
>Lars wrote:
>> On 12/9/11 12:28 PM, "ext liang...@nokia.com"
>>wrote:
>>>
>>> The original task is:
>>> http://bugreports.qt.nokia.com/browse/QTBUG-23071
>>>
>>> And the change is:
>>> http://codereview.qt-project.org/10803
>>>
>>> For the API nam
On Friday, 9 de December de 2011 11.57.21, Thomas Zander wrote:
> hey,
>
> just sending a quick email because I detected a typo in qpainter.cpp which
> misspells an enum value. So copy paste gave me a compile error :)
> It would be much appreciated if someone that actually has push rights
> changes
On Friday, 9 de December de 2011 08.50.41, lars.kn...@nokia.com wrote:
> >Now we have macros like:
> >
> >QTORGANIZER_USE_NAMESPACE
> >QTBLUETOOTH_USE_NAMESPACE
> >Q_USE_JSONDB_NAMESPACE
> >
> >So it's not consistent at the moment, which makes the macros
> >non-guessable. What would be the right th
On 12/9/11 11:20 AM, "Haverinen Henry (Nokia-MP-Qt/Tampere)"
wrote:
>
>On 12/9/11 10:50 AM, "Knoll Lars (Nokia-MP-Qt/Oslo)"
> wrote:
>
>>On 12/9/11 8:42 AM, "Haverinen Henry (Nokia-MP-Qt/Tampere)"
>> wrote:
>
>
>>>Now we have macros like:
>>>
>>>QTORGANIZER_USE_NAMESPACE
>>>QTBLUETOOTH_USE_NAMESP
Lars wrote:
> On 12/9/11 12:28 PM, "ext liang...@nokia.com" wrote:
>>
>> The original task is:
>> http://bugreports.qt.nokia.com/browse/QTBUG-23071
>>
>> And the change is:
>> http://codereview.qt-project.org/10803
>>
>> For the API name, we need a micro API review:
>> Set 1:
>> createUuidMd5(
Hi Henry,
On Fri, Dec 9, 2011 at 10:18 AM, wrote:
> This page introduces the Qt Project playground (a low-barrier area for
> experimenting with new ideas), gives some naming guidelines for modules
> and tools, and documents the module repository structure.
Thanks for getting this started. I hav
Hi Liang,
please send these to development@qt-project.org.
On 12/9/11 12:28 PM, "ext liang...@nokia.com" wrote:
>Hi, all,
>
>The original task is:
>http://bugreports.qt.nokia.com/browse/QTBUG-23071
>
>And the change is:
>http://codereview.qt-project.org/10803
>
>For the API name, we need a micr
Hi Henry,
> https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
> Choose a descriptive playground project name. The name should not include
> "Qt". For example "Extra Effects", "Mime Types"
If a developer would like to move a project that is started as "QtX",
I should rename it to
hey,
just sending a quick email because I detected a typo in qpainter.cpp which
misspells an enum value. So copy paste gave me a compile error :)
It would be much appreciated if someone that actually has push rights changes
this and pushes it upstream, since creating a merge request is kinda ove
On 12/9/11 10:50 AM, "Knoll Lars (Nokia-MP-Qt/Oslo)"
wrote:
>On 12/9/11 8:42 AM, "Haverinen Henry (Nokia-MP-Qt/Tampere)"
> wrote:
>>Now we have macros like:
>>
>>QTORGANIZER_USE_NAMESPACE
>>QTBLUETOOTH_USE_NAMESPACE
>>Q_USE_JSONDB_NAMESPACE
>>
>>So it's not consistent at the moment, which make
Hi all,
So far it has not been clear how you could start working on a new module
or tool in the Qt project. We've now created a wiki page for this
information here:
https://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
This page introduces the Qt Project playground (a low-barrier are
On 12/9/11 8:42 AM, "Haverinen Henry (Nokia-MP-Qt/Tampere)"
wrote:
>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? Es
Hello fellow Trolls,
Those of you that follow the commits on Gerrit closely may have noticed the new
QPlatformTheme API and wondered what it is. In short, the QPlatformTheme API is
there to support deeper platform integration, indepentently of
QPlatformIntegration.
Examples of (current) QPlat
Hi all,
The documentation is currently using various spelling styles for module
names, so I've worked with our technical writers and Kevin (the
documentation maintainer) on this wiki article:
http://developer.qt.nokia.com/wiki/Spelling_Module_Names_in_Qt_Documentatio
n
Comments?
There are a co
36 matches
Mail list logo
