Re: Doubts about GPeriodic
- From: Paul Davis <paul linuxaudiosystems com>
- To: Havoc Pennington <hp pobox com>
- Cc: Ryan Lortie <desrt desrt ca>, Owen Taylor <otaylor redhat com>, gtk-devel-list gnome org
- Subject: Re: Doubts about GPeriodic
- Date: Fri, 22 Oct 2010 21:56:13 -0400
On Fri, Oct 22, 2010 at 5:16 PM, Havoc Pennington <hp pobox com> wrote:
> Right - Miguel pointed out to me (unrelated to this thread) that Mac
> and Windows both work this way these days,
wayland too, as far as i understand
>and I'd already been
> noticing that Chrome, new Pepper plugin API, lightspark, and probably
> other stuff all seem to be moving to a "build a stack of
> software-rendered layers then use GL to squish them" model. So
> building a bunch of layers (ideally in threads) then GL-compositing
> the layers (with optional transformations and shaders) seems to be
> kind of the thing to do these days. You can animate the layers and
> shaders totally in the GL thread without mixing up with the app code.
> It seems like a big hairy change though. I definitely haven't taken
> the time to start working it out.
to me, it seems *really* pointless to go halfway here. its abundantly
clear what the right design is, so why put a bunch of effort into
cooking up a half-cooked solution that will still need to discarded
for real future?
you guys are working out an incredibly complex and potentially baroque
solution when the elegant and arguably "correct" one has already been
implemented several times in different contexts. what's the point?
] [Thread Prev