Improve ibus in order to replace scim
As we have a lot of problems with scim, we need to look for alternatives. One alternative is ibus. However, it needs some improvements to become a full replacement for scim.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
2008-12-23 pitti:
- Rationale: Please give an example where ibus is specifically better than scim
- Please be more verbose in use cases; just enumerating keyboard layouts does not help to understand what the user wants to do
- assumptions: is i-bus compatible to scim wrt. existing configuration files, and use cases? can this be resolved? assumptions settings is not meant for things which still need to be researched; rather for assumed user behaviour; just drop the section completely if you don't need it
- "add on-screen keyboard for mobile devices " -> uses an existing implementation? which? how is this enabled/triggered?
- "improve hotkey configuration for the IMEs" -> how? what's currently bad with them?
- "port the code from python to C" -> rationale?
- "need frontend for KDE (probably not in Jaunty)" -> please split this out to a separate spec for KDE then, if it's sufficiently indepentent work from GNOME side
2009-12-04 pitti: how did ibus turn out in karmic so far? any feedback? do we need to adjust the list above?
