On Thu, 20 Apr 2000, you wrote: > On Thu, 20 Apr 2000, John Hasler wrote: > > It would be necessary if I came up with changes that make gnucash suitable > > for my purposes but are not acceptable to the authors. Example: Bill thought fixing the transaction report was a waste of time -- his find dialog, using the register would provide the same functionality better. I disagreed, now we have both. > > Please clarify your idea of what is needed. > I'll take this opportunity to ask: what are the priorities of the developers? One thing about gnucash being your dayjob: it's harder for you to say "you want it? code it up then, we'll accept a patch gladly." :) I'm willing to help out, but my dayjob & my social life keeps me pretty busy. Here are the things that are reducing my "enjoyment" of gnucash. 1. better investment reports. This requires a strategy to deal with things like commissions and dividends. My opinion is that this should be dealt with via meta-information. We shouldn't be setting account policy. 2. better entry of investments. I'm not asking for a wizard, but it's a pain in the butt to have to switch account windows to enter commissions, etc. 3. better entry of budgets. You may have noticed that I've spent more time on the budget output than on the input. :) 4. graphing infrastructure, using a similar strategy to my new report infrastructure. The goal is to make it easier to switch away from gnuplot if so desired, as well as make it easier to add new graphs. Except for #2, I think I would be a good person to handle these jobs. Unfortunately, my day job and my social life and my sleep consume virtually all of my time. It'd probably take me a month to do any one of the three. Any opinions on what I should work on? Bryan ------------- Bryan Larsen, Senior Software Engineer & fall guy Phone: 306 664 2087 x29. Fax: 306 664 4446 Analog Design Automation: Analog Circuit Synthesis? Problem Solved. -- Gnucash Developer's List To unsubscribe send empty email to: [EMAIL PROTECTED]
