Re: File selector talk writeup

[Havoc Pennington <hp redhat com>]

On Sun, Feb 16, 2003 at 03:52:38PM -0500, Owen Taylor wrote:  
> > Besides, for a such a common feature it makes sense to have an API
> > shortcut that doesn't involve creating the widget manually
> 
> Hmm, I'd be interested to see what your API proposal for this is.
> It seems to me that if we have 4-5 things of the type:
> 
>  gtk_file_chooser_set_show_open_read_only()
>  gtk_file_chooser_get_show_open_read_only()
>  gtk_file_chooser_get_open_read_only()
>  gtk_file_chooser_set_open_read_only()
> 
> Plus corresponding properties it's going to make for a big
> messy API.

If there are really add-ons that are pretty common, to me 4-5
functions is a reasonable price for making it easy for apps to be
consistent.

But if the add-ons are all app-specific of course there's no point.


Encoding menu is needed for terminal, web browser, text editor, etc.,
both in the filesel and in the main menus, I wouldn't mind
g_encodings_list() or something either... that list just doesn't
belong in gnome-terminal, dunno where it should live but not there.

Other than encoding though I can't think of any good examples of 
common add-ons.

Havoc