Re: Re: kde plasma workspace structure

2012-06-09 Thread Martin Gräßlin
On Saturday 09 June 2012 16:29:10 Aaron J. Seigo wrote: > On Saturday, June 9, 2012 14:13:49 Martin Gräßlin wrote: > > On Saturday 09 June 2012 13:18:04 Aaron J. Seigo wrote: > > > On Saturday, June 9, 2012 12:37:47 Martin Gräßlin wrote: > > > > There might be a misunderstanding. I do not say that

Re: Re: kde plasma workspace structure

2012-06-09 Thread Martin Gräßlin
On Saturday 09 June 2012 13:18:04 Aaron J. Seigo wrote: > On Saturday, June 9, 2012 12:37:47 Martin Gräßlin wrote: > > There might be a misunderstanding. I do not say that we have to require > > OpenGL compositing, I'm saying that the stack underneath us broke for the > > non composited case (eithe

Re: Re: kde plasma workspace structure

2012-06-09 Thread Alex Fiestas
On Sat, Jun 9, 2012 at 12:37 PM, Martin Gräßlin wrote: > Also from looking at the KWin source base I have to disagree about the > benefits of keeping code portable. It makes the code ugly, adds additional > ifdefs. Keeping the source compiled with different compiles is a good thing, > that's why I

Re: Re: kde plasma workspace structure

2012-06-09 Thread Martin Gräßlin
On Saturday 09 June 2012 11:13:16 Aaron J. Seigo wrote: > On Saturday, June 9, 2012 10:28:05 Martin Gräßlin wrote: > > On Saturday 09 June 2012 04:45:51 Aaron J. Seigo wrote: > > > * losing portability to non-Linux (and even specific Linux OSes) > > > > something I would like to discuss in the ligh

Re: Re: kde plasma workspace structure

2012-06-09 Thread Martin Gräßlin
On Saturday 09 June 2012 04:45:51 Aaron J. Seigo wrote: > * losing portability to non-Linux (and even specific Linux OSes) something I would like to discuss in the light of workspace. I think we all agree that we do neither target MS Windows nor OS X. (I know you can run plasma-desktop on Windows