Hi all,
Thanks Thiago, Lars, Atlant and others. I updated the wiki page according to
this discussion:
http://developer.qt.nokia.com/wiki/Spelling_Module_Names_in_Qt_Documentation
To make this clear, the wiki page lists all the module names that have been
discussed for Qt 5.0 so far. I'm copying
On 12/12/11 6:21 PM, "ext Robin Burchell" wrote:
>On Thu, Dec 8, 2011 at 12:20 AM, Rohan McGovern
> wrote:
>> Unfortunately the qtwebkit pointed at by qt5.git is outdated and known
>> not to work.
>
>Given that webkit is developed upstream inside webkit.org, I'd second
>that there's no reason ha
The basic problem with the feature defines is that nobody is maintaining
them. There are also way too many of them to be able to test all
combinations, so things are bound to break.
Currently I'm more leaning towards advocating that people do feature
selection based on the modules (shared libs) th
On 12/14/11 6:34 PM, "ext henry.haveri...@nokia.com"
wrote:
>Hi all,
>
>I got some feedback outside this list about the documentation spelling of
>module names that contain acronyms. Now the guideline says we should
>write about the Qt Sql module, the Qt Xml module and so on. The feedback
>is tha
On 12/14/11 9:00 PM, "ext Jason Barron" wrote:
>Hi,
>
>On Wed, 2011-12-14 at 09:34 +0100, ext Robin Burchell wrote:
>> I'd sort of agree to leave it at a bug report, except that it hasn't
>> been done for a very long time already. With that in mind, plus
>> widgets not even having a maintainer at
Hi everybody,
sorry for not answering earlier. I actually wanted to bring the topic up
myself, but just didn't get it out so far. I've simply been traveling a
bit too much (I'm currently in Tokyo for the local Qt Developer event,
after we had a great one in Beijing two days ago with round 1100
par
The release process is very much community driven, with no specific team
assembled yet.
The part of actually creating the packages will have some help from both Nokia
and Digia, but the discussion about readiness and quality level needs to come
from the community; with a Chief Maintainer veto o
On Wednesday, 14 de December de 2011 21.20.40, Tomasz Siekierda wrote:
> On 14 December 2011 21:06, wrote:
> > By the way, do we have a release team or is it the sum of all the
> > maintainers?
> Hell knows, heaven suspects.
>
> But the question is indeed important. Won't Maintainers form at least
> They're already doing us a favour by with the openness report. I'd like to see
> an update to it, though, after another few months of Qt Project work.
Yep, we are in contact with them about this already.
--
Quim
___
Development mailing list
Developme
On 14 December 2011 21:06, wrote:
>
> By the way, do we have a release team or is it the sum of all the maintainers?
Hell knows, heaven suspects.
But the question is indeed important. Won't Maintainers form at least
part of that team by definition?
___
> 1. Thiago - thanks for a nice summary of release-connected vocabulary.
> 2. Kelly - thanks for the wiki, it's a good idea.
By the way, do we have a release team or is it the sum of all the maintainers?
--
Quim
___
Development mailing list
Development@
Hi,
just some ideas that might come in handy. If they don't - well, just ignore me.
1. Thiago - thanks for a nice summary of release-connected vocabulary.
2. Kelly - thanks for the wiki, it's a good idea.
Now, 2 possible additions to the freeze list:
3. What about recently (and quite vigorously)
On Wednesday, 14 de December de 2011 18.12.21, Stephen Kelly wrote:
> Ok, well let's start the list:
>
> https://wiki.qt-project.org/5.0_Feature_Requirements
>
> One thing we could do is:
>
> 1. Let people populate the list
> 2. Review the list for plausibility in a reasonable timeframe
> and
On Wednesday, December 14, 2011 17:07:21 Thiago Macieira wrote:
> On Wednesday, 14 de December de 2011 15.43.56, Stephen Kelly wrote:
> > > Also: what are the things we must still do before feature freeze?
> >
> > I think January is quite early, considering that means just between 2
> > and 6 week
On Wednesday, 14 de December de 2011 15.43.56, Stephen Kelly wrote:
> > Also: what are the things we must still do before feature freeze?
>
> I think January is quite early, considering that means just between 2 and 6
> weeks from now. There has been very little time for people outside of Nokia
> t
On Wednesday, 14 de December de 2011 09.46.10, Atlant Schmidt wrote:
> 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 absolute
Hi 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 believe the common practice is to spell these terms as acronyms:
XML is a W3C standard
On Tue, Dec 13, 2011 at 6:15 PM, wrote:
> What's state if the modules?
>
>
> For WebKit I think an API feature freeze would be okay in January. I think we
> are in good shape for that. Alexis, what do you think?
I think that our API for 5.0 (which doesn't mean it has to be in par
yet with what
Hi Henry,
On Wed, Dec 14, 2011 at 3:54 PM, wrote:
> Did you omit the mailing list by accident? I think this question might be
> interesting to others too, so do you mind if I post this on the list?
Yeah. I'm having a really terrible year for email...
>> if the includes, the headers, and the n
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
On Tuesday, December 13, 2011 21:18:34 Thiago Macieira wrote:
> So...
>
> When are we supposed to freeze? During Dev Days two weeks ago, we started
> discussing about it being in January.
>
> Can we set a more precise date? Let's say, a week [*]?
>
> Also: what are the things we must still do be
On Wednesday, 14 de December de 2011 14.02.59, quim@nokia.com wrote:
> I haven't. Vision Mobile is in fact a serious organization and their reports
> do get through the mobile industry. I won't lose a chance to pitch them Qt
> and the Qt Project if asked. :)
They're already doing us a favour b
I haven't. Vision Mobile is in fact a serious organization and their reports do
get through the mobile industry. I won't lose a chance to pitch them Qt and the
Qt Project if asked. :)
Quim
On 12/14/11 5:15 AM ext Stephen Kelly wrote:
Anyone else getting spam from these people?
The email
Hi,
it is currently not possible (at least I haven't yet found a way) to
track the global position of an item inside a
QGraphicsScene/SceneGraph.
Of course you can bind to x and y but those properties won't change if
a parent of the item moves. So the map functions do not really help
here.
See: h
On Wednesday 14 December 2011 09.34.54 henry.haveri...@nokia.com wrote:
> I got some feedback outside this list about the documentation spelling of
> module names that contain acronyms. Now the guideline says we should write
> about the Qt Sql module, the Qt Xml module and so on. The feedback is th
On Wednesday 14 December 2011 09.34.28 you wrote:
> On Wed, Dec 14, 2011 at 9:25 AM, Thomas Zander wrote:
> > If no tier one platforms are using it, I can understand your request,
> > but at the same time we are not removing symbian features, are we?
> Symbian is not supported in Qt 5, and Symbian
On 14 Dec, 2011, at 09:46 , ext Denis wrote:
[snip]
> Tell me, what it is: OS Windows feature or bug notifier?
This is a Windows "feature" you could say. You will see this behavior whenever
Windows runs a local event loop: moving or resizing a window with the mouse,
opening the application menu,
Hi,
On Wed, 2011-12-14 at 09:34 +0100, ext Robin Burchell wrote:
> I'd sort of agree to leave it at a bug report, except that it hasn't
> been done for a very long time already. With that in mind, plus
> widgets not even having a maintainer at the moment, let alone many
> contributors, plus that i
Hi Andre,
> I don't have a strong opinion on the docs. I'd think all caps is ok there if
> the
> items in question are known under such a name.
>
> But note that the class names are supposed to use QXml* (...StreamReader
> e.g.), QFtp* etc.
Certainly :)
In C++, we use the full module names st
On Wednesday 14 December 2011 10:34:54 ext henry.haveri...@nokia.com wrote:
> Hi all,
>
> I got some feedback outside this list about the documentation spelling of
> module names that contain acronyms. Now the guideline says we should write
> about the Qt Sql module, the Qt Xml module and so on.
Anyone else getting spam from these people?
The email says something about an open governance index. It was discussed on a
KDE list recently, but I got the spam to my kdab account.
Thanks,
--
Stephen Kelly | Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
www.kdab.co
Hi all,
I got some feedback outside this list about the documentation spelling of
module names that contain acronyms. Now the guideline says we should write
about the Qt Sql module, the Qt Xml module and so on. The feedback is that we
should write about the Qt SQL module, the Qt XML module, the
hi,
On Wed, Dec 14, 2011 at 9:25 AM, Thomas Zander wrote:
> If no tier one platforms are using it, I can understand your request, but at
> the same time we are not removing symbian features, are we?
Symbian is not supported in Qt 5, and Symbian code has been ripped out
from a lot of places alrea
On Tuesday 13 December 2011 19.04.18 Robin Burchell wrote:
> Hi,
> I'd like to propose a source-incompatible change for Qt 5: the removalof
> Qt::WA_*Orientation.
> The justification for this source-incompatible change is that (as faras I'm
> aware) the API has never really worked anywhere except S
34 matches
Mail list logo
