+1 If we make the css easy to use and provide a couple of examples in the documentation, that probably will ensure most extensions' prefs will look similar because it will be the path of least resistance. Developers who need more can build on the foundation or do something totally different if they want.
2009/10/2 Jói Sigurðsson <j...@chromium.org> > > How about leaving the structure of the options up to developers (i.e. > leaving it an HTML page), but providing a CSS file with styles that > can make these pages mostly uniform-looking? > > Cheers, > Jói > > > On Fri, Oct 2, 2009 at 1:26 PM, Akira <ak...@yayakoshi.net> wrote: > > > >> animgifs to make it cool and someone else will use a flash file to > >> provide even cooler animations. > > > > Someone sticking flash in the chrome-extension://.../xxxx.html page > > where the user sets options is a good example of the worst-case > > possibilities, yes. > > > > On Oct 2, 8:00 pm, UVL <andrea.do...@gmail.com> wrote: > >> If we let any extension developer to build his own preferences page, > >> the user experience will be always different and quite bad, with > >> checkboxes on the left, sometimes on the right, someone will use > > > > If we examine the limited UI config systems that already exist in the > > wild those criticisms apply to them and the case for not using a > > limited config system is made once again. In Firefox extensions we see > > that the "Options" window framework doesn't prevent things from being > > cluttered. I sampled some popular extensions tonight, confirming this- > > they need a lot of tabs to include all items and things can't be > > grouped in a natural or obvious way all the time in that situation. A > > limited set of controls forces information to be entered through some > > non-optimal inputs, e.g. ordinary list boxes that must be typed into, > > or right-clicked before doing secondary action, when you'd prefer to > > have list of draggable items. Visual control is apparently not > > practical (or possible?), e.g. hiding options that are not relevant > > until another option is selected. > > > > If you think "Well, the Firefox example can be improved on and we can > > provide those extra things", consider the mess you'd get into trying > > to define a manifest format that allows all of that. Programming the > > form/window renderer that displays it would be a proportionally longer > > job. > > > > Usability requires UI that induces to user to discover the > > functionality and complete operations with the least effort. HTML/CSS > > has evolved to be as much as possible to as many different types of > > developers as possible whilst not sucking. > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensions@googlegroups.com To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
