Spell Checking in KDE4 (KSpell2)

Thiago Macieira thiago at kde.org
Wed Apr 27 02:44:52 BST 2005


heiko.evermann at gmx.de wrote:
>> But basically the requirement on
>> my part is very simple and is "Enchant can't be linking to Glib when
>> running from KDE apps". From what I remember it was using only the
>> GModule and codecs from Glib so I guess we could write small wrapper
>> classes like ETextCodec and EModule that would be implemented both
>> with Qt/KDE and Glib/GNOME specific functions and the right
>> implementation would be a ./configure option.
>
>What is the problem with Glib? Isn't GLib some kind of standard library?

No. It's not standard. It might become standard some day if its 
functionalities are merged into glibc. But this will affect only 
glibc-based systems (i.e., Linux). Other platforms will still need an 
external library.

Think of glib as Qt4's QtCore and mostly like STL. The functionality it 
provides is already in Qt, like containers (arrays, hash tables, etc.), 
date manipulation, string manipulation, filesystem operations, thread 
handling, etc, as well as an event loop. So, we don't need it.

-- 
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

1. On frumscafte, hwonne time_t wæs náht, se scieppend þone circolwyrde 
wundorcræftlíge cennede and seo eorðe wæs idel and hit wæs gód.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050426/8491e15a/attachment.sig>


More information about the kde-core-devel mailing list