Quoting Roberto Cavada <[EMAIL PROTECTED]>: > On Wed, 2004-10-06 at 23:10 +1300, John C Barstow wrote: > > ANY feedback would be helpful > > I have no technical feedback to provide, actually. > Anyway, I want to stress that those who I talk about pygtk will always > complain about the convolution of tree/list widgets it provides. > Powerful, elegant, clever and whatever, but too complicated to begin > with.
Right, that's what I'm trying to address. You'll notice in the sample I provided there is no mention of models, iters, or TreeViewColumns. Instead, I have a widget model where you provide a list of objects, modify the list and call refresh, and get the selected object(s) directly. Not nearly as powerful but hopefully far simpler. > One would expect to see an abstraction layer *within* pygtk, that's the > point as for me. > rob If I can make some minor modifications (pixbuf columns, multi-select, and a way to handle trees) and people are generally, I'd be trying to get this incorporated into pygtk, even if just in some off-beat namespace. I think - and here is where feedback can tell me if I'm on the right track - that this is desperately needed and reasonably useful. _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
