Donald you obviously need to implement a new backend to git that lives along
side ssh, so that all development on this can be done against sources that live
on an imap server….
On 04/05/2012, at 7:41 AM, ext Donald Carr wrote:
Hey kb,
This is pretty cool, are you making any attempt at upstream
Interesting
Sent from my BlackBerry® PlayBook™
www.blackberry.com
--
*From:* "k blammo"
*To:* "development@qt-project.org"
*Sent:* May 4, 2012 2:25 AM
*Subject:* [Development] Crosscompile on Debian stable targeting MS Windows
L.s.
For those of you that want to bui
On quinta-feira, 3 de maio de 2012 22.54.38, Olivier Goffart wrote:
> On Thursday 03 May 2012 12:30:21 Thiago Macieira wrote:
> > In any case, the documentation is what's valid. If the code and the
> > documentation differ, usually the documentation prevails and the code
> > needs
> > to be changed
Hey kb,
This is pretty cool, are you making any attempt at upstreaming these
or will these continue to exist as email attachments?
Yours sincerely,
Donald
On Thu, May 3, 2012 at 11:25 AM, k blammo wrote:
> L.s.
>
> For those of you that want to build Microsoft Windows binaries on
> Debian stabl
On Thu, 3 May 2012, Thiago Macieira wrote:
>> My suggestion is to replace them by callbacks and keep the setters in a
>> private header. Someone is against this idea?
>
> Not at all.
>
> I suggested that the Squish and Gamma Ray developers get together and put
> together a proper callback implemen
On Thursday 03 May 2012 12:30:21 Thiago Macieira wrote:
> In any case, the documentation is what's valid. If the code and the
> documentation differ, usually the documentation prevails and the code needs
> to be changed.
I think this is an overstatement.
If there is conflict between the documentat
On Thursday 03 May 2012 20:50:44 Christoph Schleifenbaum wrote:
> 3 maj 2012 kl. 12:30 skrev Christoph Schleifenbaum:
> > 3 maj 2012 kl. 11:47 skrev Sean Harmer:
> >> On Tuesday 01 May 2012 23:21:50 John Layt wrote:
> >>
> >>
> >>> I've been testing the Mac printing and unfortunately hit a couple
3 maj 2012 kl. 12:30 skrev Christoph Schleifenbaum:
>
> 3 maj 2012 kl. 11:47 skrev Sean Harmer:
>
>> On Tuesday 01 May 2012 23:21:50 John Layt wrote:
>>
>>> I've been testing the Mac printing and unfortunately hit a couple of release
>>> blockers that it would be great if a Mac person could ha
L.s.
For those of you that want to build Microsoft Windows binaries on
Debian stable: Here are some patches that enable cross-compiling of Qt
5 (both libraries and examples) using mingw that comes bundled with
Debian 6 (current stable).
The resulting binaries can be tested with wine on Debian 6.
On 03/05/12 12:30, Thiago Macieira wrote:
> There's also another option, which is to have a "Qt developers documentation",
> probably matching the next unreleased version of Qt. That way, we, the
> developers, can easily locate the source code when proof-reading our
> documentation and verify that
On Thursday, May 03, 2012 15:07:47 Thiago Macieira wrote:
> On quinta-feira, 3 de maio de 2012 14.53.44, Adriano Rezende wrote:
> > Hi,
> >
> > Currently we have these 2 functions in qobject.cpp:
> >
> > extern "C" Q_CORE_EXPORT void qt_addObject(QObject *)
> > {}
> >
> > extern "C" Q_CORE_EXPOR
On quinta-feira, 3 de maio de 2012 14.53.44, Adriano Rezende wrote:
> Hi,
>
> Currently we have these 2 functions in qobject.cpp:
>
> extern "C" Q_CORE_EXPORT void qt_addObject(QObject *)
> {}
>
> extern "C" Q_CORE_EXPORT void qt_removeObject(QObject *)
> {}
>
>
> The qt_addObject is being called i
On 5/3/12 12:30 PM, "ext Thiago Macieira"
wrote:
>>
>>This is something that integrates well with the open governance concept
>>too, as I think that there's still a considerable gap between users and
>>contributors of Qt. Maybe this is something to consider in order to
>>narrow it a little more
Hi,
Currently we have these 2 functions in qobject.cpp:
extern "C" Q_CORE_EXPORT void qt_addObject(QObject *)
{}
extern "C" Q_CORE_EXPORT void qt_removeObject(QObject *)
{}
The qt_addObject is being called in the QObject constructor and
qt_removeObject in the destructor.
It seems that they ar
On quinta-feira, 3 de maio de 2012 13.30.12, Richard Moore wrote:
> One thing we've been doing in the network subsystem is adding
> information to the wiki pages about how things fit together. Olivier
> has done the same thing for QStringBuilder and QMutex too. I think
> having more information lik
Hello!
Today, we finished copying all the wiki pages to their new location.
Attached is a text file that matches URLs of the pages on
wiki.qt-project.org to the pages on qt-project.org/wiki.
If you have pages that have been moved, please take a look and see if it
all worked out the way it should.
On 3 May 2012 11:30, Thiago Macieira wrote:
> On quinta-feira, 3 de maio de 2012 12.18.47, Pierre Vorhagen wrote:
>> This is something that integrates well with the open governance concept
>> too, as I think that there's still a considerable gap between users and
>> contributors of Qt. Maybe this
On quarta-feira, 2 de maio de 2012 09.00.37, lars.kn...@nokia.com wrote:
> In total I am more leaning towards reverting it, but would also be ok to
> add Oliviers patch. Let's hear some other opinions.
No one has expressed any kind of fondness to the current change, so it looks
like we need to tak
On quinta-feira, 3 de maio de 2012 12.18.47, Pierre Vorhagen wrote:
> I regularly find myself browsing and grep'ing through the source tree to
> find the implementation of a given class, referenced in the Qt
> Documentation. Of course, as a newbie to Qt internals, I don't yet
> intuitively know whe
3 maj 2012 kl. 11:47 skrev Sean Harmer:
> On Tuesday 01 May 2012 23:21:50 John Layt wrote:
>
>> I've been testing the Mac printing and unfortunately hit a couple of release
>> blockers that it would be great if a Mac person could have a look at
>> sometime and give an opinion:
>>
>> https://bug
Hi,
I regularly find myself browsing and grep'ing through the source tree to
find the implementation of a given class, referenced in the Qt
Documentation. Of course, as a newbie to Qt internals, I don't yet
intuitively know where all the classes are located.
I find that the insight into the im
On Tuesday 01 May 2012 23:21:50 John Layt wrote:
> I've been testing the Mac printing and unfortunately hit a couple of release
> blockers that it would be great if a Mac person could have a look at
> sometime and give an opinion:
>
> https://bugreports.qt-project.org/browse/QTBUG-2
Christop
22 matches
Mail list logo
