hello, I'm one of contributer of fcitx. I just go throught all your code.Actually fcitx has provide a library for it's own config file parse and write, I think you don't need to hard code all configure option.
Maybe you can check fcitx-configtool on fcitx.googlecode.com, it's written with gtk, but still you can check how it read config files. It just parse all the configuration option from a configure description file and "generate" the ui, this will be more flexible because if upstream change the option, you can still use this tool without any problem.
If you have further intention about this tool, maybe we can have some further discussion. Just join fcitx-dev@googlegroups.com
Ratings & Comments
1 Comment
hello, I'm one of contributer of fcitx. I just go throught all your code.Actually fcitx has provide a library for it's own config file parse and write, I think you don't need to hard code all configure option. Maybe you can check fcitx-configtool on fcitx.googlecode.com, it's written with gtk, but still you can check how it read config files. It just parse all the configuration option from a configure description file and "generate" the ui, this will be more flexible because if upstream change the option, you can still use this tool without any problem. If you have further intention about this tool, maybe we can have some further discussion. Just join fcitx-dev@googlegroups.com