gnash-commit
[Top][All Lists]
Advanced

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

Re: [Gnash-commit] /srv/bzr/gnash/trunk r12341: Refactored input device


From: Benjamin Wolsey
Subject: Re: [Gnash-commit] /srv/bzr/gnash/trunk r12341: Refactored input device support for the framebuffer GUI.
Date: Fri, 30 Jul 2010 15:23:44 +0200

>   I have had some thoughts about using both the Touchscreen with GTK on
> X11, so currently they all get built in gui if you select the FB GUI.
> I'm also not sure if if would be better to use the input event devices
> (/dev/input/*) with GTK than using the glib functions for this.

Surely not! Using the library functions is by far the easiest way for
compatibility and reliability.

> > If the FB GUI is disabled, the other GUIs build fine without the extra
> > code building.
> 
>   Which is the important part. :-) Most people don't build the FB GUI.

I think it would be best to allow building the FB gui without it
affecting the other GUIs. Even when configure is fixed to detect my
missing tslib, enabling one GUI shouldn't affect the way the others are
built.

> > There are also many warnings that point to bugs in the code, and fixing
> > the warnings would be easier than waiting for bug reports!
> 
>   Most of "the code" already existed in a poor state, so many of those
> warnings are inherited. Most of what I've done is just rearrange which
> file code lives in. I assume you never built the fb gui, so didn't
> notice.

I always did, and there were no warnings. That's not to say it was in a
good state before, but it was entirely warning-free.

bwy

--
The current release of Gnash is 0.8.7
http://www.gnu.org/software/gnash/

Benjamin Wolsey, Software Developer - http://benjaminwolsey.de
C++ and Open-Source Flash blog - http://www.benjaminwolsey.de/bwysblog

xmpp:address@hidden
http://identi.ca/bwy

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


reply via email to

[Prev in Thread] Current Thread [Next in Thread]