[SCIM] Improved scim-panel-kde (about socket config)

[Cougar]

I think that's another solution, but in my opinion
KConfig is derived from QObject and depends on Qt
event loop, so I imagined it would be difficult (or
even impossible) to write a scim module based on
KConfig without a QApplication running in scim.

You are right, maybe I should make scim-panel-kde to
start scim automatically.

Or if users want to start input method when startx,
then 2 lines of commands will make no differences ;)
(I hope)

Cougar

--- James Su <suzhe at tsinghua.org.cn> wrote:
> Hmm,
>   It's a way, but not a good way. people always want
> to start scim with 
> only scim command. Starting scim-panel-kde before
> scim iteself is very 
> annoying for users.
>   I think the better way is writing a derived class
> of scim::ConfigBase 
> which using KConfig as the backend.  Then people can
> start scim with 
> just one command, like: scim -c kconfig -d
> 
> Regards
> James Su
> 
> Cougar :
> 
> >Hello everyone,
> >
> >Finally, I decided to "incoporate" KConfig into
> SCIM
> >like this: implement the config retrieving socket
> API
> >in scim-panel-kde and let scim use socket config
> (of
> >course I need to specify the socket address in
> >environmental vairable) to connect to
> scim-panel-kde
> >
> >now you can have a try like this:
> >scim-panel-kde -d (this must be started first)
>
>SCIM_CONFIG_SOCKET_ADDRESS="local:/tmp/scim-panel-socket"
> >scim -c socket -d
> >
> >scim will happily use what you are configured in
> >scim-panel-kde setup UI (though at present there
> are
> >few settings about SCIM itself, more will come)
> >
> >On the other hand, I found a potentional problem:
> the
> >first time, you ask SCIM to use socket config to
> >connect to scim-panel-kde, many settings are empty
> (do
> >not exist in kconfig files), but as long as the
> socket
> >config module connected to the server (in this case
> is
> >scim-panel-kde) and it can receive info from
> server,
> >it will think it can read the settings successfully
> so
> >do not fall back to the "default" value.
> >
> >I think it would be better to extend the socket
> config
> >API to specify whether it read something from the
> >config file (success) or just empty values (fail).
> >
> >At present, the work around is: at the first time
> you
> >decide to migrate into scim-panel-kde, to do this:
> >
> >echo "[SCIM]" >> ~/.kde/share/config/skimrc
> >cat ~/.scim/config.zh_CN* >>
> >~/.kde/share/config/skimrc
> >
> >Any suggestions and feedbacks are highly
> appreciated.
> >
> >Cougar
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> >http://mail.yahoo.com 
> >
> >_______________________________________________
> >scim mailing list
> >scim at freedesktop.org
> >http://freedesktop.org/mailman/listinfo/scim
> >
> >  
> >
> 
> 
> 
> _______________________________________________
> scim mailing list
> scim at freedesktop.org
> http://freedesktop.org/mailman/listinfo/scim



	
		
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/