El Domingo, 28 de Mayo de 2006 02:52, Aaron J. Seigo escribió: > On Saturday 27 May 2006 14:57, Iñaki wrote: > > Sincerelly I can't imagine with one is better. Could I hear your > > opinions? > > IMHO the first one is much better. > > from a technical standpoint, it is much easier to code. > > from a usability standpoint, having the tabs in between better reflects > what we see in other applications (inc outside of kde) so gets points for > user familiarity but also strengthens the relationship between "these are > the actions for this specific tab" and "these are generic actions > application to any tab". right now we have the problem of "window global" > versus "kpart specific" actions not being clearly differentiated, which > having the tabs between the toolbars sorts out very nicely. > > the second option does show the relationship between the tab and the > location bar (and other actions) clearly but feels wrong visually for some > reason (ok, that's pretty vague =). i'd also note that it doesn't solve the > problem -at all- for the case when the window is split into one or more > panes. > > and that's a challenge with split panes. it would almost make sense to put > the location path right inside the content window itself. *shrug*
And what about this picutre? http://konqueror4.home.dyndns.org/Varios/konqueror4_tab_connection.jpg I mean: a tab design that shows the user the connection between the navigation bar and the specific bar + window content. Of course in this way the tabs are not so "beautiful", but I'm sure a good designer could do a great proposal. PD: Sincerelly I prefer the first option (the original one), but it's true that the second one shows better the relationship between tab and location bar. PPD: Opera browser uses the second way, and looks very nice, I can't imagine problem for a common user because of using that way. Regards. -- Iñaki _______________________________________________ Appeal mailing list [email protected] https://mail.kde.org/mailman/listinfo/appeal
