Hi, The idea is to move the compose file reading code out of Qt. libxkbcommon 5.0 (released on 2014-10-18 [1]) added support for the compose keys. I did look at the new API already in October [2]. It should be simple enough to remove the table generation code and use xkbcommon's API instead. I have not done any benchmarking because I never got around to finishing that patch.
There are several projects that use xkbcommon (Wayland, GTK), so we can benefit from the optimizations done by others if we use this new API. Also if somebody has suggestions for improvements, those should be done in [3]. [1] http://lists.freedesktop.org/archives/wayland-devel/2014-October/017836.html [2] *WIP* https://codereview.qt-project.org/#/c/98062/ [3] https://github.com/xkbcommon/libxkbcommon ________________________________________ From: development-bounces+gatis.paeglis=theqtcompany....@qt-project.org <development-bounces+gatis.paeglis=theqtcompany....@qt-project.org> on behalf of Thiago Macieira <thiago.macie...@intel.com> Sent: Monday, January 19, 2015 9:38 PM To: development@qt-project.org Subject: Re: [Development] optimizing QComposeInputContext / TableGenerator? On Monday 19 January 2015 21:17:00 Giuseppe D'Angelo wrote: > > The best approach of course would be to have a OpenDesktop standard that > > allows mmapping the compose table in and using it from there. Probably not > > feasible. > > Why not? x...@freedesktop.org. I think I can easily convince the EFL folks for this. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development