Peter, Thanks for your reply.
I really can't see how the shortcomings I have mentioned in the Chrome interface can be a benefit? Do you foresee performance implications? I disagree with your comment that more options means a usability death. This is possible, but not a given! For example, why cannot a long click on the star button show all bookmarks (This behaviour exists for your back button)? Maybe click and downward drag? Can I ask how you manage with your bookmark bar turned off? Please try using Google Apps, with multiple logins on multiple apps domains with your password manager? It is impossible. I cannot use a Google browser with Google's maiden app suite!!!! What is the difference between the Reload and Go? How would you want me to solve my complaints? Are there commercial issues? I note Chrome is unfinished (beta) and wish to help! I hope this isn't a case of users doing things with software that the authors never even considered anyone would want! Regards, Chris On Oct 19, 11:04 pm, "Peter Kasting" <[EMAIL PROTECTED]> wrote: > On Sun, Oct 19, 2008 at 2:43 PM, Chris G <[EMAIL PROTECTED]> wrote: > > As you surf the web nothing will ever be filled, and you need never > > know the passcard system is at work! However as you surf the browser > > will scan its passcards and if there is one matching the current page > > a button will light (It does this at the moment for the star > > button). > > We considered and rejected this kind of approach. It's less intuitive and > requires users to change their focus from the page content to the browser > chrome. It also adds to the chrome for functionality that is not useful on > the majority of pages. > > If you only want to fill > > > and not submit this will be supported (allowing you to edit prior to > > submit). It will also have an option to only fill empty fields. > > Multitudinous options = usability death > > > The existing system only > > supports a username and password. My system will support unlimited > > fields. A possible extension could also store your address or credit > > card number for filling into any form. > > Form filling and password filling seem distinct to me, and we're working on > improving them in distinct ways. > > 2) Accessing my bookmarks. I have Chrome reload my last tabs on > > > startup, and would prefer to have my bookmark bar hidden (33% less > > Chrome) but I can't! In this case (Ie reusing tabs) it is impossible > > to access my bookmarks without typing in the Omnibox! We need a > > button on the main toolbar for navigating to bookmarks! I need to > > experiment for the best way to implement this, ideally reusing an > > existing button. This will enable me to have much less Chrome in > > normal circumstances. Needless to say this integrates nicely with my > > proposal for (1). > > This is a totally unrelated issue to the first one. > > Over time I believe the best solution here will be to simply allow users to > move bookmarks between the "bookmarks bar" and the normal toolbar. We have > had a few brainstorming-level ideas about this. > > Why do you have a reload and go button that > > > both do the same thing? > > Because they don't do the same thing? > > > Why does the bookmark bar not expand, scroll > > or intelligently reorganise when the buttons don't fit on one line > > (maybe another job for me)? > > Because all of these have their own downsides. > > Why is the Task Manager accessed on the > > > Page menu? > > Because its parent group, the Developer tools, are primarily page-focused. > > > Why is the Home button hidden by default? > > Most homepages are not user-set and are lousy experiences compared to the > New Tab Page. > > > Why does View > > Source in Page menu not load the webkit inspector? > > ?? Because it views source. Much like how installing Firebug for Firefox > doesn't hijack the meaning of "view source". > > When there is only > > > one tab, why not hide the tab bar? > > There would be no place to display the page title or favicon; the window > would have no drop target for tabs from other windows; the UI would shift in > jarring ways; etc. > > > To conclude, I wish to throw away your password manager (sorry), add a > > new (or change an existing) button to access bookmarks, passcards and > > > management screens, and tweak your bookmark system to replace the > > password manager and do form filling, bringing the whole subsystem > > into line with your existing history/smart homepage subsystem. > > To conclude, I think the changes you're proposing are drastic and not going > to be particularly helpful to users. It takes a great deal of time, and > usually more than one person's input, to design a system that will work well > for everyone. I think the questions in your email demonstrate that you > grasp how the current UI (of many parts of the browser) falls short for you, > but fail to appreciate its benefits for others. > > PK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
