GLib/GObject+C as the lingua franca? (was: kwallet and QCA)

Stefan Teleman stefan.teleman at gmail.com
Fri Jul 25 21:18:29 BST 2008


On Fri, Jul 25, 2008 at 3:42 PM, koos vriezen <koos.vriezen at gmail.com> wrote:

> No, because when we need something that uses another toolkit to play
> nicely in KDE, the dependencies should be as small as possible. Just a
> quick example:
> $ nm -D /usr/lib/libgtkmm-2.4.so.1.0.30 |grep ' T ' |wc -l
> 8932
> $ nm -D /usr/lib/libgtk-x11-2.0.so |grep ' T ' |wc -l
> 3535
> so almost a triple extra symbols to resolve at load time.
>
> Maybe some 'use Qt for every job' may dislike gtk or plain C in
> general, but a. they either have no clue what happening beneath it
> and/or b. are too stubborn to look over their horizon anyhow. Others
> will pick up the job.
> Btw. Vala is a nice alternative to get a nice OO language w/o extra
> dependencies (for as long as it takes of course)

Yes, and duplicating already existing work -- especially when backed
by the "too many symbols in shared library" argument --  is *always*
the best alternative. Even more so when said existing work does have
some successful history of being maintained, and being used in other
applications.

--Stefan

-- 
Stefan Teleman
KDE e.V.
stefan.teleman at gmail.com




More information about the kde-core-devel mailing list