Re: [matchbox] Merge openmoko-keyboard changes

Hi,
(restoring cc)

On Wed, 13 Jun 2007 20:59:23 +0100
Matthew Allum <mallum@...> wrote:

> On Wed, 2007-06-13 at 21:34 +0200, Daniel Willmann wrote:
> > First I would like to give a short overview about the changes made
> > and why we need them.
> > 
> > 1) Functions to set/get a background image
> > 2) Functions to set an image for the background of the keys (normal
> > and pushed)
> 
> Both are needed/good, though I would say one thing to remember is that
> you cant guarantee/fix the size of keys nor the keyboard itself.

Yeah, I'll need to remove some "realsize" features in there

> Therefor;
> 
>   - Idealy the background image should scale or tile. (being clipped
> if larger than keyboard window size)

Tiling/scaling should probably be configurable.

>  -  The keys are probably best made up by have a series of tiles that 
>     make up the keys - e.g 4 corner images, 4 edge images (which are 
>     again tiled or scaled) and finally a center image (also 
>     tiled/scaled).

Merge openmoko-keyboard changes

Hi,

I am trying to merge the changes made in openmoko-keyboard back to
matchbox-keyboard so we can avoid a maintenance hell along the road.
First I would like to give a short overview about the changes made and
why we need them.
Please tell me if/under which conditions it is possible to get them
merged upstream.

1) Functions to set/get a background image
2) Functions to set an image for the background of the keys (normal and
pushed)
3) We currently have some special buttons (see
http://wiki.openmoko.org/wiki/Input_Method#Appearance_.26_Interaction )
that switch the layout of the keyboard around. Of course having a
separate layout for caps is silly, but it is for example useful to
display a numpad. If you have a better way of doing this please let me
know.
4) The layout switching would be implemented like this:
<layout id="foo">
With corresponding keys that trigger the layout being:
<key>
  <default display="F" action="layout:foo"/>
</key>

Regards,
Daniel Willmann

GPE 3.0

 Hello,

 I am French Engineer in Informatics and I would want to build a start
 up to  manufacture mobile phones ( OEM level ). I am currently in discussion 
with investors.

We would want to use the GPE environment but we will need to complete it to 
have a "commercial grade" one.

Here are our goals :

Finish this :

http://handhelds.org/moin/moin.cgi/GpeThingsTodo

Mail : sylpheeds UI to 240*320

+

Porting Gpe to use ALSA.

Porting Matchbox to use AIGLX .

Porting Gpe-mini-browser to use Webkit.

Mini-Totem with GStreamer Backend ( 320*240 ).

Using Kaffe as JVM

We believe that we will be able to speak of GPE 3.0. :) 

errors making matchbox

I am trying to build matchbox from svn source.

I get the following error when I execute the mactchbox.autobuild.sh

colinux:$ ./matchbox-autobuild.sh
Now building "libmatchbox"
ipkg deps are xlibs,libjpeg62
~/matchbox/libmatchbox ~/matchbox
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
aclocal:configure.ac:319: warning: macro `AM_PATH_CHECK' not found in library
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy --no-force
libmb/Makefile.am:23: Libtool library used but `LIBTOOL' is undefined
libmb/Makefile.am:23:
libmb/Makefile.am:23: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
libmb/Makefile.am:23: to `configure.ac' and run `aclocal' and `autoconf' again.
autoreconf: automake failed with exit status: 1

I am building this under CoLinux.
I have the follow version of tools.

CoLinux 6.3
automake (GNU automake) 1.9
autoconf (GNU Autoconf) 2.59
aclocal (GNU automake) 1.9

What about Matchbox and Xinerama ?

Hello ,

I would like to use Matchbox on a dual LCD screen Arm device ( not yet
developed , perharps my study case could help also for the dslinux
project ? ) . For the moment , i use Xnest to emulate and build the User
environment . The +xinerama argument of Xnest clone the window and not
provide a real independant window ( i dont find relevant information
about that ). Any feed back about experience with matchbox and xinerama
will be apprecied . Where the support should be add if this it's not
done ? I think in matchbox-window-manager to choose if maximize should
be done on the 2 screens ( for an application that can split itself the
screen , like firefox Split screen extention for example ) or only one
screen , in the matchbox-panel too.

Greets , Ronan. 

--
To unsubscribe send a mail to matchbox+unsubscribe <at> o-hand.com
--

Iconized keyboard

Matchbox-keyboard has serious bug in familiar-0.8.4-rc2 or any version.

Hi,

Turn on Caps-lock key, when run Matchbox-keyboard,
type "Q", then it print "q" in the x-terminal or gedit,
type "W", then it print "w",
type "E", then it print "E",
type "R", then it print "r", ..  so on.

But this bug didn't happened with xkbd!

--
Park Ji Wong
--
To unsubscribe send a mail to matchbox+unsubscribe <at> o-hand.com
--

I made hangul support for Matchbox-keyboard

Hi,

I modified the source code of matchbox-keyboard to enable Hangul.
Where to code submit?

Thanks in advance.
--
To unsubscribe send a mail to matchbox+unsubscribe <at> o-hand.com
--

Different colormode between matchbox and X apps

Hello,

I am trying to make a demo based on a GPE / Familiar 0.8.3 snapshot image.

My framebuffer driver has a BGRA mode (instead of the more common RGB or
RGBA modes). While all X applications that I run (mainly GPE apps) are
displayed with correct colors, matchbox-window-manager and
matchbox-desktop are using a different colorset, displaying desktop
icons and windows decorations with wrong colors (see
http://free-electrons.com/issues/matchbox-apr1-2006/screen.jpg).

So, it seems that Matchbox is considering my framebuffer as RGB instead
of BGR. Is matchbox trying to get a private colormap, instead of using
the default one from X?

I checked the command line options for matchbox-window-manager and
matchbox-desktop, but didn't find anything about the colormap...

Here are the versions I'm using.

matchbox-applet-inputmanager - 0.6-r0 -
matchbox-common - 0.9.1-r0 -
matchbox-desktop - 0.9.1-r0 -
matchbox-panel-hacks - 0.3-1-r4 -
matchbox-panel-manager - 0.1-r0 -
matchbox-themes-gtk - 1.0-r0 -
matchbox-wm - 0.9.5+cvs-20051212-r1 -

Any hint for having the desktop and window decoration colors displayed
in a correct way?

    Thanks in advance,

    Cheers,

    Michael.

--

-- 
Michael Opdenacker, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training

--
To unsubscribe send a mail to matchbox+unsubscribe <at> o-hand.com
--

Re: [Fwd: Re: [maemo-developers] J2ME on Nokia 770]

Tapani Pälli wrote:

>>>>Thanks,
>>>>Philippe
>>>>  
>>>>        
>>>>
>>>What kind of problems are you actually having right now? If it's Java
>>>querying default pixmap depth you can workaround it by using different
>>>method, you can take the colordepth from rootwindow for example.
>>> 
>>>
>>>      
>>>
>>It's not the main problem
>>
>>RedHat is very interested in solving this. See the issue tracker at:
>>http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26812
>>
>>    
>>
>
>You could note to the bug that Matchbox has nothing todo with this bug.
>You can reproduce it with any window-manager, so you don't need Matchbox
>for debugging this.
>  
>

No Redhat thinks it's in a gtk problem:

 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26812

http://bugzilla.gnome.org/show_bug.cgi?id=335880

--
To unsubscribe send a mail to matchbox+unsubscribe <at> o-hand.com
--

Matchbox WM 1.0 Released

Read all about it here;

http://projects.o-hand.com/matchbox/?p=12

  -- Matthew

--
To unsubscribe send a mail to matchbox+unsubscribe <at> o-hand.com
--