Re: Meeting Minutes Published - July 25, 2010
- From: Bastien Nocera <hadess hadess net>
- To: Dave Neary <dneary gnome org>
- Cc: foundation-list gnome org
- Subject: Re: Meeting Minutes Published - July 25, 2010
- Date: Tue, 31 Aug 2010 14:36:56 +0100
On Thu, 2010-08-26 at 15:42 +0200, Dave Neary wrote:
> Bastien Nocera wrote:
> > This is what we've been told by the people we talked to. MeeGo 1.0 for
> > handsets uses a new compositor, with a new set of hints. Those are not
> > compatible with existing desktop implementations.
> > Trying to use a stock GTK+ or Qt application on MeeGo 1.0 for handsets
> > will result in a black screen.
> > Do you have any other information that contradicts that?
> After looking into it, I've been told that this is a bug in mcompositor,
> rather than a design issue: http://bugs.meego.com/show_bug.cgi?id=2953
> >>> o The board is considering funding making Maemo 6 integrate
> >>> more nicely with GTK+.
> >> In the context, it seems like the task should be "Ensuring that Maemo 5
> >> apps work well with upstream GTK+"?
> > The first step would be fixing the compositor and/or adding support for
> > this new compositor in GTK+ itself.
> > The second would be to start porting some of the Maemo 5 GTK+ and Hildon
> > features to GTK+.
> Yes, this certainly seems reasonable. But the bug in mcompositor seems
> sufficiently serious that it will have a high priority in mcompositor
> also (as mentioned in that bug report).
I'm checking now whether it's in fact the same problem, and whether we'd
need to fund fixing that bug, or whether it's a problem that MeeGo will
solve of its own.
] [Thread Prev