Richard Wackerbarth wrote:
> On Thu, 18 May 2000, Bill Gribble wrote:
> > Richard Wackerbarth <[EMAIL PROTECTED]> writes:
> > > I would handle this by having the sample setups in QIF (or a native
> > > gnucash) format and importing those files as needed. There is no
> > > point in creating new mechanisms. However, it might be appropriate
> > > to have a special "button" in the setup wizard to script the import.
> >
> > Having a skeleton of accounts in an .xac file is something that we've
> > talked about for a while.
> >
> > However, it doesn't solve the "I'm a completely new user" problem.
> > You really want a "walk through" which says, "do you have a bank
> > account? what bank? what's the account number?" etc. I think a
> > skeleton of standard accounts is a good thing but not enough in the
> > long run.
>
> I agree.
>
> I was thinking more along the lines of the income/expense part of it with a
> few dummy asset accounts that the user could mimick.
>
> Having a "setup wizard" to lead the user in setting up his asset accounts is
> even better (and more work).
>
> Actually, I see two levels:
> Do you have a(nother) bank account?
> Do you have a(dditional) credit card(s)?
> Do you have any stocks?
> etc.
>
> and
> What is the name of the bank?
> When did you open the account?
> Does the bank pay interest on your deposits?
> etc.
The very first thing I did when starting to use gnucash a few weeks ago was to
set up all of my accounts - nothing in them. I then saved this as a totally
separate file. Whenever I add an account I change this 'skeleton' account file
to track my 'real' account file. Creating a skeleton account file isn't a big
deal and I didn't understand why this wasn't done a long long long time ago by
the gnucash developers - after all they are users also.
