From kde-core-devel Mon Oct 01 12:36:31 2007 From: Andreas Pakulat Date: Mon, 01 Oct 2007 12:36:31 +0000 To: kde-core-devel Subject: Re: Behavior change in KPageDialog/KPageWidgetItem Message-Id: <20071001123631.GD14501 () morpheus ! apaku ! dnsalias ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=119124233013098 On 01.10.07 08:21:04, Adam Treat wrote: > On Monday 01 October 2007, Anders Lund wrote: > > On Monday 01 October 2007, Sebastian Kügler wrote: > > > On Monday 01 October 2007 12:16:30 Anders Lund wrote: > > > > On Monday 01 October 2007, Sebastian Kügler wrote: > > > > > I had a quick look at kate's config dialogue, and I don't see > > > > > immediately why you think it isn't possible. Put simply, right now > > > > > there's a two level hierarchy, treebranches, treenodes (= pages). > > > > > Only one config page has more than one tab. Making the branches the > > > > > top level items (i.e. those that show up in the iconview on the left) > > > > > and having the branches as tabs makes sense to me. > > > > > > > > I'm not sure I understand this. What I do know is that no widget should > > > > have more tabs than will fit it's natural size, that is, truncating tab > > > > titles or having scroll buttons on tabbars is a definite NO. If that is > > > > required (and that is how i understand your suggestion, two widget with > > > > LOTS of tabs), the tree is MUCH prefferable!! > > > > > > You're referring to konqueror here or to kate? In konqueror's case, the > > > thing getting in the way is the filemanagement / browser settings > > > distinction. Not sure how to solve this in the best possible way. > > > In kate, it looks relatively straightforward from a quick glance. > > > > I refer to Kate's configuration dialog. Kate has two groups of > > configuration widgets, one from katepart and one from kate. Neither group > > can be squeezed into one tabbed widget without the tabbar being too wide to > > fit the widget. > > I think the thing to do is stop dividing it up between the two current > categories. Is there any real reason that the user of kate needs to know > that the katepart settings are different from kate the app? If so, then I'd > either suggest to provide two different configuration dialogs that would make > this explicit IMHO thats a good idea, after all almost all katepart-using apps use the "Configure Editor" item in the Settings menu. So Kate having "Configure Editor" and "Configure Kate" would keep consistency even. Andreas -- You own a dog, but you can only feed a cat.