Just thinking about why it might be considered bad to have a bunch of buttons in your TreeView...
>From the GNOME HIG, http://developer.gnome.org/projects/gup/hig/2.0/principles-simplicity.html > don't clutter your interface, and don't overload the user with > buttons, menu options, icons, or irrelevant information. There is a clear theme through the document of buttons being something that you only ever have one or two of in any given window. For example: > > Additional Buttons > > You can include other buttons in a dialog's main button area in > addition to the affirmative button and Cancel, but any more than one > or two such buttons will make the dialog appear complicated and > difficult to use. As with any other button, keep the labels as concise > as possible to minimize this effect. > Maybe that helps? Cheers JP Alessandro Ferrarin wrote: >Il mar, 2006-01-31 alle 01:01, John Finlay ha scritto: > > >>Did you think about using Labels and SpinButtons in a Table as an >>alternative to using a TreeView? >> >> > >Not seriously. But then, I wonder: it's probably better to implement the >ill-famed CellRenderButton than MyOwnTreeView... > > > _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
