On Wed, 2005-09-21 at 10:32 +0200, Alessandro Ferrarin wrote:
> Il lun, 2005-09-19 alle 17:10, Gustavo J. A. M. Carneiro ha scritto:
>
> > http://telecom.inescporto.pt/~gjc/higcontainer.py
> >
> > Caveat: needs pygtk 2.8
>
> Unfortunately, I'm using pygtk 2.3
> Waiting the upgrade...
>
> I'll use this solution (ugly but functional): sit down, please...
>
> suppose NewWidget is a new real gtk.Widget (that extends a gtk.Widget).
> I define inside of it the methods to update and manage outside defined
> widgets which instantiations are passed at the __init of my NewWidget.
>
> This let me hide functionality inside the pseudo class. I've no
> choices: is this really terrible?
Not at all. You don't need a _real_ widget unless:
1. You want to add signals and/or properties;
2. You want to integrate with Gazpacho (making it appear in a custom
pallete);
3. You want custom theming per widget class;
4. ... probably other reasons I don't remember ...
Regards.
>
> Thanks for your kind answers!
--
Gustavo J. A. M. Carneiro
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
The universe is always one step beyond logic.
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
