Hi Davet.
1. QAbstractSocket is etalon, example to follow for class SerialPort.
ie most likely this:
- SerialPort is inspired by QAbstractSocket / follows the API-conventions
defined by QAbstractSocket?
2. QPrinterInfo is etalon, example to follow for class SerialPortInfo.
Ie general
Hi.
Yes, something like this.
Best regards,
Denis
13.03.2012, 00:47, 1+1=2 dbzhang...@gmail.com:
On Mon, Mar 12, 2012 at 12:22 PM, Davet Jacques davetjacq...@yahoo.fr wrote:
Hi,
I went over it and fixed most of
the text to make it grammatically correct and nicer to read, but I don't
We can talk about making it into a nicer API in a future version of Qt, but
for Qt 5, we should keep it as it is.
Understood. I'm not against out-of-qtbase plugins. I am against forcing them
to use private and changing API like QtPlatformSupport.
Ah, now I see. This is where the
Hi All,
Although late for 4.8.1 this is a good discussion to have.
I think the key question that needs to be answered is: Do we aim to have a
model where it is typically ok to take always the latest that exists in
the repository?
If the answer is yes, agreeing not to branch will support the
On Tue, Mar 13, 2012 at 07:16:35AM +, ext Turunen Tuukka wrote:
Certainly for the minor releases we need to have a branch in order not to
hurt development of new things while getting into release maturity. But
for patch releases it should be feasible to keep release maturity at any
time.
On terça-feira, 13 de março de 2012 09.22.21, tang ke wrote:
hi all:
I want to build the qt5 with cross-toolchain, the target arch is mips,
the qt5 build support it?
When I last checked the build with Yocto's MIPS toolchain, it worked.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Den 12. mars 2012 23:45, skrev ext Rohan McGovern:
Richard Moore said:
On 12 March 2012 17:56,kent.han...@nokia.com wrote:
Besides flaky tests, we also have the general/recurring problem of changes
going into qtbase that break qtdeclarative (and possibly/likely other
modules). While I
Hi,
Our hosting provider need to do a quick update on some of our servers related
to qt-project.org. The
affected services are:
* Gerrit / Code Review - http://codereview.qt-project.org/
* Mailing lists - http://lists.qt-project.org/
* Wiki - http://wiki.qt-project.org/
The services will
On 13 March 2012 13:27, Matias Rand matias.r...@nokia.com wrote:
Hi,
Our hosting provider need to do a quick update on some of our servers related
to qt-project.org. The
affected services are:
* Gerrit / Code Review - http://codereview.qt-project.org/
* Mailing lists -
On 03/13/2012 02:32 PM, ext Giuseppe D'Angelo wrote:
On 13 March 2012 13:27, Matias Randmatias.r...@nokia.com wrote:
Hi,
Our hosting provider need to do a quick update on some of our servers
related to qt-project.org. The
affected services are:
* Gerrit / Code Review -
Den 13. mars 2012 12:08, skrev ext Kent Hansen:
It's difficult to know which type of changes can break stuff in other
modules, but things like
- QtCore/Gui event/timer handling
- Gui text/font changes
- Network changes (declarative uses networking extensively)
- Changing the semantics of
Hi,
Some updates on this. After yesterday's discussion it was decided to
keep QRegExp in QtCore as a deprecated class. At the same time all
QRegExp-related classes or overloads get deprecated as well (although
probably not disabled with QT_DEPRECATED_SINCE because very few of
them are actually
Hi all,
I just put the patch in that removes qdoc3 from qtdoc. From then onwards there
will only be qdoc in qtbase.
It is in Gerrit as http://codereview.qt-project.org/#change,19829
That is one of the changes I think we need for the alpha (to not ship both
qdoc3 and qdoc)
Another thing we
(Sorry for top-posting from this web client)
Thank you for the list of modules. Can I do the following changes to the wiki?
1. Move the list of modules at
http://qt-project.org/wiki/Qt_5.0#66036ddf6d03c9ce1fc742741417f128 to two new
pages:
- Qt Essential Modules
- Qt Add-on Modules
Hi all.
I can not run GUI application built in Release mode.
In the console displays the error:
No platform plugin argument was specified and the default plugin
windows is not available
What could it be?
PS:
Qt5 (qtbase) built in Win7 x32 with Windows SDK 7.1:
set
Hi, here you have the list of essential add-on modules going to the Qt 5
alpha release:
http://qt-project.org/wiki/Qt-5-Alpha
I have tried to find information about these modules in the wiki and the Qt 5
snapshot docs, with mixed results:
- Many modules don't seem to have docs available, at
Hi,
Please read
http://qt-project.org/wiki/Spelling_Module_Names_in_Qt_Documentation.
That should contain module names for most modules and gives hints on what to
use (I am aware that these guidelines are not followed everywhere)
So if you have the source and see incorrect use of module names
On 03/13/2012 07:04 AM, Vandonderen Casper (Nokia-MP/Oslo) wrote:
The solution given above would mean that it will become optional to
document NOTIFY signals. But is that not completely different from
the original problem?
Yes.
The original question was how to make qdoc not see Q_PROPERTY
On 03/12/2012 11:56 PM, ext Thiago Macieira wrote:
qmake does not add a dependency on the .a file, so the other target doesn't
get
relinked.
Qtopia had a large number of .a files and this hit us hard so we devised
a workaround.
# A function to create explicit dependencies in a Makefile
19 matches
Mail list logo
