--===============26210719973459806==
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_ASI9+1DkoQajxrF";
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


--Boundary-02=_ASI9+1DkoQajxrF
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

Am Samstag, 21. Juni 2003 17:29 schrieb Henrique Pinto:
> That may be possible for some things. Having a plugin-aware framework wou=
ld
> allow us to have a common frontend "linked" to a distro(or OS) specific
> plugin as the backend. At the first run, the distribution would be
> identified and the correct plugin would be loaded.

Yes, distro-specific plugins were the first thing that=20
came to my mind, too.  But I think that even with a proper design=20
this is a tremendous task.

Christian.


--Boundary-02=_ASI9+1DkoQajxrF
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA+9ISAdKozh3+HUO4RAlnUAJ0ZAHdntGrz+KuAbioZCK3vPuqHqwCcDfHp
ioKqPtZPGU30ig5dpik8ZYI=
=0O60
-----END PGP SIGNATURE-----

--Boundary-02=_ASI9+1DkoQajxrF--


--===============26210719973459806==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============26210719973459806==--