Hi,
the status of the module is that we are trying to keep it compiling,
such that it does not totally fall apart.
Apart from the meta object issues, it needs another major refactoring
due to the Lighthouse architecture (it previously used widgets with
native handles).
We (at Nokia) do not have
On Wed, Feb 1, 2012 at 4:53 PM, David Faure wrote:
> However I would like this to be called qDebug(AREA) rather than qLog(AREA).
> Otherwise we are presenting a confusing situation of two competing debug-
> output frameworks inside Qt.
Agreed. Extra functionality can be built on top of what is th
> From: David Faure
> On Wednesday 01 February 2012 10:02:00 BRM wrote:
>> I would also suggest that the plugins use a standard public interface class
>> such as QAbstractLogFacility, like QTcpSocket uses QAbstractSocket - so
>> that people can add their own custom logging output easily
>
> T
On Wednesday 01 February 2012 10:02:00 BRM wrote:
> I would also suggest that the plugins use a standard public interface class
> such as QAbstractLogFacility, like QTcpSocket uses QAbstractSocket - so
> that people can add their own custom logging output easily
This is already available, see qIns
On Wednesday, 1 de February de 2012 17.57.57, lars.kn...@nokia.com wrote:
> I'm also in favor of keeping the 4.7 behavior if it causes quite some apps
> to break. It's not really important enough to break this in the last minor
> release we do in 4.x.
>
> Let's get this sorted and fully fixed in 5.
Getting caught up again...
- Original Message -
> From: Lincoln Ramsay
> On 01/31/2012 05:08 PM, ext Jordi Pujol wrote:
>> - Crazy idea : allow logging to a socket ? ( remote log/debug )
>> - More than one logging file ? One file for every category / group of
>> categories
>> - Log
I'm also in favor of keeping the 4.7 behavior if it causes quite some apps
to break. It's not really important enough to break this in the last minor
release we do in 4.x.
Let's get this sorted and fully fixed in 5.0
Cheers,
Lars
On 1/31/12 1:24 PM, "ext Thiago Macieira"
wrote:
>On Tuesday, 31
Guess I should give my $0.02 as well ;-)
I'm perfectly fine with dropping -no-stl. As already explained in this
thread, we need STL (or a subset of it) anyways on embedded systems (due
to V8 and WebKit). On desktop systems -no-stl doesn't make any sense
anyway.
Now the main point is about decent
Sorry, I'm a little late to the conversation - got behind a bit...
> From: Thiago Macieira
>On Monday, 30 de January de 2012 16.32.38, Olivier Goffart wrote:
>> On Monday 30 January 2012 16:13:48 Thiago Macieira wrote:
>> > We definitely want:
>> > - the language support library (chapter 18)
>>
On Wednesday 01 February 2012 11:20:17 Lincoln Ramsay wrote:
> In summary:
> 1) Generated default logging config file (for sanity).
I agree (please use
QStandardPaths::writableLocation(QStandardPaths::ConfigLocation)
as the base directory for it)
> 2) QLog::setDefaultConfigFile for application
On Wednesday 1. February 2012 12.48.07 ext Robin Burchell wrote:
> 2012/2/1 Jedrzej Nowacki :
> > Yes, and by updating QMetaObjectBuilder we will update data generated by
> > ActiveQt. ActiveQt would use the newest meta object version (faster &&
> > tested).
>
> As (I think) was raised on Gerrit -
Den 01. feb. 2012 12:48, skrev ext Robin Burchell:
> 2012/2/1 Jedrzej Nowacki:
>> Yes, and by updating QMetaObjectBuilder we will update data generated by
>> ActiveQt. ActiveQt would use the newest meta object version (faster&&
>> tested).
> As (I think) was raised on Gerrit - this requires that so
2012/2/1 Jedrzej Nowacki :
> Yes, and by updating QMetaObjectBuilder we will update data generated by
> ActiveQt. ActiveQt would use the newest meta object version (faster &&
> tested).
As (I think) was raised on Gerrit - this requires that someone take
the time to make it use QMetaObjectBuilder..
On Wednesday 1. February 2012 10.36.35 ext Kent Hansen wrote:
> Den 01. feb. 2012 09:47, skrev ext Olivier Goffart:
> > Facts:
> > 1) QMetaObjectBuilder is private, its API may still change from minor
> > version to minor version
>
> That's fine. It's still better (lower maintenance) than having
>
Ich bin vom 27.01. - 12.02. 2012 im Urlaub.
Die Mails werden weder gelesen noch weitergeleitet.
Bitte senden Sie die Mails an matthias.deusc...@amk-antriebe.de, so werden sie
auch waehrend meiner Abwesenheit bearbeitet und beantwortet.
Mit freundlichen Gruessen
i. A. Michael Klank
Abt. VT-APL
_
We are happy to announce a 2.4.1 patch release of Qt Creator.
It is a pure bugfix release, please have a look at the blog post
http://labs.qt.nokia.com/2012/02/01/qt-creator-2-4-1-released/
The Qt SDK also has received an update that includes the new Qt Creator, and
you can download the standalo
On 1 February 2012 06:37, Kent Hansen wrote:
> The .ico plugin was originally a Qt Solution, but in Qt 4.4 it was made
> part of Qt because QtWebKit needed it.
>
> Does QtWebKit still need it? Does anyone else need it?
> In any case, would it be OK to move it to the new qtimageformats module
> (wh
Den 01. feb. 2012 09:47, skrev ext Olivier Goffart:
> Facts:
> 1) QMetaObjectBuilder is private, its API may still change from minor version
> to minor version
That's fine. It's still better (lower maintenance) than having
home-grown / incompatible generators floating around, IMO.
> 2) Qt mainta
Hi,
It would be useful to have a QByteArrayRef class, similar to QStringRef
-- a thin wrapper that doesn't copy the data.
Did anyone implement it already? If not, I can take a stab at it.
Kent
___
Development mailing list
Development@qt-project.org
htt
On Wednesday 01 February 2012 07:11:20 Kent Hansen wrote:
> Hi,
> Does anyone care about the ActiveQt module for Qt5?
>
> A problem with this module is that it doesn't have any autotests. I can
> run some on the examples, but I don't really know what they're supposed
> to do, or how to use them to
20 matches
Mail list logo
