Hi,
On 11 February 2012 21:15, Philip Ashmore wrote:
> Hi there.
> Please find attached a patch for qtwebkit-examples-and-demos that allows the
> build to complete on Debian Wheezy amd64.
>
> Please also note that this patch includes a previously submitted patch, not
> yet applied.
>
> Also, exam
Philip Ashmore said:
> Hi there.
> Please find attached a patch for qtwebkit-examples-and-demos that allows
> the build to complete on Debian Wheezy amd64.
>
> Please also note that this patch includes a previously submitted patch,
> not yet applied.
>
> Also, examples/webkit/fancybrowser/fancy
On 02/11/2012 01:44 AM, ext kai.koe...@nokia.com wrote:
> However, adding yet another 'keyword' to the framework has a price,
> especially since the difference between
> 'qDebug(QMessageLogContext("MyCategory"))'<< and a
> 'qLog("MyCategory")<< ' is subtle.
We tried that but while this difference
Well I think I can change the macro name very easy but we can't name it qDebug.
So maybe qDebugCat or somethink like this.
But I think the macro is very necessary special if you develop for devices they
don't have the capacity of a desktop machine.
Cheers,
WB
-Original Message-
Fro
On 10/02/2012, at 5:13 AM,
mailto:marius.storm-ol...@nokia.com>>
mailto:marius.storm-ol...@nokia.com>> wrote:
I think there are a few issues here:
1) Only Dimitri touches Doxygen code, and it doesn't look like
contributions go in (at least not under the authors name). This means
that the funct
On 11/02/2012, at 12:47 AM, André Somers wrote:
My suggestion would be this:
1) If possible, documentation goes right above the relevant code
(implementation or declaration)
2) Prefer the implementation over the declaration when you have to choose
3) If neither is possible, prefer the implementat