[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: konqueror issues
From:       David Faure <David.Faure () insa-lyon ! fr>
Date:       1999-02-11 13:37:34
[Download RAW message or body]

On Thu, Feb 11, 1999 at 02:11:19PM +0100, Matthias Welk wrote:
> On Thu, 11 Feb 1999, David Faure wrote:
> >On Thu, Feb 11, 1999 at 11:58:47AM +0100, Simon Hausmann wrote:
> >> On Wed, 10 Feb 1999, Matt Koss wrote:
> >> >On St, 10 feb 1999, you wrote:
> >> >>Hi,
> >> >>
> >> >>I dont think that n views are of any help. It is easier to
> >> >>use if you have one or two views only IMHO.
> >> >>
> >> >I agree with this. I would personally use only two views, like its in
> >> >mc. I was using TkDesk for a while, but it's kind of confusing.
> >> 
> >> I agree, too.
> >> 
> >> (so I also vote for KfmViewProps :)
> >   ^^
> >?? I don't understand.
> >
> >You agree that one will never need more than two views, ok. 
> >
> >But KfmViewProps was about allowing the following :
> >a) KfmView doesn't need gui->props()->... anymore - better design
> >b) KfmGui can have _more than two_ views, as the properties would then
> >be in the view itself...
> >c) Same advantages as KfmGuiProps (saving, reading, ... in a central place
> >; default values in a static instance, and above all, local properties).
> >
> >So b) is not an issue if we stick to two views anyway.
> >
> >Anyway, I suggest the following :
> >
> >KfmViewProps, one per view, with view-related items
> > (and a static instance with default values)
> >
> 
> Ok.
> But how will you save the configuration ? I mean, the view know nothing
> about its location (top,bottom,left,right).


KfmGui (or KfmGuiProps) will set the group, then call
view->props()->save(KConfig * config).

Makes sense, doesn't it ?

[prev in list] [next in list] [prev in thread] [next in thread]