On sábado, 16 de junho de 2012 01.59.16, warg...@gmx.de wrote:
> > > So is it farewell for Qt and QML? Not at all, says
> > >
> > > Nokia. 'Speculation is groundless,'"
> >
> > Don't trust The Register unless you can corroborate the evidence
> > from somewhere else.
>
> Ok, I don't trust The Re
On sexta-feira, 15 de junho de 2012 16.45.48, d3fault wrote:
> > No, most people don't want the rights to be exercised. The Foundation is a
> > "poison pill", a last resort solution if all else fails.
> >
> > We're nowhere near there.
>
> Why a poison pill? I'd consider it a life pill if anything.
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.
Fork the code, lets throw out the Crayons and let Qt thrive on the
Desktop, Server, and Enterprise space. Leave the mobile space to Html and
Java.
Jus
> >
> > So is it farewell for Qt and QML? Not at all, says
> > Nokia. 'Speculation is groundless,'"
>
> Don't trust The Register unless you can corroborate the evidence
> from somewhere else.
Ok, I don't trust The Register. But unfortunately I don't trust Nokia
even less. Much MUCH less.
Gui
On Fri, Jun 15, 2012 at 3:42 PM, Pau Garcia i Quiles
wrote:
> Hi,
>
> Actually, the KDE Free Qt Foundation agreement is not that good. It
> only covers X11. All the other important platforms are out: Windows,
> Mac, Android, iPhone, Symbian, QNX, VxWorks, etc. Probably Wayland
> would also be out
On sexta-feira, 15 de junho de 2012 15.35.52, d3fault wrote:
> LGPL is good enough. The fork is more important than triggering the BSD
> Clause..
No, most people don't want the rights to be exercised. The Foundation is a
"poison pill", a last resort solution if all else fails.
We're nowhere near
Hi,
Actually, the KDE Free Qt Foundation agreement is not that good. It
only covers X11. All the other important platforms are out: Windows,
Mac, Android, iPhone, Symbian, QNX, VxWorks, etc. Probably Wayland
would also be out (unless you find a very convincing way to show
Wayland is the successor
>
> I don't know why I waste my time talking to you...
>
because you love me and want to have my babies (he tried to convince me of
this once too! I have the message digitally signed)
You're right though: I'm retarded. I thought the legal text had explicitly
used the wording 'significant release'
Hi all,
After adding a desktop target to a Harmattan project, I could not
anymore deploy to QEMU 'target not available' was the error.
Knowing that re-installing the SDK helps that, I downloaded the
latest image and apparently to harmattan tool-chain post install is
broken, is this known? Or am
On sexta-feira, 15 de junho de 2012 14.31.26, 3dw...@verizon.net wrote:
> Here&aps;s hoping the upgrade at least the standard library a LOT faster
> going forward.
Great! Now maybe in C++15 or 16 we'll be able to convert strings from the
local 8-bit codec to Unicode without using , mbstowcs and ma
On sexta-feira, 15 de junho de 2012 13.35.56, d3fault wrote:
> Oh man thanks for reminding me of my strongest point in the 'fork' argument:
> If we DON'T fork, then OUR contributions contributed-to/'released' by them
> probably (can someone fill me in here?) won't allow the BSD Clause to ever
> tak
On sexta-feira, 15 de junho de 2012 13.13.10, d3fault wrote:
> On Fri, Jun 15, 2012 at 12:02 PM, Thiago Macieira > wrote:
> >
> > On sexta-feira, 15 de junho de 2012 11.42.07, d3fault wrote:
> > > The Qt Trademark and the Nokia Corporation might die (except Qt won't
> >
> > ever
> >
> > > 'officia
On Fri, Jun 15, 2012 at 11:50:47AM +0100, Rui Maciel wrote:
> Does anyone know what's the rationale for relying on Qt's custom QString
> instead of simply using C++'s standard and omnipresent std::string?
std::string is closer to QByteArray than to QString, so you are
probably not asking the que
Oh man thanks for reminding me of my strongest point in the 'fork' argument:
If we DON'T fork, then OUR contributions contributed-to/'released' by them
probably (can someone fill me in here?) won't allow the BSD Clause to ever
take effect. I think this might also be amplified by the fact that Nokia
If Nokia is not interested enough to maintain it, why would they be interested
enough to keep it non-BSD?
Its availability as LGPL as you point out, enable significant deployment of Qt
without the need for it to be BSD.
From: d3fault
To: Thiago Macieira
Cc:
On Fri, Jun 15, 2012 at 12:02 PM, Thiago Macieira wrote:
> On sexta-feira, 15 de junho de 2012 11.42.07, d3fault wrote:
> > The Qt Trademark and the Nokia Corporation might die (except Qt won't
> ever
> > 'officially' die. It's in Nokia/Microsoft's best interest to not let the
> > BSD Clause (
>
> From: "lorn.pot...@nokia.com"
>Subject: Re: [Interest] Is Nokia officially done with Qt?
>On 16/06/2012, at 12:11 AM, ext Doogster wrote:
>> Here's an article that does specifically mention Qt:
>>
>> http://www.theregister.co.uk/2012/06/14/nokia_software_purge/
>>
>> "Among the 10,000 casu
On 16/06/2012, at 5:37 AM, ext Sivan Greenberg wrote:
> On Fri, Jun 15, 2012 at 10:26 PM, wrote:
>>
>> We have been told the Qt asset (Brisbane, Oslo, Berlin - Trolltech) are not
>> "immediately" 'shutting our doors' like Ulm, and other areas. We have been
>> told we are still working on get
On Fri, Jun 15, 2012 at 10:26 PM, wrote:
>
> We have been told the Qt asset (Brisbane, Oslo, Berlin - Trolltech) are not
> "immediately" 'shutting our doors' like Ulm, and other areas. We have been
> told we are still working on getting Qt 5 released in the near term. We have
> also been told
"Are people fixing up resume/cv's and looking for new digs? You betcha."
Are there any one on this list with low-level embedded experience fixing up
their resumes? I can't promise a "Qt" job, but we are looking for quality
(Masters preferred) embedded people. On site in US-Baltimore.
__
I know C+11 is not available everywhere but they did work on lexical casting:string to_string(int val);string to_string(unsigned val);string to_string(long val);string to_string(unsigned long val);string to_string(long long val);string to_string(unsigned long long val);string to_string(float val);s
"He once tried to convince me that Microsoft actually likes Qt. Uhhh..
WHAT???"
What indeed. But Thiago knows his stuff.
We've had Miguel de Icaza arguing for OpenSource and .NET so I guess there is
one in every bunch. Not only is MS not succeeding as it once did (Failure of
Hotmail,
On 16/06/2012, at 12:11 AM, ext Doogster wrote:
> Here's an article that does specifically mention Qt:
>
> http://www.theregister.co.uk/2012/06/14/nokia_software_purge/
>
>"Among the 10,000 casualties officially announced are teams working on
>Meltemi, Qt and QML.
>
>So is it farew
On sexta-feira, 15 de junho de 2012 11.42.07, d3fault wrote:
> The Qt Trademark and the Nokia Corporation might die (except Qt won't ever
> 'officially' die. It's in Nokia/Microsoft's best interest to not let the
> BSD Clause ( http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php)
> ever
lol wut?
Did you guys feel that earthquake? It wasn't huge, but it's indicative of a
pressure build-up right beneath our feet. And you expect us to build our
houses on this land? Frack that, I'm moving to Nebraska.
(Translation: I'm definitely using QWidgets from now on. If Nokia kills Qt
or gets
On Fri, Jun 15, 2012 at 6:40 PM, Constantin Makshin wrote:
> I don't think that "mobile distraction" was really bad (but IMHO Symbian
> took more attention than it deserved) — there are not many frameworks
> that would be as both feature-rich and close to the "wrote once, run
> everywhere" princip
On sexta-feira, 15 de junho de 2012 12.19.27, Rui Maciel wrote:
> With C++11, UTF-16 strings are supported through the std::u16string
> type, which is a typedef for basic_string.
That's great. Except that the standards people often forget the most basic
things should be easy...
Here's one they fo
On 6/15/12 10:18 AM, Konstantin Tokarev wrote:
>
>
> 15.06.2012, 17:50, "Giuseppe D'Angelo" :
>> On 15 June 2012 14:35, Sven Anderson wrote:
>>
>>> On 15.06.2012 14:58, Thiago Macieira wrote:
Any one care to give me the Standard Library equivalent of:
QString::number(x)
>
15.06.2012, 21:26, "Charley Bay" :
> That's my venting because for over a decade I never understood why people
> thought std::string was an acceptable component. IMHO it's absolutely
> useless. And dangerous. I don't care if I'm the only one on the planet with
> my conclusion, but IMHO, std:
>
> >>> > But it's standard and it is C++.
> >> But (I think) the point was: what should have we used for the last
> >> 10-15 years of QString?
> >
> > I could've been a bit clearer in my initial post, but I intended to know
> > if there was currently any reason that justified having QString aroun
On Fri, 15 Jun 2012 17:39:06 +0300, Rui Maciel
wrote:
> On 06/15/2012 03:13 PM, Giuseppe D'Angelo wrote:
>>> > But it's standard and it is C++.
>> But (I think) the point was: what should have we used for the last
>> 10-15 years of QString?
>
> I could've been a bit clearer in my initial post,
Am 15.06.2012 um 17:50 schrieb Konstantin Tokarev :
>> Java on the
>> desktop? Dead... (at least on the Mac you sure will win the price of
>> the "Most Loved App").
>
> Don't confuse "dead" and "out of trend".
Well, I wasn't confusing... I was exagerating ;)
Anyway, my message was more along
That's why I've proposed Vaudeville, a companion to the GTK Broadway.
I already have something that works with a Qt4 Paint device... You run the app,
then point your browser and you see the app. Right now I just use a timer to
take the local widget and repaint it to the HTML5 canvas... It is almo
> From: Till Oliver Knoll
>2012/6/15 Rui Maciel :
Nevertheless, why is it important to support UTF-16?
>>>
>>> 1. Faster string search modification than for UTF8
>>> 2. It's native UTF string format on Windows and Mac OS X.
>>
>> How relevant is the efficiency of string search modification o
15.06.2012, 19:42, "Till Oliver Knoll" :
> 2012/6/15 Jason H :
>
>> Bleak? I was annoyed when Nokia took over TT, because substantial the
>> resources got moved to mobile. And I hated the preferred
>> Symbian-was-the-favoriate updates.
>>
>> ..., especially web services (consuming/providing)
2012/6/15 Jason H :
> Bleak? I was annoyed when Nokia took over TT, because substantial the
> resources got moved to mobile. And I hated the preferred
> Symbian-was-the-favoriate updates.
>
> ..., especially web services (consuming/providing) ...
That's not so bad. After all, Qt was initially in
I don't think that "mobile distraction" was really bad (but IMHO Symbian
took more attention than it deserved) — there are not many frameworks
that would be as both feature-rich and close to the "wrote once, run
everywhere" principle as Qt.
On 06/15/2012 07:00 PM, Jason H wrote:
> Bleak? I was ann
Hi,
Did anyone of you get his or her hands on a new MacBook Pro Retina display? :)
(for the sake of this discussion: assume any high-DPI device)
To my understanding after reading several news about it the OS does
the proper up-scaling for the high ~220 DPI of the Retina display,
such that an exi
On 15 June 2012 15:39, Rui Maciel wrote:
> On 06/15/2012 03:13 PM, Giuseppe D'Angelo wrote:
>>> > But it's standard and it is C++.
>> But (I think) the point was: what should have we used for the last
>> 10-15 years of QString?
>
> I could've been a bit clearer in my initial post, but I intended
On 6/15/2012 9:00 AM, Jason H wrote:
> I've always used it for desktop/server apps and will continue to do so. Glad
> the mobile distraction is over with. Let's get back to taking on .Net and
> Java..
+1
___
Interest mailing list
Interest@qt-project.or
2012/6/15 Paul Miller :
>>> ...
>>> QString::number(x)
>>
>> static_cast(&(ostringstream()<< x ) )->str();
>
> I just threw up a little in my mouth.
>
> I'll take QString::number(x), thank you.
Hehe, thanks for the chuckle, I was just about to write a similar story ;)
In fact, I'll pref
[proper recipient]
2012/6/15 Rui Maciel :
> ...
>
> Wouldn't it be better to simply provide an alternative std::string
> implementation for that specific case?
That's what has been done: it's called QString ;)
> And how relevant is that
> requirement today?
As others have mentioned, C++ 11 is n
Bleak? I was annoyed when Nokia took over TT, because substantial the resources
got moved to mobile. And I hated the preferred Symbian-was-the-favoriate
updates.
Qt is still sub-par in many areas, especially web services
(consuming/providing) and XML (If DOM is deprecated then we need Update
f
On 06/15/2012 03:13 PM, Giuseppe D'Angelo wrote:
>> > But it's standard and it is C++.
> But (I think) the point was: what should have we used for the last
> 10-15 years of QString?
I could've been a bit clearer in my initial post, but I intended to know
if there was currently any reason that ju
On sexta-feira, 15 de junho de 2012 17.46.37, Konstantin Tokarev wrote:
> 15.06.2012, 16:58, "Thiago Macieira" :
> > Any one care to give me the Standard Library equivalent of:
> >
> > QString::number(x)
>
> static_cast( &(ostringstream() << x ) )->str();
Don't forget the #include, which i
On 06/15/2012 12:25 PM, Konstantin Tokarev wrote:
>
>
> 15.06.2012, 15:19, "Rui Maciel":
>> On 06/15/2012 11:55 AM, Konstantin Tokarev wrote:
>>
>>> 1. Historical reasons - STL was not implemented on the same level in all
>>> compilers
>>> in the past.
>>
>> Is this constraint still relevant
On sexta-feira, 15 de junho de 2012 07.11.42, Doogster wrote:
> http://www.theregister.co.uk/2012/06/14/nokia_software_purge/
>
> "Among the 10,000 casualties officially announced are teams working on
> Meltemi, Qt and QML.
>
> So is it farewell for Qt and QML? Not at all, says Nokia. '
On 6/15/2012 8:46 AM, Konstantin Tokarev wrote:
>
>
> 15.06.2012, 16:58, "Thiago Macieira":
>> Any one care to give me the Standard Library equivalent of:
>>
>> QString::number(x)
>
> static_cast(&(ostringstream()<< x ) )->str();
I just threw up a little in my mouth.
I'll take QString::
15.06.2012, 17:50, "Giuseppe D'Angelo" :
> On 15 June 2012 14:35, Sven Anderson wrote:
>
>> On 15.06.2012 14:58, Thiago Macieira wrote:
>>> Any one care to give me the Standard Library equivalent of:
>>>
>>> QString::number(x)
>> string to_string(int) ?
>
> No go, C++11 only.
#if NO_C
On 15 June 2012 15:11, Doogster wrote:
> Here's an article that does specifically mention Qt:
>
> http://www.theregister.co.uk/2012/06/14/nokia_software_purge/
>
> "Among the 10,000 casualties officially announced are teams working on
> Meltemi, Qt and QML.
>
> So is it farewell for Qt an
On 15 June 2012 15:10, Rui Maciel wrote:
> On 06/15/2012 02:50 PM, Giuseppe D'Angelo wrote:
>>> > string to_string(int) ?
>> No go, C++11 only.
>
> But it's standard and it is C++.
But (I think) the point was: what should have we used for the last
10-15 years of QString?
--
Giuseppe D'Angelo
__
Here's an article that does specifically mention Qt:
http://www.theregister.co.uk/2012/06/14/nokia_software_purge/
"Among the 10,000 casualties officially announced are teams working on
Meltemi, Qt and QML.
So is it farewell for Qt and QML? Not at all, says Nokia. 'Speculation is
On 06/15/2012 02:50 PM, Giuseppe D'Angelo wrote:
>> > string to_string(int) ?
> No go, C++11 only.
But it's standard and it is C++.
Rui Maciel
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
On 15 June 2012 14:35, Sven Anderson wrote:
>
>
> On 15.06.2012 14:58, Thiago Macieira wrote:
>> Any one care to give me the Standard Library equivalent of:
>>
>> QString::number(x)
>
> string to_string(int) ?
No go, C++11 only.
--
Giuseppe D'Angelo
15.06.2012, 16:58, "Thiago Macieira" :
> Any one care to give me the Standard Library equivalent of:
>
> QString::number(x)
static_cast( &(ostringstream() << x ) )->str();
--
Regards,
Konstantin
___
Interest mailing list
Interest@qt-project.o
On 15.06.2012 14:58, Thiago Macieira wrote:
> Any one care to give me the Standard Library equivalent of:
>
> QString::number(x)
string to_string(int) ?
Sven
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/
On 15.06.2012 14:58, Thiago Macieira wrote:
> On sexta-feira, 15 de junho de 2012 16.12.55, Constantin Makshin wrote:
>> 3. std::string's behavior (e.g. use of the copy-on-write technique) is
>> implementation-dependent while QString is the same everywhere.
>
> C++11 bans that. C++11 says that st
On sexta-feira, 15 de junho de 2012 16.12.55, Constantin Makshin wrote:
> On 06/15/2012 02:55 PM, Konstantin Tokarev wrote:
> > 15.06.2012, 14:50, "Rui Maciel" :
> >> Does anyone know what's the rationale for relying on Qt's custom QString
> >> instead of simply using C++'s standard and omnipresent
On Fri, Jun 15, 2012 at 3:17 AM, André Pönitz <
andre.poen...@mathematik.tu-chemnitz.de> wrote:
> On Wed, Jun 13, 2012 at 07:52:45PM -0400, Josiah Bryan wrote:
> > The real problem here is that Qt Creator / Debugger doesn't even
> > bother to give a stack trace of where it stopped at - just the MS
15.06.2012, 16:12, "Constantin Makshin" :
> On 06/15/2012 02:55 PM, Konstantin Tokarev wrote:
>
>> 15.06.2012, 14:50, "Rui Maciel" :
>>> Does anyone know what's the rationale for relying on Qt's custom QString
>>> instead of simply using C++'s standard and omnipresent std::string?
>> 1. Histo
On 06/15/2012 02:55 PM, Konstantin Tokarev wrote:
> 15.06.2012, 14:50, "Rui Maciel" :
>> Does anyone know what's the rationale for relying on Qt's custom QString
>> instead of simply using C++'s standard and omnipresent std::string?
> 1. Historical reasons - STL was not implemented on the same leve
15.06.2012, 15:19, "Rui Maciel" :
> On 06/15/2012 11:55 AM, Konstantin Tokarev wrote:
>
>> 1. Historical reasons - STL was not implemented on the same level in all
>> compilers
>> in the past.
>
> Is this constraint still relevant today?
Not so long ago it turned out that toolchain for some S
On 06/15/2012 11:55 AM, Konstantin Tokarev wrote:
> 1. Historical reasons - STL was not implemented on the same level in all
> compilers
> in the past.
Is this constraint still relevant today?
> 2. std::string does not hadle UTF16 strings, and std::wstring is non-standard
With C++11, UTF-16
On Fri, Jun 15, 2012 at 12:55 PM, Sivan Greenberg wrote:
> Does Qt5 support JSON parsing as per its standard lib?
See QJsonDocument and friends in QtCore.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/int
Hi All,
I recalled some discussion from (Lars, Thiago ) and others about JSON
parsing support in Qt , what was the outcome? Does Qt5 support JSON
parsing as per its standard lib? Seeing this is still open[0] and that
I want to decide on the best way to quickly parse JSON in a client
app, I am ask
Hi,
I'm using Qt Quick on Windows and when calling a method written in Qt
from within QML I get a memory leak. So my first thought was to use
something like valgrind to find out in which method this leak occured,
because the runtime of Qt is not able to point me to the right
direction (and I don't
15.06.2012, 14:50, "Rui Maciel" :
> Does anyone know what's the rationale for relying on Qt's custom QString
> instead of simply using C++'s standard and omnipresent std::string?
1. Historical reasons - STL was not implemented on the same level in all
compilers
in the past.
2. std::string does
Does anyone know what's the rationale for relying on Qt's custom QString
instead of simply using C++'s standard and omnipresent std::string?
Thanks in advance,
Rui Maciel
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mai
On 06/15/2012 11:31 AM, Sven Anderson wrote:
> On 14.06.2012 18:22, Paul Miller wrote:
>> There was no mention at all about the fate of Qt. No reason to spread
>> any FUD.
>>
>> No matter - all my Qt applications continue to work, I can still get
>> Commercial support through Digia, and Open Govern
On 14.06.2012 18:22, Paul Miller wrote:
> There was no mention at all about the fate of Qt. No reason to spread
> any FUD.
>
> No matter - all my Qt applications continue to work, I can still get
> Commercial support through Digia, and Open Governance will keep it going.
I'm also not worried very
On 06/14/12 17:01, Jason H wrote:
> What is the issue here? That QDateTime does not handle the +HH:MM in the
> timezone string?
> At most I would see this being a possible datastream version bump, with
> a bit of code (No API changes? - I think we have what we need, just that
> the TZ does not pers
On Wed, Jun 13, 2012 at 07:52:45PM -0400, Josiah Bryan wrote:
> The real problem here is that Qt Creator / Debugger doesn't even
> bother to give a stack trace of where it stopped at - just the MSVC
> error dialog, no stack trace.
[...]
> I'll double-check globals, but a stack trace is really wha
72 matches
Mail list logo
