[PyKDE] Opinions on pyuic Custom Widget Support

Kaleb Pederson kibab at icehouse.net
Sat Dec 14 16:10:01 GMT 2002

Hash: SHA1

I don't have a better suggestion at the time. The way it currently works is 
very intuitive.  Without looking through the documentation, I assumed that it 
would work that way and when I added custom widgets to my programs everything 
just "worked".  I haven't recently played with uic so I don't remember what 
it does nor how the two compare.

I like the idea of the new way providing more flexibility, however, as I have 
been considering changing some of my naming conventions.

If the change is made, as long as it is well documented, it shouldn't be a 

- --Kaleb

On Saturday 14 December 2002 03:10 am, Phil Thompson wrote:
> I've been prompted to look at improving pyuic's support for custom widgets.
> At the moment, if you use a custom widget, pyuic will generate the
> following at the start of the module...
> from modname import widgetname
> ...where "widgetname" is the class name of the custom widget - no problem
> there. "modname" is the value entered in the Headerfile field of the Edit
> Custom Widgets dialog with the .h extension removed. While this works, I'm
> told it isn't particularly useful. It also makes dubious assumptions about
> how custom widgets have been packaged into modules and make it less easy to
> satisfy both uic and pyuic.
> I propose to remove this behaviour.
> A more generic, think about it for 2 minutes, solution is to allow Python
> code to be embedded in the Comment field of the Form Settings dialog. Any
> line beginning with "Python:" will be copied to the generated module. This
> is then completely flexible.
> Before I go ahead and implement this, does anybody have any better
> suggestions? Or additional things that could be done for common cases (like
> support for PyKDE widgets).
> Phil
> _______________________________________________
> PyKDE mailing list    PyKDE at mats.gmd.de
> http://mats.gmd.de/mailman/listinfo/pykde
Version: GnuPG v1.0.7 (GNU/Linux)


More information about the PyQt mailing list