Re: [PyKDE] The thingie that makes your user interfaces....

[Torsten Marek]

Hello again,

I created a new release (0.2.1, same place as yesterday) showing two techniques
of putting implementations and UI files together.

The first one uses some deeper Python magic to create types on the fly and what
not. A lot of implicit stuff and some restraints (?) like not having to call the
base class constructor. Furthermore, you inherit from PyQtUI but this is not
your base class at all.

The second one is more typing on the user side and you need to make sure that
you inherit the correct base class and call your base class constructor, but
it's more obvious what happens.

Preferences, anybody?
Although I like the dark stuff happing in (1), I'd go for (2).

greetings

Torsten
--
Torsten Marek <[EMAIL PROTECTED]>
ID: A244C858 -- FP: 1902 0002 5DFC 856B F146  894C 7CC5 451E A244 C858
Keyserver: subkeys.pgp.net

formimpl1.py
Description: application/python

formimpl2.py
Description: application/python

ImplTest1 ImplTest1 0 0 186 140 ImplTest1 unnamed pushButton1 Click this! pushButton1 clicked() ImplTest1 ok() ok()

signature.asc
Description: OpenPGP digital signature

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde