research@qt-project.org
[mailto:development-bounces+aschmidt=dekaresearch@qt-project.org] On Behalf
Of Samuel Rødal
Sent: Monday, October 01, 2012 9:11 AM
To: development@qt-project.org
Subject: Re: [Development] resolution independence (was Re: Retina display
support)
On 10/01/2012 01:
Folks:
> Likewise the idea that HiDPI displays are always "2x" seems to me another
> inelegant hack. Actually the DPI varies between devices, so high-resolution
> art should not always need to be exactly 2x the normal size. It may be
> convenient, but it's not the kind of "solution" we can expec
Folks:
Yesterday, I attended the trade show at the Embedded Systems Conference
East, held annually in Boston Massachusetts. I'm glad to say that Qt had a
booth there on the trade show floor, staffed by Digia employees.
This year, the story being told in the Qt booth was a good one, addres
All:
Congratulations to everyone who survived the transition;
I can't imagine it's been an easy several years for any
of you!
And best wishes to the Qt team going forwards!
Atlant
-Original Message-
From: development-bounces+aschmidt=dekaresearch.
Brisbane folks:
> I would say most of the talented engineers in Brisbane are
> still looking for jobs. (hint, hint, hint)
How's your Finnish / Suomi?
Is Digia hiring? Jolla certainly still is!
Atlant
-Original Message-
From: development-bounces+aschmidt=dekare
I'll retry this question once seeing as how I got no answers
after a month...
Situation:
We have an application using Qt 4.6.2 on Embedded Linux (so
QWS). Our client has requested that the Japanese version of
our app use the Hiragino font.
Problem:
But we've seen that several (many? mo
All:
> > nice, but you forgot to mention your favourite colour.
>
> Right, that's important. (for the bike shed)
Look, it's either that or the airspeed of a swallow!
Atlant
-Original Message-
From: development-bounces+aschmidt=dekaresearch@qt-project.org
All:
This is *GREAT* news!
Digia have always been hard workers including all of
their work on Qt (as a Nokia contractor) before most
of you probably heard of them.
Their statement that they will "bring back focus on Qt's
desktop and embedded platform support" is also welcome
news a
g] On Behalf
Of Atlant Schmidt
Sent: Wednesday, August 01, 2012 8:30 AM
To: '"C. Bergström"'; development@qt-project.org
Subject: Re: [Development] state of Qt's Australia office
Folks:
I wasn't going to mention this but since the topic has come up...
A source I
Folks:
I wasn't going to mention this but since the topic has come up...
A source I consider reliable has whispered in my ear that
in the aftermath of Nokia recently shooting Meltemi dead*,
Sebastian Nyström (the Nokia Senior VP in charge of Qt) has
been given explicit direction to sell
For those of us who couldn't be there, "Thanks!" to everyone
who is providing notes from the Contributor Summit!
Atlant
-Original Message-
From: development-bounces+aschmidt=dekaresearch@qt-project.org
[mailto:development-bounces+aschmidt=dekaresearc
Alexis:
> I hate to point fingers but reading this made me sad :
>
> http://labs.qt.nokia.com/2012/06/18/qt-5-accessibility-apis/#comments
That's actually an excellent example of how/why electronic
discussions often go sour. The basic algorithm is:
1. Begin discussion about something mea
All:
> W00t should have a backlog which covers the conversation,
> if it was done on our public channels :-)
If only Pierre de Fermat had had that feature!
Atlant
-Original Message-
From: development-bounces+aschmidt=dekaresearch@qt-project.org
[mailto:dev
Folks:
There's been a lot of discussion recently regarding whether
or not Qt functions (specifically, interlocking functions)
should be declared "inline" or not.
But in fact, isn't this much ado about nothing? If I
understand current compiler technology, when one declares
a function "
ailto:development-bounces+aschmidt=dekaresearch@qt-project.org] On Behalf
Of Kate Alhola
Sent: Friday, May 18, 2012 04:22
To: development@qt-project.org
Subject: Re: [Development] The place of QML
On Thu, May 17, 2012 at 1:35 PM, Atlant Schmidt
wrote:
> Peter, et al.:
>
>> We don&#x
ishnan [mailto:gir...@forwardbias.in]
Sent: Thursday, May 17, 2012 14:45
To: Atlant Schmidt
Cc: Peter Kümmel; development@qt-project.org
Subject: Re: [Development] The place of QML
Hi Atlant,
On Thu, May 17, 2012 at 11:18 AM, Atlant Schmidt
wrote:
> Peter:
>
>> Then Qt Widgets is perfe
esearch@qt-project.org] On Behalf
Of Peter Kümmel
Sent: Thursday, May 17, 2012 12:24
Cc: development@qt-project.org
Subject: Re: [Development] The place of QML
On 17.05.2012 12:35, Atlant Schmidt wrote:
> Peter, et al.:
>
>> We don't wanna use obsolete stuff with a "architec
Peter, et al.:
> We don't wanna use obsolete stuff with a "architecture from
> the 90s" in times where "graphical technology has moved on" (Thiago).
Computer architectures don't necessarily "become obsolete".
Oh, trends come and trends go, but the fundamental concepts
go on forever. For exa
for other customers, hence our current debate
about QML Qt versus QWidget Qt.
Atlant
-Original Message-
From: ro...@viroteck.net [mailto:ro...@viroteck.net] On Behalf Of Robin Burchell
Sent: Wednesday, May 16, 2012 10:56
To: Atlant Schmidt
Cc: Samuel Rødal; deve
Samuel:
> It's worth noting that the Qt project is designed to
> be a meritocracy, not a democracy.
What this ignores, though, is the fact that the *CONSUMERS*
of the Qt product are not necessarily at all congruent with
the *DEVELOPERS* of the Qt product. (While there's some
cross-over, I
d3fault:
> Trolltech may have been in the red, but that doesn't mean it
> would have stayed in the red. And if would never have seen a
> profit, then why would Nokia have it?
Nokia bought Trolltech for one simple reason: Development
on Symbian/S60/Averell/Avkon was too arcane/too weird and
Ben:
> For starters, there's already a foundation in place -
>http://www.kde.org/community/whatiskde/kdefreeqtfoundation.php.
> That Foundation has the right to license Qt under a "BSD-style
> license or under other open source licenses" regardless of
> any other licensing. ...
No, there's
Thiago:
Does the project maintain a list of "Subject Matter Experts"
from which 1) volunteers could be solicited or 2) reviewers
could be "drafted"? If not, *SHOULD* the project maintain
such a list?
Otherwise, it's as we saw in "T2"...
http://noffload.net/uploader/files/1/term2/t2
Folks:
> If you can prove that, you are assured Fields Medal.
> > I am sure with a bunch of boolean operations. We can create a teapot from a
> > cube.
As long as you don't mind your teapot spout being open
rather than a tube and your teapot handle not having a
hole in it, then yes, the c
Frederik:
> We didn't have this email in a while and I don't know how
> regular we get around to sending it, but it might be
> interesting. If everyone here thinks it's spam, we'll stop ;)
I support your sending of this mail.
I think it will be valuable in keeping everyone
aware of:
1
may not have tested) doesn't
work without producing warnings?
Atlant
-Original Message-
From: ro...@viroteck.net [mailto:ro...@viroteck.net] On Behalf Of Robin Burchell
Sent: Thursday, March 15, 2012 07:36
To: Atlant Schmidt
Cc: Thiago Macieira; development@qt
Thiago:
> -Werror should never be enabled on non-developer builds.
Why not? Is the plan to ship code that contains
warnings?*
This is the sort of thing that destroyed Symbian.
When I last counted, the Symbian build routinely
produced more than 7,000 warnings. No one at Nokia
besides
Rohan:
Because no one more-authoritative has answered you,
I'll give it a try.
I think that this occurs because QVariant must have
sufficiently-strict alignment constraints to hold,
properly aligned, the largest POD datum that can be
stored in the variant. Other, more-specific objects
Shawn:
> BTW back in the 80's I knew an old civil engineer who was new to
> computers (more of a slide-rule guy) and thought that "mouse" referred
> to what we usually call the cursor (the arrow on the screen). I've
> also seen in the context of CAD digitizing tablets that the puck you
> move aro
Shawn:
This sounds like the roots of a strong proposal -- carry on!
Two thoughts:
o Please be sure your "pointing device" proposal
can be generalized beyond "mice and touchscreens".
There are certainly other pointing devices already
in the world (who remembers Light Pen
João:
> I think the even better approach, once the necessary changes are done
> inside Qt and things settle down, is to drop qreal completely. Don't
> pick float or real, don't define it. Or typedef it to some dummy type:
>
>class qreal_IsNoMore {};
>typedef qreal_IsNoMore qreal;
>
> Force
pment] Possible bug in signals and slots handling in QML.
On Wednesday, 4 de January de 2012 07.51.48, Atlant Schmidt wrote:
> Thiago, et al.:
>
> This is another one of those "don't play in the
> grey areas of the language" things.
>
> Even if iden
Thiago, et al.:
This is another one of those "don't play in the
grey areas of the language" things.
Even if identifiers are case-sensitive, one should
probably never depend upon that; why tempt fate?
Atlant
-Original Message-
From: development-bounces+a
Tuukka:
How can we most-easily discover the list of changes that
are in Qt Commercial 4.8.0 but not in (LGPL) Qt 4.8.0?
We have several bugs we're particularly interested in...
Atlant
From: development-bounces+aschmidt=dekaresearch@qt-project.org
Thomas:
> names like 'xml' are no longer abbreviations, they are product names.
> Not just something that Qt made up, but industry wide known product names.
>
> As such they should have only one capital.
I absolutely disagree with this.
The correct spelling of "XML" is "XML". The only time w
Folks:
I've avoided entering this topic because, as a Wikipedia administrator,
I might be perceived as being biased in favor of Wikimedia, but I want
to echo and amplify what Stephen has said:
WYSIWYG editors may be easier for novice wikipedians to use, but
markup-based editors are far
r support
On Tuesday, 8 de November de 2011 06:39:23 Atlant Schmidt wrote:
> When you settle on the set of "enhanced" features that
> compilers must support to allow use with Qt, please design,
> as the VERY FIRST PORTIONS of the Qt build procedure, a
> small series of prog
Folks:
With regard to compiler support, I would like to make
one small suggestion:
When you settle on the set of "enhanced" features that
compilers must support to allow use with Qt, please design,
as the *VERY FIRST PORTIONS* of the Qt build procedure, a
small series of programs that
38 matches
Mail list logo
