Re: [Epiphany] Encoding dialog

[Christian Persch <chpe stud uni-saarland de>]

Hi,

just to add a something... In all designs of course the current encoding
would be initially selected, so finding it again in a big list is not a
problem with any of the designs.

Also, many encodings have similar names, differing only in a suffix, so
even a long list is fast to scan.

On Sat, 2003-10-18 at 07:53, Marco Pesenti Gritti wrote:
> Chpe has been working on a better design for encoding menu. We are
> uncertain about what design is better for the dialog.
> The problem is mainly how to allow users to find encoding in a list more
> fastly.
> 
> A two pane view like gnome-chat:
> 
> http://www.gnome.org/~marco/gnomechat-encodings-customise-dialog.png
> 
> Here geographical groups are used, probably it would be better to use
> groups like we have in current encoding menu.
Yeah, the grouping isn't very good... grouping by language would be
better, but then how many languages are there out on the web? ;)

> We could have a "All languages" item selected by default.
That would just make it a overly complicated version of the 1pane view
below...
> A way to get back to the automatic selection could be useful. Maybe add
> a third button "Automatic".
Yes.
> A one pane view, with the Automatic/Custom selection done with radio
> buttons (ignore the rtl radio).
> 
> http://www.gnome.org/~marco/dialog.png
I kind of prefer this one, but I could be biased since I spent quite
some time implementing exactly this :)

> A third alternative could be a tree, with Languages as folders. Though
> that's a pain to implement with current code design :/
Yeah, I think it's not worth it, and anyway as I said above, grouping by
language would make a _huge_ list of language.

> Mpt thinks the complexity of the second pane is not worth with only 80
> items. He seem to be in favor of a tree too ...
Well I think he'd be for 2nd option, since it's his design :)


Regards,
	Christian