I’m curious why you are not interested in QML.
I’m just finishing up a an initial production release of software oriented
towards high-performance graphics. We used QML for the interface, coffeescript
for view logic, and Qt/c++ for processing and business logic. It works
astonishingly well
Em dom 20 abr 2014, às 22:13:47, Denis Shienkov escreveu:
> == Second issue ==
>
> What about two scenarios ? (e.g. for some abstract I/O device):
>
> 1) Without flush():
>
> MyClass::foo()
> {
> dev.write('a');
> dev.write('b');
> }
>
> MyClass::bar()
> {
> dev.write('c');
> dev.write('d');
>
Em dom 20 abr 2014, às 22:37:11, m...@rpzdesign.com escreveu:
> With Qt 5.3.0 release just around the corner, will Qt Widgets be able to
> run stable on IOS and ANdroid?
They run. They just look horrible.
> Many comments I have seen on this list refers to Qt Widgets as a desktop
> oriented toolki
Michael:
That is a great question.
I hope you get answers that focus on the mobile side of things (IOS/Android)
With Qt 5.3.0 release just around the corner, will Qt Widgets be able to
run stable on IOS and ANdroid?
Many comments I have seen on this list refers to Qt Widgets as a desktop
orie
I feel like Qt is going in the direction of being Qml and Javascript only.I
fear that they may abandon Qt Widgets in the near future,I think they are
heavily promoting Qml.I don't want to use Qml,and before I start using Qt,I
want to be sure that they will not abandon C++ side of Qt and that the
Em dom 20 abr 2014, às 22:32:29, Denis Shienkov escreveu:
> Hi all..
>
> I began to receive indecent e-mails ( the portfolios of prostitutes) in
> the form of "responses" to my questions in the mailing list.
>
> Of course, it is fine, but not in the Qt-development resource.
>
> Can you to take m
Hi all..
I began to receive indecent e-mails ( the portfolios of prostitutes) in
the form of "responses" to my questions in the mailing list.
Of course, it is fine, but not in the Qt-development resource.
Can you to take measures against it? :)
BR,
Denis
___
Thiago,
many thanks for your time and answers.
Forgive for my importunity, but I shall ask also about following:
== Second issue ==
What about two scenarios ? (e.g. for some abstract I/O device):
1) Without flush():
MyClass::foo()
{
dev.write('a');
dev.write('b');
}
MyClass::bar()
{
dev.writ
