Most of the functionality was already in Qt 4 and was moved out for Qt 5
because of maintenance issues and different code for different platforms
exposed to the customer.
On 02/09/2013 10:35 PM, Sorvig Morten wrote:
> I agree the "Extra" looks superfluous. In fact I'd like to go a bit further
>
On segunda-feira, 2 de setembro de 2013 18:46:37, Oswald Buddenhagen wrote:
> > That defines what atomic is. It doesn't say that the commit must compile
> > and pass all tests if the rest of the commits in a topic are ignored.
> >
> >
>
> in fact, point 4 of the commit policy is pretty clear on
2013/8/22 Hirvonen Olli :
> Mirrorbrain system is working and we are closing the old CacheFly service
> 13th of September. The old service was using these addresses:
> releases.qt-project.org & origin.releases.qt-project.org. There is a
> redirect from releases.qt-project.org to download.qt-project
On Mon, Sep 02, 2013 at 08:16:17AM -0700, Thiago Macieira wrote:
> On segunda-feira, 2 de setembro de 2013 12:55:38, Oswald Buddenhagen wrote:
> > On Sat, Aug 31, 2013 at 03:08:56PM -0700, Thiago Macieira wrote:
> > > Of course, each commit must stand on its own and be self-contained (it has
> > >
On Sep 2, 2013, at 5:35 PM, Thiago Macieira
wrote:
> On segunda-feira, 2 de setembro de 2013 15:31:45, Sletta Gunnar wrote:
>> Hi,
>>
>> The new scene graph renderer was just accepted into the qtdeclarative "dev"
>> branch. I've done a fair amount of testing, but I'm sure some things will
>> h
On segunda-feira, 2 de setembro de 2013 15:31:45, Sletta Gunnar wrote:
> Hi,
>
> The new scene graph renderer was just accepted into the qtdeclarative "dev"
> branch. I've done a fair amount of testing, but I'm sure some things will
> have slipped through, so if you notice something: Create a bugr
Hi,
The new scene graph renderer was just accepted into the qtdeclarative "dev"
branch. I've done a fair amount of testing, but I'm sure some things will have
slipped through, so if you notice something: Create a bugreport, mail me or
ping me on IRC and I'll try to get it ironed out as soon as
On segunda-feira, 2 de setembro de 2013 12:55:38, Oswald Buddenhagen wrote:
> On Sat, Aug 31, 2013 at 03:08:56PM -0700, Thiago Macieira wrote:
> > Of course, each commit must stand on its own and be self-contained (it has
> > to compile and should hopefully pass all tests). If you have to choose
>
I agree the "Extra" looks superfluous. In fact I'd like to go a bit further and
suggest we don't have platform extras at all and instead integrate the
functionality into Qt:
- Conversion functions for types in QtCore to QtCore
- Conversion functions for types in QtGui to QtGui
- Widgets to QtWid
PS: Tried the same routine under Openbox with QtCreator - with the same
results (no layout change only on QtCreator with setxkbmap) .
Petko
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On 08/31/2013 07:35 PM, Thiago Macieira wrote:
> On sábado, 31 de agosto de 2013 14:51:58, Petko Ditchev wrote:
>>I need some help troubleshooting a problem I've been having : for a
>> week now (I think since some updates to the keyboard layout settings in
>> gnome) I can't change the keyboard
On Sat, Aug 31, 2013 at 03:08:56PM -0700, Thiago Macieira wrote:
> Of course, each commit must stand on its own and be self-contained (it has to
> compile and should hopefully pass all tests). If you have to choose between
> atomicity and self-containment, prefer self-containment.
>
atomicity im
The flat directory structure doesn't fix the QObject/QWidget subclass problem.
At the moment, this is in the "Too Hard" category.
martin
From: development-bounces+martin.smith=digia@qt-project.org
[development-bounces+martin.smith=digia@qt-project
On 02/09/2013 09:52, Smith Martin wrote:
> Two reasons. First, so people can enter documentation page paths without
> knowing
> the module subdirectory they are in. Second, so the pages will appear first
> in google searches.
One more reason: take the Qt5's QObject page, QWidget doesn't show i
On 02/09/2013 09:46, Saether Jan-Arve wrote:
> What you are suggesting should be possible, but I would like to explore if
> there can be a more generic way.
> You are suggesting to push this even further, i.e. one layout might use a
> QComboBox instead of a groupbox with radio buttons.
> * If its
On 2 September 2013 12:07, Joerg Bornemann wrote:
> Third, my rather obscure use case:
> switching between Qt4 and Qt5 doc URLs more easily.
This could easily be done by server-side redirections, though... (cf.
QTWEBSITE-504)
--
Giuseppe D'Angelo
___
On 02/09/2013 09:52, Smith Martin wrote:
> Two reasons. First, so people can enter documentation page paths without
> knowing the module subdirectory they are in. Second, so the pages will appear
> first in google searches.
Third, my rather obscure use case:
switching between Qt4 and Qt5 doc UR
Hi,
On Sunday 01 September 2013 13:20:10 Stefan Merettig wrote:
> The meta object compiler currently supports something it calls 'method
> tags', where it collects identifiers it doesn't know in front of
> methods:
>
> #ifndef Q_MOC_RUN
> # define MYTAG
> #endif
> ...
> MYTAG
Two reasons. First, so people can enter documentation page paths without
knowing the module subdirectory they are in. Second, so the pages will appear
first in google searches.
martin
From: development-bounces+martin.smith=digia@qt-project.org
[devel
What you are suggesting should be possible, but I would like to explore if
there can be a more generic way.
You are suggesting to push this even further, i.e. one layout might use a
QComboBox instead of a groupbox with radio buttons.
* If its pushed far enough, wouldn't this be like having two se
20 matches
Mail list logo
