> FireFox in the other hand only used new GUI ideas in smart way such as > the use of tabs. the brain gets connected in a way you deal with > other windows in your OS and as soon as the brain sees Chrome it > stops and think ( Why not capitalize on the work done by thousands of > programs , why user needs a training).
The tab bar on top seems more intuitive to me, as the address bar, webpage, and tab itself are all physically connected. > this problem happens when > Chrome is not maximized and many tabs are opened, then you almost > loose the title bar(I know u get about 10px for title bar) and Chrome > start to be hard to drag and move around. Maximized? Are we talking about the Windows version? Why would one need to drag a maximized window? In the Mac version, although the title bar is reduced, the contrast of the tabs still makes it an easy target. In this case, I'd rather have a slightly smaller title bar than less space for displaying content. > I think Google's method in developing Chrome is just like Microsoft's > method in developing Vista. Great GUI + Great Code = Bad Program !!! I'm confused. Vista (at least before the service packs) had an inconsistent GUI and sluggish code, with some flashy transparencies. Does Bad GUI + Bad Code = Great Program? > One more thing is the stop button is so confusing and you have to > change your sight angle to look for it to the right ( that after u > google why no stop button in Chrome !!! and you find it's in the > right !!! ) This, I do agree on. I'm still not used to the stop button on the right (this applies to Safari 4, as well). --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
