I only want to point out that the performance with extended monitor is NOT
that great when using Intel 965, right now my resolution is:
with: 1280 + 1920
height: 1080
total: 3200x1080
To be able to support this kind of textures some tricks has been added to
the driver but even with that the per
A Romario's message somehow got bouced away by the server, pasting here:
2011/2/20 Martin Gräßlin
> On Sunday 20 February 2011 22:30:01 Beat Wolf wrote:
> > Then leave it out during dev, but in when releasing.
> I wrote that in my initial mail about the config option.
> >
> > I just don't agree
On Sunday 20 February 2011 23:03:10 Martin Gräßlin wrote:
> On Sunday 20 February 2011 22:50:01 Dario Freddi wrote:
> > On Sunday 20 February 2011 13:38:40 Martin Gräßlin wrote:
> > > Hi all,
> > >
> > > sending this to both Plasma and KWin as the idea affects the complete
> > > workspace.
> > >
- Ursprüngliche Mitteilung -
> 2011/2/20 Martin Gräßlin
>
> > On Sunday 20 February 2011 22:30:01 Beat Wolf wrote:
> > > Then leave it out during dev, but in when releasing.
> > I wrote that in my initial mail about the config option.
> > >
> > > I just don't agree that for example nvid
2011/2/20 Martin Gräßlin
> On Sunday 20 February 2011 22:30:01 Beat Wolf wrote:
> > Then leave it out during dev, but in when releasing.
> I wrote that in my initial mail about the config option.
> >
> > I just don't agree that for example nvidia will fix their drivers just
> > because kde does n
On Monday 21 February 2011 22:11:23 Aaron J. Seigo wrote:
> On Sunday, February 20, 2011, Martin Gräßlin wrote:
> > What do you think about this idea?
>
> first, thumbs up for daring to ask the Big Questions. it's something i
> appreciate in you as a developer :)
>
> so ...personally, i'm ok with
On Sunday, February 20, 2011, Martin Gräßlin wrote:
> What do you think about this idea?
first, thumbs up for daring to ask the Big Questions. it's something i
appreciate in you as a developer :)
so ...personally, i'm ok with re-thinking the options in the kcm GUI, but i
feel that it is a very
On Monday 21 February 2011 20:51:40 you wrote:
> A Segunda, 21 de Fevereiro de 2011 18:55:25 Martin Gräßlin você escreveu:
> > On Monday 21 February 2011 12:55:48 Markus Slopianka wrote:
> > > Am Montag 21 Februar 2011, 07:24:33 schrieb Martin Gräßlin:
> > > > I don't want to remove the workaround,
A Segunda, 21 de Fevereiro de 2011 18:55:25 Martin Gräßlin você escreveu:
> On Monday 21 February 2011 12:55:48 Markus Slopianka wrote:
> > Am Montag 21 Februar 2011, 07:24:33 schrieb Martin Gräßlin:
> > > I don't want to remove the workaround, I only do not longer want to
> > > expose it in the UI
On Monday 21 February 2011 20:25:23 todd rme wrote:
> On Mon, Feb 21, 2011 at 11:35 AM, Martin Gräßlin wrote:
> > * improve situation with X devs - in whatever possible way (input
> > welcome)
> >
> > Thanks all
> > Martin
>
> If I am understanding what I am hearing correctly, kwin, gnome 3
> sh
On Mon, Feb 21, 2011 at 11:35 AM, Martin Gräßlin wrote:
> * improve situation with X devs - in whatever possible way (input welcome)
>
> Thanks all
> Martin
If I am understanding what I am hearing correctly, kwin, gnome 3
shell, unity, and to a lesser extent firefox are all doing basically
the sa
On Monday 21 February 2011 12:55:48 Markus Slopianka wrote:
> Am Montag 21 Februar 2011, 07:24:33 schrieb Martin Gräßlin:
> > I don't want to remove the workaround, I only do not longer want to
> > expose it in the UI. That's a big difference. And I really like Markus'
> > idea with the None compos
On Monday 21 February 2011 12:23:36 Sebastian Kügler wrote:
> Hey all,
>
>
> - let's try it in unreleased master for a bit
> - let's see how Unity and GNOME shell are received
> - let's try to improve communication with Xorg devs
> - let's target it for 4.8
>
Thanks all for the feedback, it help
A Segunda, 21 de Fevereiro de 2011 13:26:12 Sebastian Kügler você escreveu:
> On Monday, February 21, 2011 14:05:59 Nuno Pinheiro wrote:
> > A Segunda, 21 de Fevereiro de 2011 11:23:36 Sebastian Kügler você
escreveu:
> > >
> > > - let's try it in unreleased master for a bit
> > > - let's see how
Am Montag 21 Februar 2011, 14:24:42 schrieb Sebastian Kügler:
> I agree with Martin that the KWin KCMs could use a major redesign,
> shuffling options around is not enough and leads to confusion among users
> short-term, without tackling the real problem long term.
My side note was not the main p
On Monday, February 21, 2011 14:05:59 Nuno Pinheiro wrote:
> A Segunda, 21 de Fevereiro de 2011 11:23:36 Sebastian Kügler você escreveu:
> >
> > - let's try it in unreleased master for a bit
> > - let's see how Unity and GNOME shell are received
> > - let's try to improve communication with Xorg d
On Monday, February 21, 2011 12:55:48 Markus Slopianka wrote:
> Am Montag 21 Februar 2011, 07:24:33 schrieb Martin Gräßlin:
> > I don't want to remove the workaround, I only do not longer want to
> > expose it in the UI. That's a big difference. And I really like Markus'
> > idea with the None comp
A Segunda, 21 de Fevereiro de 2011 11:23:36 Sebastian Kügler você escreveu:
> Hey all,
>
>
> - let's try it in unreleased master for a bit
> - let's see how Unity and GNOME shell are received
> - let's try to improve communication with Xorg devs
> - let's target it for 4.8
>
wille I agrea with
Am Montag 21 Februar 2011, 07:24:33 schrieb Martin Gräßlin:
> I don't want to remove the workaround, I only do not longer want to expose
> it in the UI. That's a big difference. And I really like Markus' idea with
> the None compositing backend.
I took a few minutes of time to squeeze out a mocku
On Monday 21 February 2011, Sebastian Kügler wrote:
> Hey all,
>
>
> - let's try it in unreleased master for a bit
> - let's see how Unity and GNOME shell are received
> - let's try to improve communication with Xorg devs
> - let's target it for 4.8
>
i kept myself quite away from this but yeah
On Sunday 20 of February 2011, Martin Gräßlin wrote:
> Let's turn the question around: why should the user be able to enable or
> disable compositing?
Since, as experience shows, compositing is nowhere near a perfect world?
> What would be a valid reason to do so?
- Intel releases a new driver
Hey all,
- let's try it in unreleased master for a bit
- let's see how Unity and GNOME shell are received
- let's try to improve communication with Xorg devs
- let's target it for 4.8
On Sunday, February 20, 2011 15:38:22 Martin Gräßlin wrote:
> We have two categories of problems
> 1. Hardware
- Ursprüngliche Mitteilung -
> On Sun, Feb 20, 2011 at 4:40 PM, Martin Gräßlin
> wrote:
> > On Sunday 20 February 2011 22:32:47 Davide Bettio wrote:
> > > Hi,
> > >
> > > On 02/20/11 22:25, Martin Gräßlin wrote:
> > > > On Sunday 20 February 2011 22:18:16 Davide Bettio wrote:
> > > > > H
Am 20.02.2011, 22:06 Uhr, schrieb Martin Gräßlin :
> On Sunday 20 February 2011 22:00:58 Davide Bettio wrote:
>> I can't understand the point about removing enable/disable options.
>> if we don't want to give the user the possibility to disable, we don't
>> need an option to enable/disable.
we'l
On Sun, Feb 20, 2011 at 4:40 PM, Martin Gräßlin wrote:
> On Sunday 20 February 2011 22:32:47 Davide Bettio wrote:
>> Hi,
>>
>> On 02/20/11 22:25, Martin Gräßlin wrote:
>> > On Sunday 20 February 2011 22:18:16 Davide Bettio wrote:
>> >> Hi,
>> >>
>> >> On 02/20/11 22:06, Martin Gräßlin wrote:
>> >>
On Sunday 20 February 2011 22:50:01 Dario Freddi wrote:
> On Sunday 20 February 2011 13:38:40 Martin Gräßlin wrote:
> > Hi all,
> >
> > sending this to both Plasma and KWin as the idea affects the complete
> > workspace.
> >
> > Since 4.2 we have enabled OpenGL based compositing by default and I
On Sunday 20 February 2011 13:38:40 Martin Gräßlin wrote:
> Hi all,
>
> sending this to both Plasma and KWin as the idea affects the complete
> workspace.
>
> Since 4.2 we have enabled OpenGL based compositing by default and I was
> wondering if in 4.7 we should go the next step: disabling the po
On Sunday 20 February 2011 22:30:01 Beat Wolf wrote:
> Then leave it out during dev, but in when releasing.
I wrote that in my initial mail about the config option.
>
> I just don't agree that for example nvidia will fix their drivers just
> because kde does not work with some, probably older card
On Sunday 20 February 2011 22:32:47 Davide Bettio wrote:
> Hi,
>
> On 02/20/11 22:25, Martin Gräßlin wrote:
> > On Sunday 20 February 2011 22:18:16 Davide Bettio wrote:
> >> Hi,
> >>
> >> On 02/20/11 22:06, Martin Gräßlin wrote:
> I can't understand the point about removing enable/disable op
On Sunday 20 February 2011 22:00:58 Davide Bettio wrote:
> Hi,
>
> On 02/20/11 21:57, Martin Gräßlin wrote:
> > No, while the KCM sucks it will still suck after those three options
> > have been
> > removed. It needs a proper redesign, but that is out of the scope of this
> > thread ;-)
>
> I can
Hi,
On 02/20/11 22:25, Martin Gräßlin wrote:
> On Sunday 20 February 2011 22:18:16 Davide Bettio wrote:
>> Hi,
>>
>> On 02/20/11 22:06, Martin Gräßlin wrote:
I can't understand the point about removing enable/disable options.
>>> if we don't want to give the user the possibility to disable, w
Then leave it out during dev, but in when releasing.
I just don't agree that for example nvidia will fix their drivers just because
kde does not work with some, probably older cards.
But i know that i can't win that debate. But i just know that such a decision
will cause problems.
Am Sonntag, 2
Hi,
On 02/20/11 21:57, Martin Gräßlin wrote:
> No, while the KCM sucks it will still suck after those three options
> have been
> removed. It needs a proper redesign, but that is out of the scope of this
> thread ;-)
I can't understand the point about removing enable/disable options.
Bye,
Davide
On Sunday 20 February 2011 22:11:35 Beat Wolf wrote:
> On this computer, using the binary nvidia drivers, i could enable
> compositing. But due to some nvidia driver bugs, my computer becomes
> slugish very fast, which means compositing is not an option.
>
> i don't think that the x.org environmen
On this computer, using the binary nvidia drivers, i could enable compositing.
But due to some nvidia driver bugs, my computer becomes slugish very fast,
which means compositing is not an option.
i don't think that the x.org environment is stable enough to be able to remove
a option that lets y
Hi,
On 02/20/11 22:06, Martin Gräßlin wrote:
>> I can't understand the point about removing enable/disable options.
> if we don't want to give the user the possibility to disable, we don't need
> an
> option to enable/disable.
>
I don't see anything bad about having enable/disable options on the
On Sunday 20 February 2011 22:18:16 Davide Bettio wrote:
> Hi,
>
> On 02/20/11 22:06, Martin Gräßlin wrote:
> >> I can't understand the point about removing enable/disable options.
> >
> > if we don't want to give the user the possibility to disable, we don't
> > need an option to enable/disable.
On Sunday 20 February 2011 20:51:53 Davide Bettio wrote:
> Hi,
>
> On 02/20/11 13:38, Martin Gräßlin wrote:
> > Hi all,
> >
> > sending this to both Plasma and KWin as the idea affects the complete
> > workspace.
> >
> > Since 4.2 we have enabled OpenGL based compositing by default and I was
> >
Hi,
On 02/20/11 13:38, Martin Gräßlin wrote:
> Hi all,
>
> sending this to both Plasma and KWin as the idea affects the complete
> workspace.
>
> Since 4.2 we have enabled OpenGL based compositing by default and I was
> wondering if in 4.7 we should go the next step: disabling the possibility to
On Sunday 20 February 2011 18:18:41 Thomas Lübking wrote:
> Am 20.02.2011, 15:45 Uhr, schrieb Martin Gräßlin :
> > If we know that R100 does not support it, we could use the GLPlatform to
>
> w/o kms glxgears ran @200fps - that's not much, but might be enough. the
> problem seems that the driver o
Am 20.02.2011, 15:45 Uhr, schrieb Martin Gräßlin :
> If we know that R100 does not support it, we could use the GLPlatform to
w/o kms glxgears ran @200fps - that's not much, but might be enough. the
problem seems that the driver only provides GL 1.2 for the GPU - whether
for HW or SW limitatio
On Sunday 20 February 2011 14:52:16 Thomas Lübking wrote:
> Am 20.02.2011, 13:38 Uhr, schrieb Martin Gräßlin :
> > With Mesa 7.10 it seems that the driver problems (Mesa 7.8) which hit us
> > in
> > 4.5 are finally gone and our new compositor is performing much, much
> > better
> > than the one we
On Sunday 20 February 2011 15:12:58 Rohan Prabhu wrote:
> Hi,
> Having compositing enabled by default is good. Not allowing the user
> to switch it off is bad. Here are a few reasons why I think so:
>
> 1. Support does not mean performance: even though on some systems
> there would be enough suppo
On Sunday 20 February 2011 14:47:17 Markus Slopianka wrote:
> > Since 4.2 we have enabled OpenGL based compositing by default and I was
> > wondering if in 4.7 we should go the next step: disabling the possibility
> > to turn compositing off if supported.
> >
> > With Mesa 7.10 it seems that the d
Am 20.02.2011, 13:38 Uhr, schrieb Martin Gräßlin :
> With Mesa 7.10 it seems that the driver problems (Mesa 7.8) which hit us
> in
> 4.5 are finally gone and our new compositor is performing much, much
> better
> than the one we have in 4.6. This means from a performance perspective I
> am o
> Since 4.2 we have enabled OpenGL based compositing by default and I was
> wondering if in 4.7 we should go the next step: disabling the possibility
> to turn compositing off if supported.
>
> With Mesa 7.10 it seems that the driver problems (Mesa 7.8) which hit us in
> 4.5 are finally gone
> (..
Hi all,
sending this to both Plasma and KWin as the idea affects the complete
workspace.
Since 4.2 we have enabled OpenGL based compositing by default and I was
wondering if in 4.7 we should go the next step: disabling the possibility to
turn compositing off if supported.
With Mesa 7.10 it se
47 matches
Mail list logo
