On Tuesday 20 September 2011 16:33:37 Wolf-Michael Bolle wrote:
On Thursday 15 September 2011 19:12:56 ext David Faure wrote:
Well, apart from the too many details about the spec the API in
qmime.git is mostly good, I like QMimeDatabase.
But the code is mostly about parsing XML files...
Hello,
I'm curios if for qt5 would it be possible to implement some sort of desktop
components like the ones available now for qml but mimic
the metro look of windows 8 for usage on windows(and if possible maybe on
also desktop platforms).
Thanks,
Radu
--
My programs never have bugs, they just
Hello Radu,
On Wed, Sep 21, 2011 at 5:03 AM, Radu - Ionut Kurta
kurta.r...@gmail.com wrote:
I'm curios if for qt5 would it be possible to implement some sort of desktop
components like the ones available now for qml but mimic
the metro look of windows 8 for usage on windows(and if possible
I agree and I and probably other people will be glad in helping out
developing these widgets, now where do we find a designer ? :)
On Wed, Sep 21, 2011 at 11:31 AM, Artur Souza (MoRpHeUz)
artur.so...@openbossa.org wrote:
Hello Radu,
On Wed, Sep 21, 2011 at 5:03 AM, Radu - Ionut Kurta
On Wed, Sep 21, 2011 at 5:50 AM, Radu - Ionut Kurta
kurta.r...@gmail.com wrote:
I agree and I and probably other people will be glad in helping out
developing these widgets, now where do we find a designer ? :)
Give me a few weeks and I'll probably be able to get the help from a
professional
Why should individual platforms handle adding mime types, if there are only 3
ways to add them - from xml (1 or many), from text files, from binary database?
21.09.2011, в 10:27, David Faure написал(а):
On Tuesday 20 September 2011 16:33:37 Wolf-Michael Bolle wrote:
On Thursday 15 September
Everyone who has tried to use QML has said it's much beyond any other
technology in terms of ease of development. I have friends making
applications professionally and that's what they tell me.
I don't know if I'm alone, but without fully supported QML-Desktop
elements I assume I will
Hi David,
On Wednesday 21 September 2011 08:27:52 ext David Faure wrote:
Well, apart from the too many details about the spec the API in
qmime.git is mostly good, I like QMimeDatabase.
But the code is mostly about parsing XML files...
Well, anyway. I'll let you and
Sean wrote:
If I understood things correctly at QtCS in Henry's talks then a QtAddon
module does not necessarily have to support every platform that Qt
Essentials does.
Right, we can have more add-ons like ActiveQt or Qt Compositor that are
specific to certain environments.
On the other
Besides having that, what I would really like is that we have a
component set (at some point in the future I would like to be able
to start calling them widgets again, as this is what they are) that
is the same on all platforms.
I also secretly call them widgets out of habit. However the
Hi everyone,
Just wanted to wrap up the naming discussions on this list. I've now documented
the conclusions on this page:
http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/Qt5ProductDefinition
The page explains the naming guidelines for header files, QML import
statements,
On Wednesday, 21 de September de 2011 11.52.03, Peter Kuemmel wrote:
I still see a problem in making signals public, this
completely breaks encapsulation, and makes it possible
for everyone to emit any signal.
There's no way around it. Since we're using the function pointer (actually,
the
I explored native mime database in Windows. It is stored in registry and
contains data for most common extensions. It is a map from *.extension to
mime type name. This mime type name is equal to freedesktop.org, however for
most of types it is not set. So, if we will try to generate database
On Wednesday, 21 de September de 2011 12.25.42, Peter Kuemmel wrote:
Everyone who has tried to use QML has said it's much beyond any other
technology in terms of ease of development. I have friends making
applications professionally and that's what they tell me.
I don't know if I'm alone,
On Wednesday, 21 de September de 2011 14.18.49, Wolf-Michael Bolle wrote:
I don't like the idea of imposing a database seperate from the one the
individual platform already has. Also, I don't believe that on mobile
platforms such as Symbian it is such a good idea to use up valueable flash
On Wed, Sep 21, 2011 at 4:22 PM, Thiago Macieira thi...@kde.org wrote:
On Wednesday, 21 de September de 2011 14.18.49, Wolf-Michael Bolle wrote:
I don't like the idea of imposing a database seperate from the one the
individual platform already has. Also, I don't believe that on mobile
On Wednesday, 21 de September de 2011 15.12.21, Thiago Macieira wrote:
There's no way around it. Since we're using the function pointer (actually,
the PMF) to identify the signal, you must have C++ access to the signal
function. That means you must be able to call it.
Other template-based
On Wed, 21 Sep 2011 15:21:32 +0200, Thiago Macieira wrote:
I understand that sentiment. What I was saying is that I want to bring
that ease of making applications to the desktop too. Not because I think
mobile UIs are better (or worse, they are just different), but because
I've seen how
On Wednesday, 21 de September de 2011, às 16.30.13, you wrote:
While Symbian is not a target anymore, there are plenty of embedded
platforms
with little flash memory available.
Wait... Symbian is off?
Yes.
What about the next billion devices?
I guess they won't run Symbian.
Sorry for
On Wednesday, 21 de September de 2011 13.50.21, Uwe Rathmann wrote:
On Wed, 21 Sep 2011 15:21:32 +0200, Thiago Macieira wrote:
I understand that sentiment. What I was saying is that I want to bring
that ease of making applications to the desktop too. Not because I think
mobile UIs are
On Wednesday, 21 de September de 2011 16.06.13, Peter Kuemmel wrote:
One way around it would be on-the-fly inheriting:
https://qt.gitorious.org/~syntheticpp/qt/qtbase-staging-improvements/commit/
c1cf86f08fca7efbbf03106756d4c5bbd991664c
Maybe this commit could be the starting point for a
- Original Message -
From: Artur Souza (MoRpHeUz) artur.so...@openbossa.org
To: jens.bache-w...@nokia.com
Cc: qt5-feedback@qt.nokia.com
Sent: Wednesday, September 21, 2011 9:05 AM
Subject: Re: [Qt5-feedback] Windows UI
On Wed, Sep 21, 2011 at 9:56 AM, jens.bache-w...@nokia.com
On Wednesday 21 September 2011 15:19:59 ext Иван Комиссаров wrote:
I explored native mime database in Windows. It is stored in registry and
contains data for most common extensions. It is a map from *.extension
to mime type name. This mime type name is equal to freedesktop.org,
however for
On Wed, Sep 21, 2011 at 12:03 PM, BRM bm_witn...@yahoo.com wrote:
One of the biggest attractions to using Qt is the fact that it integrates
natively. So I would say that #2 needs to as well.
I honestly don't get the whole Java-like mindset that the application needs
to look the same on all
Don't mix things. No one said desktop support is Done. The QWidget
infrastructure is Done.
This is what I have meant with: 'Done' (QWidget)
Qt5 should come with fully Nokia-supported QML Desktop Components.
This would also help the acceptance of QML, because it is technically
the
Thiago Macieira wrote:
On Wednesday, 21 de September de 2011 15.12.21, Thiago Macieira wrote:
There's no way around it. Since we're using the function pointer
(actually, the PMF) to identify the signal, you must have C++ access to
the signal function. That means you must be able to call it.
Op 21-9-2011 17:57, Peter Kuemmel schreef:
...
I don't like it either.
I know, both solutions aren't very elegant, but I hope
someone gets inspired and finds a better solution.
And I still prefer to have things checked by the compiler
and not to trust developers (I promise I never emitted
Stephen Kelly wrote:
Thiago Macieira wrote:
On Wednesday, 21 de September de 2011 15.12.21, Thiago Macieira wrote:
There's no way around it. Since we're using the function pointer
(actually, the PMF) to identify the signal, you must have C++ access to
the signal function. That means you
Op 21-9-2011 19:09, Thiago Macieira schreef:
On Wednesday, 21 de September de 2011 18:47:38 Andre Somers wrote:
Is it really nessecairy that _everyone_ has public access to the signal?
What if only QObject had access to it? Would that work? If so, it could
work to just make QObject a friend
On Wed, Sep 21, 2011 at 1:15 PM, Adriano Rezende
adriano.reze...@openbossa.org wrote:
On Wed, Sep 21, 2011 at 9:56 AM, jens.bache-w...@nokia.com wrote:
1 - platform specific qml widgets (I don't care if technically the
desktop widgets share the same implementation and use the QStyle API
I've been following this discussion since the beginning, but only briefly
participated on devnet. It took a while for me to get my exact thoughts
about this lined up, and a lot has already been discussed, but here goes.
On Wed, 21 Sep 2011 19:20:06 +0200, Thiago Macieira thi...@kde.org
On Wednesday, 21 de September de 2011 23:19:43 Frans Klaver wrote:
To be honest I never really understood why one would insist on
compile-time checking of something that was obviously intended to be used
and checked at run-time.
It was never intended to be done only at runtime. It was done
Sorry, slight typo in my original email. Creating an observer would be done
like this:
addObserver(sender, SomeSignalEvent::eventID(), receiver,
ReceivingClass::handleSomeSignalEvent);
Also, the SomeSignalEvent class should have had an accessor function to allow
the receiver to get the
33 matches
Mail list logo
