Re: [pygtk] Simple TreeView API
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. As a GTK 1.2/2.x and PyGtk 0.6/2.x programmer, I think it's worse than that. I think the problem about the list widget lies in Gtk, not in PyGtk. Once upon a time was the CList widget. It was limited but simple and practical, and suited many needs. Using it, it was simple to do simple things, it was moderately complicated to do moderately complicated things, and it was impossible to do complicated things. Now the Gtk developers decided CList is deprecated, and want to replace it with TreeView. Unfortunately using the TreeView is overly complicated even to do simple things. PyGtk simply mirrors the Gtk API, and I see nothing wrong with this. One would expect to see an abstraction layer *within* pygtk, that's the point as for me. Beware: it should be a temporary replacement solution until Gtk developers understand this problem and provide a simple CList-like widget. Since /me alone doesn't have enought weight to speak to Gtk developers about this, I'm still looking for people with the same/approaching point of view and enough influence... But I think this would be The Right Way to go. -- Best regards, Fabien ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Simple TreeView API
On Thu, 2004-10-07 at 13:46 +0200, Fabien COUTANT wrote: As a GTK 1.2/2.x and PyGtk 0.6/2.x programmer, I think it's worse than that. I think the problem about the list widget lies in Gtk, not in PyGtk. Once upon a time was the CList widget. It was limited but simple and practical, and suited many needs. Using it, it was simple to do simple things, it was moderately complicated to do moderately complicated things, and it was impossible to do complicated things. You should have done some support on irc about that. gtkclist caused an enormous amount of questions, noise and annoyances. Regards, Xavier Ordoquy. -- Complexity has nothing to do with intelligence. Simplicity does. (Larry Bossidy, CEO, Allied Signal) ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Simple TreeView API
On Tue, 2004-10-05 at 11:51 +1300, [EMAIL PROTECTED] wrote: some feedback on the API itself at this stage would be really helpful. ANY feedback would be helpful. I know everyone has done similar stuff before; I'm just trying to make it super-simple. I can take criticism, really. ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Simple TreeView API
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. One would expect to see an abstraction layer *within* pygtk, that's the point as for me. rob ___ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
Re: [pygtk] Simple TreeView API
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/
