On Saturday 11 Feb 2012 13:26:49 you wrote:
> 2) Change format/parse API to support CLDR/ICU formats.
> 1) Keep one consistent API, minimise source compatability break by providing
> deprecated enum methods, but force everyone to switch to new format codes.
I've now pushed a patch to Gerrit impl
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/fancybrowser.pro contains a
TARGET.EPO
Hi all.
I prepared for the first QtSerialPort review.
But then I do not know what to do:
Who will review my changes? Who will do the audit?
Someone, please check the code, because I still have not figured much in the
features by:
http://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
Hi,
Two essential areas need to be addressed. While these could be left for 5.1,
I believe it would be far messier as a result because we would have 2
different API's that are subtly different and would lead to confusion and
inconsistencies.
1) Change the Qt string format codes used to the CL
