Default args for KParts

Ian Reinhart Geiser ian at geiseri.com
Fri Apr 30 13:46:10 BST 2004


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

Greetings,
	I have been trying to solve the issue with chainloading KParts for my PyQt 
and KJSEmbed kpartsproxy parts.  The goal of these is that I can create a 
KPart in PyQt or KJSEmbed.  In the past I have been abusing Libtool's la 
files, but this is a horrible solution imho.

	The solution I propose is in the patch as follows.  It involves adding the 
concept of default arguments to a kpart.  By adding a list of args in the 
"X-KDE-DefaultArgs" entry in a service's desktop file, you can have these 
args prepended to the kparts args that are passed into the part from the 
componentFactory's createInstanceFromService(...) functions.

	This would allow me to then give things like the script name for the kpart I 
want the proxy to load.

	My questions here:
	Is there a better way to do this?
	Is the solution I proposed useful outside of chainloading parts?

Cheers
	-ian reinhart geiser
- -- 
- --:Ian Reinhart Geiser <geiseri at yahoo.com>
- --:Public Key: http://geiseri.myip.org/~geiseri/publickey.asc
- --:Public Calender: http://geiseri.myip.org/~geiseri/publicevents.ics
- --:Jabber: geiseri at geiseri.myip.org
- --:Be an optimist -- at least until they start moving animals in 
- --:   pairs to Cape Canaveral. ~ Source Unknown
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAkkqXPy62TRm8dvgRAjxcAKDgcZ7UDBaci1cSCuCaK6qM03WmqACggxRi
3svySIQ4rkkPZrksgFfMazw=
=pJfr
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kparts_with_args.patch
Type: text/x-diff
Size: 3564 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040430/518671f9/attachment.patch>


More information about the kde-core-devel mailing list