Re: Several comments on panel, nautilus and evolution

[Mike Palczewski <mpalczew u washington edu>]

On Thu, Sep 07, 2000 at 03:00:17PM -0700, Alan wrote:
> On Thu, Sep 07, 2000 at 02:11:01PM -0700, Mike Palczewski wrote:
> > On Thu, Sep 07, 2000 at 02:07:41PM -0700, Alan wrote:
> > > 
> > > On Fri, Sep 08, 2000 at 07:27:49AM +1100, Jason Stokes wrote:
> > > > 
> > > > Loban Rahman wrote:
> > > > 
> > > > > Simple solution to end this argument: Evolution brings up a setup dialog
> > > > > when a user runs it for the first time. This dialog should ask "where to
> > > > > store evolution files", with "$HOME/evolution" being the default (or
> > > > > "$HOME/.evolution", it doesn't really matter). Once the user accepts
> > > > > a certain directory, the value can be stored in a file in "$HOME/.gnome"
> > > > > or something.
> > > > 
> > > > As Alan Cooper would point out, why should the user be asked to
> > > > administrate where Evolution stores its configuration information? 
> > > > Users shouldn't have to deal with what is a low-level design issue, not
> > > > an user interface issue. Storing configuration information is the
> > > > programmer's responsibility.  Don't design for geeks; design for real
> > > > people.
> > > 
> > > Agreed, but there should still be the option somewhere, so that the "power
> > > user" can move things around if needed.  Perhaps an "advanced options"
> > > tab/button on the initial setup with these sorts of options in it?
> > But a "power user" shouldn't really care becase she/he can use symlinks and
> > move stuff around while maintaining a symlink.
> 
> Yes and no... I'd rather not have ~/evolution, ~/nautilus, ~/some_other_progs
> filling up my home dir.  If I do want to see ~/evolution, I can symlink
> .evolution to it, but not the other way around :)  

thats what I meant

-- 
Mike Palczewski (mpalczew u washington edu)