Re: Building multiple backends on on same system

On Mon, 2010-12-06 at 15:16 -0500, Behdad Esfahbod wrote:
> On 12/06/10 13:46, Alexander Larsson wrote:
> > On Mon, 2010-12-06 at 12:53 -0500, Behdad Esfahbod wrote:
> >> On 12/05/10 17:14, Alexander Larsson wrote:
> >>> Then we add a GdkBackend type that each backend implements. This is a
> >>> singleton created at init to hang global stuff off. Its also useful for
> >>> backend specific code.
> >>
> >> Would it be possible to allow multiple backends at runtime?  Imagine, moving
> >> your app currently running on your desktop to running on broadway without
> >> restarting it...
> > 
> > I think it will be kinda hard. It will require passing a GdkBackend to
> > all global gdk functions, which is a huge API break.
> Or have a push/pop gdk_backend...

As benjamin said, most of these functions should already be backend
agnostic or have a display/screen/whatnot argument that we can vtable
on. Not having that is just "wrong". (Of course, fixing that is a
general API break.) So introducing a public gdk_backend_xxx set of calls
makes it harder to fix this properly later.

 Alexander Larsson                                            Red Hat, Inc 
       alexl redhat com            alexander larsson gmail com 
He's a Nobel prize-winning one-eyed paranormal investigator fleeing from a 
secret government programme. She's a mistrustful snooty opera singer prone to 
fits of savage, blood-crazed rage. They fight crime! 

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]