[Interest] Is Nokia officially done with Qt?

[d3fault]

On Fri, Jun 15, 2012 at 6:18 PM, David Boosalis <david.boosalis at gmail.com>wrote:

> A nice name for a fork of Qt would be QTHE (Pronounced Cutie) The HE being
> the first name of original founders of Trolltech - Haarvard and Eirik.
>

I like that name. I like the nod to the creators and keeping the Q prefix
is also be a big win... no (or minimal) changes to existing user code.


> Fork the code, lets throw out the Crayons


By crayons you mean QML? Can't imagine what else you might mean... nothing
else fits 'crayons' so perfectly.


> Leave the mobile space to Html and Java.
>

No way, have to disagree. Mobile, where resources are even more
constrained, shouldn't be dominated by interpretted/networkBound
application environments.

Dontcha know the slogan for QThe Project (pronouced Q-The-Project)? Code
Once. Create More. Deploy Everywhere.
I think there should be only one requirement for whether or not QThe
targets a given device:

if(computer)
{
    target;
}
// I dream of QThe on my toaster (though i don't know what it's doing. JUST
BECAUSE WE CAN)

QThe should work towards adding Android/iOS targets
asep<http://www.youtube.com/watch?v=ZdVHZwI8pcA>,
including pulling in Necessitas's ADK/QTheCreator (<---omg QThe fits
'creator' perfectly!) integration, regardless of how buggy they are.... so
long as the bugs on those two platforms don't affect the others. Putting
the mobile platforms right in the user's face and calling them 'official'
will do wonders for bug reports, patch submissions, and, well.. you get the
idea.

Mobile's way too huge to overlook. Some would argue that mobile is the
future and that desktop/etc is dead. And while users definitely interact
with their phones very differently than the desktop, I don't think the
interaction is different enough that mobile should be ignored outright...
or even require a new development environment. QThe can do both (in theory.
and that's all code is before you write it anyways).

Now that all the Nokia devs live in trash cans, I guess it's up to us to
further [the?] QThe Project (i vote the word 'the' is not allowed to appear
directly in front of the word 'QThe'.... for no other reason than it
looks/sounds ugly and that I am allowed to vote). QML will be lopped off
anyways as per QThe's policy of modules requring an active maintainer to be
included in a release...  right? And QTheDeclarative as a whole might be
too large in general for the community to even finish before it even gets
to a maintainable status. I'll be sad if we lose QTheQuick along with it
:-/.

d3fault
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20120616/4c98b9b2/attachment.html>