Scim-bridge is yet another gtk-immodule for SCIM. You can use this to avoid the problem caused by C++ ABI transition.
Scim-bridge is yet another gtk-immodule for SCIM.It communicates with scim over sockets,
and the DLL loaded by applications is written in pure C (for now).
You can use this to avoid the problem caused by C++ ABI transition.
Scim-bridge is currently released as 0.2.0. All the functions have been implemented enough for daily usage.
There is only gtk client for now, but we have plan to make both qt client and console client at last.
How does it works
Scim-bridge consists of two parts, that is, client and agent (server).
The client is a GTK immodule (for now), which communicates with the agent over sockets.
The agent communicates with SCIM, and bring back the data for each client.
Accordingly, the applications become dependent from SCIM if you use scim-bridge.
This is why scim-bridge solves the problem caused by C++ ABI transition.
Why don't you have two scim-libs for both C++ ABI?
Of course, you can build scim-libs against both new and old C++ ABI, and launch the one as a server then use it over the socket from the other.
But this will become *VERY* tiring and troublesome work for maintainers or packagers. Judging from our experiences, it won't pay. :(
Where can I get it?
You can get it from SCIM project page at sourceforge.net. Have fun!