On 15.08.2012 21:35, Romain Pokrzywka wrote:
> On Wednesday, August 15, 2012 08:36:35 PM Thiago Macieira wrote:
>> On quarta-feira, 15 de agosto de 2012 22.05.02, Konstantin Tokarev wrote:
>>> From wiki:
>>>
>>> "QPA on Qt4.8 only makes sense on OpenGL Hardware! If you don�t have
>>> OpenGL
>>> HW
On 07.08.2012 13:09, joao.abeca...@nokia.com wrote:
> While the two setups are very similar, almost isomorphs, they're not exactly
> so. There are important practical consequences that distinguish the two.
>
> - Releases happen on a fixed schedule
> - Minor versions have a defined lif
Hi,
On 07.08.2012 01:12, Thiago Macieira wrote:
> On terça-feira, 7 de agosto de 2012 01.00.54, Olivier Goffart wrote:
>> ---+--+-- fire-hose
>> / \ / / / / / / / / \ / / / / / /
>> --+ +-+++ +-++-
On 19.07.2012 03:29, Alan Alpert wrote:
> On Wed, 18 Jul 2012 19:00:01 ext Rafael Brandao wrote:
>
> There's a new enabled property which also prevents mouse input. It also
> affects
> keyboard focus, but if you aren't using keyboard focus you can bind enabled:
> opacity > 0 and get effectively th
On 17.07.2012 07:47, Alan Alpert wrote:
> But our Qt4Support library exists and is called QtQuick1. All the old symbols
> should be there, if you want to take the easy road to saying "done, ported to
> Qt 5!".
Well, there is no other choice if you have a platform without hardware
graphics accel
On 16.07.2012 16:06, Laszlo Papp wrote:
>> No, going through 443 is _not_ an option of the firewall, it's like
>> lock-picking a useless lock.
>
> No, the firewall and the whole establishment have the option to go out
> over the port 443.
So, you are saying, the implementer of such a firewall th
On 16.07.2012 15:26, Laszlo Papp wrote:
>> Sorry, but bike locks have keys to disable them. The sanity bot have an
>> option
>> to override it. Where is that option in your firewall?
>
> Going through 443.
No, going through 443 is _not_ an option of the firewall, it's like
lock-picking a usele
On 13.07.2012 17:10, Laszlo Papp wrote:
>> He also says that you should at the same time have a discussion with
>> Corporate Security to make them understand that the current situation is
>> hurting the organization, and try to get it changed so you _don't_ have
>> to circumvent Corporate Securit
On 02.07.2012 12:24, marius.storm-ol...@nokia.com wrote:
> Can the one responsible for this list please provide the development
> list a short description of the new ML and why it was needed?
I would assume that it's just a preparation to move the list
qt-compone...@qt.nokia.com to the qt-project
But then, where does qdoc get the information about inherited
members and the location of their documentation?
Thanks, and best regards,
Sven
> On 6/8/12 5:16 PM, "ext Sven Anderson" wrote:
>
>> Hi all,
>>
>> since qdoc is the only tool that can create docu
Hi all,
since qdoc is the only tool that can create documentation for QML APIs,
but it's (AFAIK) not supported as an external tool - although that is
very much needed especially for QML - I suggest to make qdoc the offical
tool for generation of external QML API documentation (and fix it
accor
On 25.05.2012 12:29, andre.poen...@nokia.com wrote:
>
> Sven Anderson:
>> I also don't think fixed numbers in rules are very wise. What about
>> offering some moving average stats of various metrics somewhere (maybe
>> they already exist?) and just referring to them in
Hi,
On 25.05.2012 09:34, André Somers wrote:
> Bottom line: let's not introduce rules that are supposed to solve
> problems that have not occured, and that are likely to cause more
> problems than they might ever prevent occuring in the first place. I
> would like to stimulate people to make the m
Am 02.11.2011 11:14, schrieb Olivier Goffart:
> But am I alone to think that 3 weeks of waiting time is a lot?
> 15 work day is a lot, how about reducing it to something between 7 and 10
> work days?
OTOH, is this really a time-critical process? In doubt I would choose
the longer option, not t
14 matches
Mail list logo
