Hi,

On Sun, 2008-11-23 at 20:31 +0300, Paul Fertser wrote:
> Hi,
> 
> Sebastian Ohl <[EMAIL PROTECTED]> writes:
> >> first: if you don't like it, just don't use it .. ;)
> > second: everyone who want's to used the software should do it! And we 
> > are always open for suggestions or patches to improve it! (the "first"
> > sounded so hard....)
> 
> So, my suggestion is: if you don't like the default FSO rules file
> (i.e. buttons handling and brightness handling) you should disable it
> on installation or (imo better) you should ask the user whether he
> prefers handling by oeventsd or by o-p-p.
> 
> [snip]
> > it is. i don't understand you problem with the keyboard in your
> > mail.
> 
> I wanted to type some russian so i had to start another instance of
> matchbox-keyboard with ru layout. So i did. But then pressing the
> keyboard button killed the keyboard instead of opening another one
> with english layout. It seems it can be useful to sometimes have two
> keyboards opened at once. So, it wasn't a real problem, but rather an
> illustration to why i think that panel-plugin shouldn't be a launcher.
yes i see your problem. calling the keyboard via a shell is not the best
solution. when i wrote this code, i was very new to python, so it was
the easiest thing to do. the right one is to do a fork and then an exec.
so we would only kill the binary that has been started by the panel. i
hope i'll find time to alter this piece of code. but our first concern
is the conversion to a plugin architecture. 

btw: please respond to the list not to me in person(i quoted your
complete message to inform the others).

regards
 sebastian


_______________________________________________
Smartphones-userland mailing list
Smartphones-userland@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland

Reply via email to