Rob Browning <[EMAIL PROTECTED]> writes:

> Matt Armstrong <[EMAIL PROTECTED]> writes:
> 
> What would you *like* to be contributing to?  Like it or not, that's
> a big part of the question.  If you're planning to get heavily
> involved, you, presuming you're capable, may have a lot to say about
> where things are going in the long run.

I'm interested for pragmatic reasons.  If Intuit does a port of
Quicken to Linux, I'll probably lose interest in GnuCash.  I basically
want a clone of that program.  No innovation necessary.  :-)

1) Straighten out the build situation.  I'm interested in this because
   I think it is necessary to keep gnucash alive.

   This involves the automake stuff I'm doing now as well as having a
   good INSTALL file in the root dir that will help people get it
   installed.

   We need a few people who can answer the RPM questions.  Push come
   to show I'll install some weird Linux distribution on my other
   machine and verify I can build gnucash on that.  Gnucash builds
   with relative ease under Debian since all the required packages are
   nicely available pre-compiled.  It should be just as easy for a Red
   Hat folks, etc.  For non Linuxen, providing binaries will be
   harder.  For them, compile instructions will have to suffice.

2) Get GnuCash working well under lesstif.  I'm interested in doing
   this because it is the shortest path towards me getting a working
   GUI.  (I don't care about GTK or Themes or Gnome.  I think Motif
   support will remain important for a long time to come, if only for
   portability reasons.)

3) Improve QIF imports.  I'm interested in doing this because I refuse
   to go back to manually entering all my bank transactions (my bank
   lets me download QIF files for savings/checking/credit).  I'm glad
   to see that Christopher Brown is doing stuff on this.

With those three done, I'd release 1.2.  :-)


>From then on, things get more pipe dreamish:

*) Online banking -- I love paying bills with Quicken.

*) Loan accounts a-la quicken (where it'll automatically split payments
   based on interest/principal, etc.).

*) General GUI ease of use issues.

*) Documentation improvements?

*) World domination.

*) Laughing when Microsoft sends e-mail to this list offering to buy
   GnuCash.


> *I* want to have really good built in scripting so that you can
> fairly easily extend GnuCash to do whatever you want it to do, and I
> want the scripting language to be as powerful as scheme.  Some of
> the more sophisticated pure(ish) functional languages would probably
> be fine too, but those are esoteric, even for me, for this kind of
> job, and we already have a good (IMO) example of a program with
> powerful scheme-ish scripting support in emacs.

Yes.  I have a strong love hate relationship with emacs.  I use about
10% of what it can do.  I keep trying to switch to other editors
because I'm tired of its bloat and I always seem to struggle with
lispish languages.  Whenever I do switch, I always find some missing
feature and switch back.  But I do not like the fact that most of
emacs is in lisp.  It makes it slow and bloated.

Currently, the only thing that really bothers me about guile is that
it takes a long time to start up.

I also think we should never consider a feature finished until the
user doesn't have to edit lisp code to get it to work (import QIF,
online banking, budget, etc.).  I want my mother to be able to use
this program.


> The best I can do is to say which Debian packages I'm using.

I'll add your description to the INSTALL file I'm writing.


Jeremy Collins <[EMAIL PROTECTED]> writes:

> We also probably need some sort of "guide" to developing Gnucash.
> It should contain an up to date list of what is being worked on, who
> is working on it, and what else needs to be worked on.  It should
> also contain information on getting there patches accepted, and who
> they should send them to.  etc, etc, etc... you get the picture.

In some ways, if more discussion occuring on gnucash-devel would
accomplish the same thing.

Part of why gnucash development appeared slow to me was because the
patches weren't posted.  I always love it when I subscribe to a devel
list for a package and browse through the history to find lots of
patches.  :-)


-- 
matt - http://www.lickey.com
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body

Reply via email to