--nextPart1511855.Bao2SlEEpP
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

heiko.evermann@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=20
functionalities are merged into glibc. But this will affect only=20
glibc-based systems (i.e., Linux). Other platforms will still need an=20
external library.

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

=2D-=20
  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=E6s n=E1ht, se scieppend =FEone circolwyr=
de=20
wundorcr=E6ftl=EDge cennede and seo eor=F0e w=E6s idel and hit w=E6s g=F3d.

--nextPart1511855.Bao2SlEEpP
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCbu6dM/XwBW70U1gRAlYYAJ0f6YJaZxhnv/mPYhNNZJIOT2hezQCgkIpU
SLTjRLtnAg1x/fBDIw6Pztc=
=AKWv
-----END PGP SIGNATURE-----

--nextPart1511855.Bao2SlEEpP--