On terça-feira, 17 de abril de 2012 15.02.22, lars.kn...@nokia.com wrote:
> >The access to screen() and display() may indicate a missing Qt API, which
> >we
> >may be able to add. If the X11 dependency was intentional, it can be
> >ported to
> >QPlatformNativeInterface, to obtain the XCB pointers.
On 4/17/12 1:15 AM, "ext Thiago Macieira"
wrote:
>On segunda-feira, 16 de abril de 2012 21.31.52, Fredrik Höglund wrote:
>> On Monday 16 April 2012, Thiago Macieira wrote:
>> > On segunda-feira, 16 de abril de 2012 00.02.21, Stephen Kelly wrote:
>> > > Can you point me to it? Does it contain a eq
On segunda-feira, 16 de abril de 2012 21.31.52, Fredrik Höglund wrote:
> On Monday 16 April 2012, Thiago Macieira wrote:
> > On segunda-feira, 16 de abril de 2012 00.02.21, Stephen Kelly wrote:
> > > Can you point me to it? Does it contain a equivalent
> > > API to QX11Info (the removal of this cla
On Monday 16 April 2012, Thiago Macieira wrote:
> On segunda-feira, 16 de abril de 2012 00.02.21, Stephen Kelly wrote:
> > Can you point me to it? Does it contain a equivalent
> > API to QX11Info (the removal of this class is a problem for KDE which
> > doesn't have a solution yet).
>
> KDE needs
Hi,
On Fri, Apr 13, 2012 at 10:08 AM, Girish Ramakrishnan
wrote:
> Hi,
> I am going through all the new apis. I have a couple of more changes
> to the public apis already. I am not submitting them to api_changes
> branch. I think Lars and co are having enough trouble as-is with
> getting api_chan
Hi,
On Mon, Apr 16, 2012 at 6:46 AM, Oswald Buddenhagen
wrote:
> On Mon, Apr 16, 2012 at 10:21:00AM -0300, ext Thiago Macieira wrote:
>> On segunda-feira, 16 de abril de 2012 10.30.50, Oswald Buddenhagen wrote:
>> > On Fri, Apr 13, 2012 at 03:16:54PM -0300, ext Thiago Macieira wrote:
>> > > 2) ad
On segunda-feira, 16 de abril de 2012 15.46.36, Oswald Buddenhagen wrote:
> On Mon, Apr 16, 2012 at 10:21:00AM -0300, ext Thiago Macieira wrote:
> > On segunda-feira, 16 de abril de 2012 10.30.50, Oswald Buddenhagen wrote:
> > > On Fri, Apr 13, 2012 at 03:16:54PM -0300, ext Thiago Macieira wrote:
>
On Mon, Apr 16, 2012 at 10:21:00AM -0300, ext Thiago Macieira wrote:
> On segunda-feira, 16 de abril de 2012 10.30.50, Oswald Buddenhagen wrote:
> > On Fri, Apr 13, 2012 at 03:16:54PM -0300, ext Thiago Macieira wrote:
> > > 2) add #pragma qt_no_master_include so that they aren't included in
> > >
On segunda-feira, 16 de abril de 2012 14.51.31, Michael Jansen wrote:
> One thing i would like to add.
>
> In kde we have a central daemon that manages the global shortcuts for all
> kde apps. Other apps talk to him by dbus.
>
> This was done (afaik) because on the mac this behavious is a must. But
On segunda-feira, 16 de abril de 2012 10.30.50, Oswald Buddenhagen wrote:
> On Fri, Apr 13, 2012 at 03:16:54PM -0300, ext Thiago Macieira wrote:
> > 2) add #pragma qt_no_master_include so that they aren't included in
> >
> > and people use them by accident because they happened to complete in
> >
> >in question is complex. A source of many kde bugs.
> >
> >All that descibes Qt4. No idea what changed in Qt5.
> >
> >But such function or some Qt support for global shortcuts would help us.
> >
> >The same applies afaik for the mac. No idea about windows.
>
> IMO this ideally belongs as an ext
On 4/16/12 2:15 PM, "ext Michael Jansen" wrote:
>On Sunday, April 15, 2012 08:40:38 PM Thiago Macieira wrote:
>> On segunda-feira, 16 de abril de 2012 01.33.31, Stephen Kelly wrote:
>> > > The only applications that should do that are the workspace fixture
>> > > ones:
>> > > kwin and plasma.
>
On Sunday, April 15, 2012 08:40:38 PM Thiago Macieira wrote:
> On segunda-feira, 16 de abril de 2012 01.33.31, Stephen Kelly wrote:
> > > The only applications that should do that are the workspace fixture
> > > ones:
> > > kwin and plasma.
> >
> > Yes, those are the ones that were brought up, tog
On Fri, Apr 13, 2012 at 03:16:54PM -0300, ext Thiago Macieira wrote:
> 2) add #pragma qt_no_master_include so that they aren't included in
> and people use them by accident because they happened to complete in
> QtCreator
> or another IDE
>
this is entirely unnecessary when the files are renam
On segunda-feira, 16 de abril de 2012 01.33.31, Stephen Kelly wrote:
> > The only applications that should do that are the workspace fixture ones:
> > kwin and plasma.
>
> Yes, those are the ones that were brought up, together with the
> KWindowSystem class. Apart from those I don't think KDE uses
On Sunday, April 15, 2012 20:03:38 Thiago Macieira wrote:
> On segunda-feira, 16 de abril de 2012 00.59.51, Stephen Kelly wrote:
> > On Sunday, April 15, 2012 19:32:46 Thiago Macieira wrote:
> > > > Can you point me to it? Does it contain a equivalent
> > > > API to QX11Info (the removal of this cl
On segunda-feira, 16 de abril de 2012 00.59.51, Stephen Kelly wrote:
> On Sunday, April 15, 2012 19:32:46 Thiago Macieira wrote:
> > > Can you point me to it? Does it contain a equivalent
> > > API to QX11Info (the removal of this class is a problem for KDE which
> > > doesn't have a solution yet).
On Sunday, April 15, 2012 19:32:46 Thiago Macieira wrote:
> > Can you point me to it? Does it contain a equivalent
> > API to QX11Info (the removal of this class is a problem for KDE which
> > doesn't have a solution yet).
>
> KDE needs to be ported away from it anyway. It cannot depend on X11
> s
On segunda-feira, 16 de abril de 2012 00.02.21, Stephen Kelly wrote:
> On Friday, April 13, 2012 19:48:49 lars.kn...@nokia.com wrote:
> > ie. we have a QtX11/QtMac/QtWinSupport add-ons. That's also a natural
> > place to add feature gaps to Qt 4.x such as QX11Embed into.
>
> There's a QtX11 add-on?
On Friday, April 13, 2012 19:48:49 lars.kn...@nokia.com wrote:
> ie. we have a QtX11/QtMac/QtWinSupport add-ons. That's also a natural
> place to add feature gaps to Qt 4.x such as QX11Embed into.
There's a QtX11 add-on? Can you point me to it? Does it contain a equivalent
API to QX11Info (the re
On Fri, Apr 13, 2012 at 12:48 PM, wrote:
> On 4/13/12 7:18 PM, "ext Samuel Rødal" wrote:
>
>>On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
>>> Hi,
>>> I am going through all the new apis. I have a couple of more changes
>>> to the public apis already. I am not submitting them to api_cha
On 4/13/12 7:18 PM, "ext Samuel Rødal" wrote:
>On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
>> Hi,
>> I am going through all the new apis. I have a couple of more changes
>> to the public apis already. I am not submitting them to api_changes
>> branch. I think Lars and co are having eno
On 04/13/2012 08:41 PM, ext Girish Ramakrishnan wrote:
> Hi,
>
> On Fri, Apr 13, 2012 at 11:30 AM, Girish Ramakrishnan
> wrote:
>
>> I think the idea with _qpa_ in the file name is to imply that it has
>> plugin api. As opposed to let's say qpen_p.h. This means that when I
>> see a change to a _
On sexta-feira, 13 de abril de 2012 11.30.42, Girish Ramakrishnan wrote:
> Yes, agreed (and thanks for those pragmas that I was not aware of).
Remember to wrap them in #if 0, so only syncqt will see them.
> I think the idea with _qpa_ in the file name is to imply that it has
> plugin api. As oppo
Hi,
On Fri, Apr 13, 2012 at 11:30 AM, Girish Ramakrishnan
wrote:
> I think the idea with _qpa_ in the file name is to imply that it has
> plugin api. As opposed to let's say qpen_p.h. This means that when I
> see a change to a _qpa.h file, I know that plugins will get affected
> by this api chan
Hi Thiago,
2012/4/13 Thiago Macieira :
> On sexta-feira, 13 de abril de 2012 11.03.58, Girish Ramakrishnan wrote:
>> Hi Thiago,
>> > Let's please not invent a new rule.
>> >
>> > If it's _p.h, it's private, otherwise it's public and subject to source-
>> > and binary-compatibility guarantees. If t
On sexta-feira, 13 de abril de 2012 11.03.58, Girish Ramakrishnan wrote:
> Hi Thiago,
> > Let's please not invent a new rule.
> >
> > If it's _p.h, it's private, otherwise it's public and subject to source-
> > and binary-compatibility guarantees. If there's API in some files that we
> > don't want
Hi Thiago,
2012/4/13 Thiago Macieira :
> On sexta-feira, 13 de abril de 2012 19.18.26, Samuel Rødal wrote:
>> On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
>> > Hi,
>> > I am going through all the new apis. I have a couple of more changes
>> > to the public apis already. I am not submitti
On sexta-feira, 13 de abril de 2012 19.18.26, Samuel Rødal wrote:
> On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
> > Hi,
> > I am going through all the new apis. I have a couple of more changes
> > to the public apis already. I am not submitting them to api_changes
> > branch. I think Lar
On 04/13/2012 07:27 PM, ext Girish Ramakrishnan wrote:
> On Fri, Apr 13, 2012 at 10:18 AM, Samuel Rødal wrote:
>> On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
>>> My current understanding of the "qpa" plan is this, correct me if I am
>>> wrong:
>>> 1. Files with _qpa in them are suppose
On Fri, Apr 13, 2012 at 10:18 AM, Samuel Rødal wrote:
> On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
>> Hi,
>> I am going through all the new apis. I have a couple of more changes
>> to the public apis already. I am not submitting them to api_changes
>> branch. I think Lars and co are ha
On 04/13/2012 07:08 PM, ext Girish Ramakrishnan wrote:
> Hi,
> I am going through all the new apis. I have a couple of more changes
> to the public apis already. I am not submitting them to api_changes
> branch. I think Lars and co are having enough trouble as-is with
> getting api_changes to merge
Hi,
I am going through all the new apis. I have a couple of more changes
to the public apis already. I am not submitting them to api_changes
branch. I think Lars and co are having enough trouble as-is with
getting api_changes to merge to master :-) All the commits will have
the "api:" prefix in the
33 matches
Mail list logo
