[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Plugin tutorial request
From:       Benjamin Meyer <ben () meyerhome ! net>
Date:       2004-02-19 4:27:13
Message-ID: 200402182327.16065.ben () meyerhome ! net
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Many applications these days (too many?, different thread please) have or will 
have a plugin system.  There is this doc:

http://developer.kde.org/documentation/tutorials/dot/writing-plugins.html

but it really has to do with writing kpart plugins and not about generic 
plugin systesms.  I have written a few different plugin systems in the past 
few years, each one different (and better).  And in the same time come across 
several dozen more.  No doubt code is unnecessarily being duplicated all over 
the place and sub optimal or just flat out wrong choices are being made in 
the design of these plugin systems.  It would probably be worth while to put 
together a document describing all of the best practices for creating a 
plugin system.  What modules in KDE that already exist that developers can 
take advantage of, how to manage versioning, the build system, etc.  I know 
that many KDE developers have worked on plugin systems before and would 
probably be able to add in a good point or two.  This way the same lessons 
don't have to be relearned

- -Benjamin Meyer

- -- 
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFANDsj1rZ3LTw38vIRAtwtAJ9emNJROH87a0l0xfZ6nTIxVm5pBQCeOcuA
8W/yFwdx66BPSd/TA70hWhk=
=qN74
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]