Aaron J. Seigo kirjoitti viestissään (lähetysaika sunnuntai, 28. toukokuuta 2006 05:38): > On Saturday 27 May 2006 19:44, Iñaki wrote: > > El Domingo, 28 de Mayo de 2006 02:52, Aaron J. Seigo escribió:ow itself. > > > > 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. > > at the cost of showing the relationship between the part's toolbar and the > tab. imagine when the kpart has a forwards/backwards button like kpdf (nee, > okular ;) does? no, i really think the separation is useful to us. > > keeping the common controls separate from the content-specific controls is > a real win in mymind.
Another issue that IMHO should be taken into account here is that several options in the (at least current) konqueror menu are also tab specific (i.e. affect only the selected tab) and, when you really think about it, even the window title is tab specific. So if one were to group all _tab_ specific controls within each tab, the current konqueror GUI (and probably the whole GUI paradigm) would need a pretty complete overhaul (which might not necessarily be a bad thing, per se) The other option, which Aaron describes above, is to group the _content_ specific controls (i.e. the options, which vary depending on what's inside the current tab) below the tabs, as also illustrated by Iñaki's original web preview. IMHO having the location bar and other tab-specific things outside the tab is clearly unintuitive (if you want an clear example of this, try using the MySQL Query Browser http://www.mysql.com/products/tools/query-browser/ & http://dev.mysql.com/downloads/query-browser/1.1.html). But, on the other hand, if designed well (e.g. if the distance between the location bar and tabs is small enough), it's pretty easy to get used to it. On the other hand, while grouping all tab specific stuff within the tab is intuitive, it would pretty much mean that the tab bar would have to be placed into the window title, along with a menu including all the common functions (new window, close, settings, etc.). Everything else would be situated within the tabs. One option (although I'm not sure if it's really doable) would be to make tabs more generic. After all, tabs were originally created because managing a lot of windows is a real pita. So, if one were to think of a way to group and organise windows in a way similar to tabs, one might be able to create a more generic solution (something like a frame/context specific taskbar, which would also allow grouping different applications). -- Jani-Matti Hätinen _______________________________________________ Appeal mailing list [email protected] https://mail.kde.org/mailman/listinfo/appeal
