Hi,
> Great - I've moved it over to the wiki so that others can contribute:
> http://maemo.org/maemowiki/InputMethod
This is looking great.
I have a couple of suggestions.
* In the case the application input window cannot be resized,
e.g. in games, you might not want to have the window resized.
Then it's better to have the keyboard as a non-modal, movable,
dialog that's above the application window, either:
- above everything (i.e. not trancient to anything) if it's generic
input method, or
- trancient to that specific window, if the keyboard is intended only
for that particular application
* In case you have an application specific keyboard and the application
accepts / needs to accept only ASCII, you don't need to use the Gtk
/ Maemo IM framework, you can use just XTest extension to inject
key events to to the focused window. See xkbd, matchbox-keyboard,
and:
http://maemo.org/pipermail/maemo-developers/2006-February/003081.html
* In case you want to integrate things into the Gtk IM framework,
I think it would help reading about the Gtk IM context from the Gtk
documents, e.g. what kind of (Glib) signals the input method modules
use to communicate with the widgets.
- Eero
_______________________________________________
maemo-developers mailing list
[email protected]
https://maemo.org/mailman/listinfo/maemo-developers
