I agree with d3fault on this one.
On 29/11/2012 1:07 PM, d3fault wrote:
> "always close to releasable" = testing
>
> -dev
> -testing
> -release or stable
>
> eradicates any chance of confusion, regardless of who is "right"
>
>
> d3fault
> ___
> Developme
Hi, Chen Qi,
Glad to see your contribution. But in qt-project era, maybe you could
contribute it to Qt via open governance way.
Reference:
http://blog.qt.digia.com/blog/2012/01/10/qt-4-moved-to-open-governance/
http://qt-project.org/contribute
And if you are Chinese, maybe you could also try th
Hi all,
Attached is a patch that makes qt4 work with long building path.
If qt4 is integrated into other projects, in my case, Yocto, it's likely
that the 256 length limit of its building path is not enough. See more
details in attachment.
Sorry if I'm sending this to the wrong ML. (If so, c
Hi all,
Attached is a patch that makes qt4 work with long building path.
If qt4 is integrated into other projects, in my case, Yocto, it's likely
that the 256 length limit of its building path is not enough. See more
details in attachment.
Sorry if I'm sending this to the wrong ML. (If so, c
"always close to releasable" = testing
-dev
-testing
-release or stable
eradicates any chance of confusion, regardless of who is "right"
d3fault
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/devel
On Thu, Nov 29, 2012 at 9:58 AM, d3fault wrote:
> The words "stable" and "release" are somewhat ambiguous (enough to
> warrant change).
>
> A release is implicitly stable, so the converse usually also holds
> true: stable is released.
Not really. IMO, stable should be an "always close to releasab
On 29/11/2012, at 5:47 AM, Knoll Lars wrote:
> If maintainers for other repositories would like to get the same branches
> setup, please speak up and tell Sergio and Janne. Both have agreed to do most
> of the actual work of creating the branches in gerrit and setting up the CI
> system and a
The words "stable" and "release" are somewhat ambiguous (enough to
warrant change).
A release is implicitly stable, so the converse usually also holds
true: stable is released.
d3fault
___
Development mailing list
Development@qt-project.org
http://list
On 28/11/12 22:45, Denis Shienkov wrote:
> Why not available Qt env variables from *.qdocconf file?
>
> For example,
>
> I need specify path to Qt Doc installation directory from my.qdocconf file:
>
> ...
> indexes = $QT_INSTALL_DOCS/doc/html/qt.index
$ in a .qdocconf file uses environment variabl
On Wed, Nov 28, 2012 at 09:35:40AM -0800, Romain Pokrzywka wrote:
> It would have been a good idea to ask a native English speaker before deciding
> on the name, as this is an atrocity, language-wise.
Is it?
But even if so, most of the target audience are not native speakers
of English either...
On 28 November 2012 18:35, Romain Pokrzywka wrote:
> It would have been a good idea to ask a native English speaker before
> deciding on the name, as this is an atrocity, language-wise. I'm not a
> native myself but I can tell this sounds wrong. 'Chose' is definitely not
> the right verb here, you
… this time for real… :)
Qt 5.0 is getting closer, and we're still working to get the final release out
before the end of the year. To make this easier and also allow new development
towards 5.1 to happen again, we'll branch the qt repositories during this
weekend in preparation for the Release
On quarta-feira, 28 de novembro de 2012 17.43.18, Knoll Lars wrote:
> The repository is now created, so I'd rather not change that (as that's a
> hazzle in gerrit). But we can still choose freely how to call the binary.
> Nobody apart from a few developers and packagers will ever see the
> reposito
On Wed, Nov 28, 2012 at 04:56:08PM +0100, Labs, Torsten wrote:
> Hello,
>
> is there a possibility to add the current help for Qt5.0-snapshot in a self
> compiled Qt Creator with Qt5 Libs. At the moment if i press F1 i get allways
> "No Documentation available.
If you have a (_really_) recent bu
The repository is now created, so I'd rather not change that (as that's a
hazzle in gerrit). But we can still choose freely how to call the binary.
Nobody apart from a few developers and packagers will ever see the repository
name anyway.
Cheers,
Lars
On Nov 28, 2012, at 6:35 PM, Romain Pokrz
It would have been a good idea to ask a native English speaker before
deciding on the name, as this is an atrocity, language-wise. I'm not a
native myself but I can tell this sounds wrong. 'Chose' is definitely not
the right verb here, you probably wanted 'select' instead?
On top of that, IMO the
> From: BRM
> Sent: Monday, November 26, 2012 9:39 PM
> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>> From: Matt Broadstone
>> Subject: Re: [Development] Qt Playground - Updating Daemon/Service Support
>> On Mon, Nov 26, 2012 at 1:48 PM, BRM wrote:
>>> From: Ch
Hello,
is there a possibility to add the current help for Qt5.0-snapshot in a self
compiled Qt Creator with Qt5 Libs. At the moment if i press F1 i get allways
"No Documentation available.
Thx.
With best regards,
Torsten Labs
Siemens AG
Industry Sector
Industry Automation Division
Industrial
Maybe you can create a my.qdocconf.in file, then let qmake generating
proper my.qdocconf file for you.
On Wed, Nov 28, 2012 at 8:45 PM, Denis Shienkov wrote:
> Hello, Qt developers.
>
> Why not available Qt env variables from *.qdocconf file?
>
> For example,
>
> I need specify path to Qt Doc i
On Wed, Nov 28, 2012 at 1:35 PM, Poenitz Andre wrote:
>> Nope, but I guess that a common interpretation of pro-files between
>> qmake and QtCreator are of interest to most.
>
> You need contemporary versions of Qt Creator for use with recent versions of
> Qt.
Verified with a fresh git clone, the
Hello, Qt developers.
Why not available Qt env variables from *.qdocconf file?
For example,
I need specify path to Qt Doc installation directory from my.qdocconf file:
...
indexes = $QT_INSTALL_DOCS/doc/html/qt.index
...
After make:
$qmake my.pro file
creates a Makefile with docs target,
On Wed, Nov 28, 2012 at 1:36 PM, Oswald Buddenhagen
wrote:
> On Wed, Nov 28, 2012 at 01:17:58PM +0100, Johan Thelin wrote:
>> On Wed, Nov 28, 2012 at 11:24 AM, Daniel Teske
>> wrote:
>> >> - Means that source code where headers and sources are split into
>> >> different directories all of a sudd
On Wed, Nov 28, 2012 at 01:17:58PM +0100, Johan Thelin wrote:
> On Wed, Nov 28, 2012 at 11:24 AM, Daniel Teske wrote:
> >> - Means that source code where headers and sources are split into
> >> different directories all of a sudden depends on relative paths to all
> >> files
> > See VPATH, which O
> Nope, but I guess that a common interpretation of pro-files between
> qmake and QtCreator are of interest to most.
You need contemporary versions of Qt Creator for use with recent versions of Qt.
Andre'
___
Development mailing list
Development@qt-proj
On Wed, Nov 28, 2012 at 1:30 PM, Daniel Teske wrote:
> On Wednesday 28 Nov 2012 13:17:58 Johan Thelin wrote:
>> On Wed, Nov 28, 2012 at 11:24 AM, Daniel Teske
> wrote:
>> >> - Means that source code where headers and sources are split into
>> >> different directories all of a sudden depends on re
On Wednesday 28 Nov 2012 13:17:58 Johan Thelin wrote:
> On Wed, Nov 28, 2012 at 11:24 AM, Daniel Teske
wrote:
> >> - Means that source code where headers and sources are split into
> >> different directories all of a sudden depends on relative paths to all
> >> files
> >
> > See VPATH, which Oss
On Wed, Nov 28, 2012 at 11:24 AM, Daniel Teske wrote:
>> - Means that source code where headers and sources are split into
>> different directories all of a sudden depends on relative paths to all
>> files
> See VPATH, which Ossi already mentioned in the bug report.
yup, will do. I'm just questio
On 2012-11-28, Labs, Torsten wrote:
> Hello,
>
> does anybody know something about a possiblity to use C# for programming Qt=
> 5 and Qt Quick?
> I know this sounds funny :-)
I would expect the people behind Qyoto (Qt4 mono bindings) will move on
to Qt 5 sometime in the future.
iirc Qyoto (a
Hello,
does anybody know something about a possiblity to use C# for programming Qt5
and Qt Quick?
I know this sounds funny :-)
With best regards,
Torsten Labs
Siemens AG
Industry Sector
Industry Automation Division
Industrial Automation Systems
Factory Automation
__
> - Means that source code where headers and sources are split into
> different directories all of a sudden depends on relative paths to all
> files
See VPATH, which Ossi already mentioned in the bug report.
> - Behaves differently from QtCreator (tested with a rather old version
> 2.5.2).
What ex
Hi,
Thanks for your reply.
I created a bug at https://bugreports.qt-project.org/browse/QTWEBKIT-383.
On Wed, Nov 28, 2012 at 3:26 PM, Hausmann Simon wrote:
> Hi,
>
> If the issue appears only with QtWebKit on Windows but not with the same
> version on Mac or Linux/X11, then I think it is very u
> -Original Message-
> From: development-bounces+jan-arve.saether=digia@qt-project.org
> [mailto:development-bounces+jan-arve.saether=digia@qt-project.org]
> On Behalf Of Oswald Buddenhagen
> Sent: 27. november 2012 17:13
> To: development@qt-project.org
> Subject: Re: [Development]
On Wednesday, November 28, 2012 09:38:24 AM Konstantin Ritt wrote:
> OR this could be a result of using QRawFont "backdoor" :)
That wouldn't explain though why it works on Mac and Linux, no?
There are two code paths in WebKit, a fast text code path and one for complex
text (note how it's not cal
33 matches
Mail list logo
