aherman
/
gnucash
mirror of https://github.com/Gnucash/gnucash
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

status updates

Browse Source 
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@2393 57a11ea4-9604-0410-9ed3-97b8803252fd
zzzoldreleases/1.4
Linas Vepstas 26 years ago
parent 87fd144fde
commit c285636a4d
1 changed files with 396 additions and 251 deletions
Show Stats Download Patch File Download Diff File

647
doc/html/C/projects.html
Unescape View File

@ -375,8 +375,8 @@
"Personal Finance Functionality Requirements">
<tr>
<th>Feature</th>
<th>Sizing</th>
<th>Responsible</th>
</tr>
<tr>
@ -388,152 +388,198 @@
<td><a href="#i18n">Internationalization</a></td>
<td>Small</td>
<td>Dave</td>
</tr>
<tr>
<td><a href="#reports">Reports</a></td>
<td>Small</td>
<td></td>
</tr>
<tr>
<td><a href="#graphs">Graphs</a></td>
<td>Medium</td>
<td>Guppi/Bill</td>
</tr>
<tr>
<td><a href="#stock">Simplified Stock Ledger</a></td>
<td><a href="#ledger">Simplified Ledger</a></td>
<td>Small</td>
<td>Dave,Linas</td>
</tr>
<tr>
<td><a href="#glitz">Themes, Icons, Glitz</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#book">Books, Accounting Periods</a></td>
<td><a href="#misc">Miscellaneous Small Tasks</a></td>
<td>Small</td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#check">Check Printing</a></td>
<td><a href="#alerts">Alerts, Recurring
Transactions</a></td>
<td>Small</td>
<td>Medium</td>
<td>RLB</td>
</tr>
<tr>
<td><a href="#userpref">User Preferences</a></td>
<td><a href="#budget">Budgeting</a></td>
<td>Medium</td>
<td>Dave</td>
</tr>
<tr>
<td><a href="#ext">Extension Language Support</a></td>
<td><a href="#check">Check Printing</a></td>
<td>Small</td>
<td>Grib</td>
</tr>
<tr>
<td><a href="#userpref">User Preferences/Session Mgmt.</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#401K">401K etc.</a></td>
<td><a href="#quickim">Quicken(TM) Import</a></td>
<td>Small</td>
<td>Grib</td>
</tr>
<tr>
<td><a href="#note">Annotate with Investment News</a></td>
<td><a href="#quickex">Quicken(TM) Export</a></td>
<td>Small</td>
<td>Grib</td>
</tr>
<tr>
<td><a href="#loan">Loan and Mortgage Calculators</a></td>
<td><a href="#book">Books, Accounting Periods</a></td>
<td>Small</td>
<td>Linas</td>
</tr>
<tr>
<td><a href="#budget">Budgeting</a></td>
<td><a href="#currency">Multiple Currencies</a></td>
<td>Medium</td>
<td>Rethink Requirements-Linas</td>
</tr>
<tr>
<td><a href="#overdraft">Overdraft Alerts</a></td>
<td><a href="#ext">Extension Language Support</a></td>
<td>Medium</td>
<td>RLB</td>
</tr>
<tr>
<td><a href="#quote">Stock Quotes, Price Quotes</a></td>
<td>Small</td>
<td>RLB</td>
</tr>
<tr>
<td><a href="#alerts">Alerts, Recurring
Transactions</a></td>
<td><a href="#install">Install</a></td>
<td>Medium</td>
<td>Small ?</td>
<td></td>
</tr>
<tr>
<td><a href="#quickim">Quicken(TM) Import</a></td>
<td><a href="#double">Forced Double Entry</a></td>
<td>Small</td>
<td></td>
</tr>
<tr>
<td><a href="#quickex">Quicken(TM) Export</a></td>
<td><a href="#401K">401K etc.</a></td>
<td>Small</td>
<td></td>
</tr>
<tr>
<td><a href="#quote">Stock Quotes, Price Quotes</a></td>
<td><a href="#docs">Documentation</a></td>
<td>Small</td>
<td></td>
</tr>
<tr>
<td><a href="#tech">Technical Stock Analysis</a></td>
<td><a href="#note">Annotate with Investment News</a></td>
<td>Medium</td>
<td>Small</td>
<td></td>
</tr>
<tr>
<td><a href="#sink">Depreciation, Sinking Funds</a></td>
<td><a href="#loan">Loan and Mortgage Calculators</a></td>
<td>Medium</td>
<td>Small</td>
<td></td>
</tr>
<tr>
<td><a href="#ofx">OFX, Online Banking, Trading,
Bill-pay</a></td>
<td><a href="#overdraft">Overdraft Alerts</a></td>
<td>Large</td>
<td>Small</td>
<td></td>
</tr>
<tr>
<td><a href="#currency">Multiple Currencies</a></td>
<td><a href="#tech">Technical Stock Analysis</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#double">Double Entry Accounting</a></td>
<td><a href="#sink">Depreciation, Sinking Funds</a></td>
<td>Small</td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#ofx">OFX, Online Banking, Trading,
Bill-pay</a></td>
<td>Large</td>
<td>Dave</td>
</tr>
<tr>
<td><a href="#tab">Tab-delimited ASCII export</a></td>
<td>Small</td>
<td></td>
</tr>
<tr>
<td><a href="#tax">Tax Preparation</a></td>
<td>Large</td>
<td></td>
</tr>
<tr>
@ -541,12 +587,14 @@
organizers</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#emerg">Emergency Records Organizer</a></td>
<td>Small</td>
<td></td>
</tr>
</table>
@ -559,6 +607,7 @@
<th>Feature</th>
<th>Sizing</th>
<th>Responsible</th>
</tr>
<tr>
@ -571,18 +620,21 @@
Objects</a></td>
<td>Large</td>
<td></td>
</tr>
<tr>
<td><a href="#sql">SQL I/O</a></td>
<td>Medium</td>
<td>Linas</td>
</tr>
<tr>
<td><a href="#multiuser">Multi-User Support</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
@ -590,30 +642,35 @@
Receivable</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#payroll">Payroll</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#invoice">Invoicing</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#estimate">Job Costing</a></td>
<td>Medium</td>
<td></td>
</tr>
<tr>
<td><a href="#expense">Expense Accounts</a></td>
<td>Large</td>
<td></td>
</tr>
</table>
<hr>
@ -697,6 +754,8 @@
report, Market Index report, Stock Option values,
Estimation of capital gains tax liabilities.</p>
<p>Reports should be printable to printer.</p>
<p><b>Status:</b></p>
<ul>
@ -769,6 +828,7 @@
settable/controllable -- drag/move callbacks when segments
are click-draged.</p>
<p>Graphs should be printable to printer.</p>
<p><b>Status:</b></p>
<ul>
@ -779,9 +839,21 @@
<br>
</dd>
<dt><a name="stock"><b>Simplified Stock Ledger</b></a></dt>
<dt><a name="ledger"><b>Simplified Ledger</b></a></dt>
<dd>
Ledger needs various fixes/cleanups. Before any fixups can be
done, agreement needs to be gotten as to what the register
*should* look like.
<p>Multi-Line splits look confusing when viewed from
Income/Expense Accounts.
</p>
<p>Stock splits & reverse splits are not displayed correctly.
</p>
<p>Currency trading Ledger is confusing.
</p>
<p>
Stocks and Mutual funds are handled by placing them each in
their own account. Each account can be viewed individually.
If all of the stock accounts are children of a master
@ -790,21 +862,22 @@
general ledger window is a bit obtuse, and difficult to
understand and use. A simplified but still powerful ledger
window is desperately needed.
</p>
<p><b>Question</b>: How to most simply allow the user to
enter loads and fees?</p>
<p><b>Answer</b>: Through splits. Unfortunately, some users
may not properly understand splits, at least not initially.
<p>How to most simply allow the user to
enter loads and fees?
Through multi-line transactions. Unfortunately, some users
may not properly understand multi-line transactions,
at least not initially.
Thus, a little popup is needed to allow the user to type in
the sales load or fee and such, and then auto-create the
needed splits.</p>
needed journal entries.</p>
<p>Note the current transfer window does <em>NOT</em> allow
a share price to be specified !! Needs fixing ...</p>
</dd>
<dt><b>Documentation</b></dt>
<dt><a name="docs"><b>Documentation</b></a></dt>
<dd>Need to add a 'meta keyword' tag to the documetnatin
pages, this will help the search engine (<em>e.g.</em> <a
@ -813,9 +886,8 @@
might be more embeddable ... I am told that htdig-API is in
good solid condition for this, but undocumented.</dd>
<dd><a name="glitz"></a></dd>
<dt><b>Themes, Icons, Glitz</b></dt>
<dt><a name="glitz"><b>Themes, Icons, Glitz</b></a></dt>
<dd>
A variety of finer touches need work:
@ -825,7 +897,9 @@
<p><b>Hint-of-the-Day</b>. A collection of a some
50-100 hints-of-the-day: short (2-4 sentance)
hints/tips on how to use gnucash. Every time the user
starts gnucash, an new hint shows up ...</p>
starts gnucash, an new hint shows up ...
<b>Status:</b> Dave volunteers...
</p>
</li>
<li>
@ -872,8 +946,9 @@
</li>
<li>
<p><b>Cut-n-paste</b> Cut-n-paste of items in the
regsiter window...</p>
<p><b>Cut-n-paste</b> Cut-n-paste of whole transactions
in the regsiter window... <b>Status:</b>Dave... Done. (in
1.4.0)</p>
</li>
<li>
@ -993,9 +1068,63 @@
</ul>
</dd>
<dd><a name="book"></a></dd>
<dt><a name="misc"><b>Miscellaneous Small Projects</b></a></dt>
<dd>
A variety of small projects (mostly in the one person-week
range):
<ul>
<li>
<p><b>File Format</b>. Rework miscellaneous file storage to
use Sleepy Cat DB.
<b>Status:</b> RLB, 2 weeks.
</p>
</li>
<li>
<p><b>Reconcile Window</b>.
<b>Status:</b> Dave.
</p>
</li>
<li>
<p><b>Print Register Window</b>. Output register window to
printer.
<b>Status:</b> none
</p>
</li>
<li>
<p><b>gtkhtml</b>. Grib.
</p>
</li>
<li>
<p><b>print</b>. Grib.
</p>
</li>
<li>
<p><b>key-val pairs</b>. Grib.
</p>
</li>
<li>
<p><b>guid in fileio</b>. Dave.
</p>
</li>
<li>
<p><b>Engine validity test suite</b>.
</p>
</li>
<li>
<p><b>Reconcile groups</b>.
</p>
</li>
<li>
<p><b># of decimal places in prices (penny stock)</b>.
</p>
</li>
</ul>
</dd>
<dt><b>Books, Accounting Periods</b></dt>
<dt><a name="book"><b>Books, Accounting Periods</b></a></dt>
<dd>
Ability to close the book at end of the fiscal year. This
@ -1029,6 +1158,12 @@
match the book period), and the file format needs to
support multiple charts ...</p>
</li>
<li>Memorized Transactions ... Currently, transaction
autocompletion works by autocompleting with the last
'similar' transaction. This ability will get trashed
when books for the old year get closed, because there
won't be 'similar' transactions.
</li>
</ul>
<br>
<br>
@ -1147,125 +1282,31 @@
<br>
</dd>
<dd><a name="401K"></a></dd>
<dt><b>401(k), RSP</b></dt>
<dd>
401K, 403, IRA, Roth IRA, SEP, Keogh ... "Retirement Savigs
Plans"
<p>Retirement Savings Plans often do not put a high
priority on tracking costs, as the tax implication is that
amounts are taxable upon withdrawal, meaning that there is
little necessity to track capital gains. (huh??)</p>
</dd>
<dt><a name="note"><b>Annotate with News Stories</b></a></dt>
<dd>
Download, save, annotate investment news and research.
<p>Provide a way of storing news stories with accounts, and
possibly annotating individual transactions in the same
way.</p>
</dd>
<dt><a name="loan"><b>Loan and Mortgage
Calculators</b></a></dt>
<dd>
Provide a variety of simple GUI utilities to allow user to
calculate the future value of loans, mortgage payments,
interest payments, etc.
<p><b>Status:</b></p>
<ul>
<li>Not Started.</li>
</ul>
<br>
<br>
</dd>
<dt><a name="overdraft"><b>Overdraft Alerts</b></a></dt>
<dt><a name="alerts"><b>Recurring Transactions, Calander Alerts</b></a></dt>
<dd>
Overdraft alerts are popups that pop up whenever the user
enters a transaction that would move an account below some
minimum balance, or above some max balance (for a bank
account) or an expense/spending limit is reached (on an
expense account). A similar but different alert can be
implenmented for price highs &amp; lows. Note that these
alerts do <em>not</em> require any sort of calendaring or
recurring transaction support.
<p>Design requirements: implement multiple (not just two)
alerts for any account type. Alert should consist of</p>
<ul>
<li>value point or price point</li>
<li>movement direction</li>
<li>'is active' boolean flag (<em>i.e.</em> Should be
possible to 'turn off alert' without deleting it)</li>
<li>memo text</li>
</ul>
<br>
<br>
<p><b>Status:</b></p>
<ul>
<li>Not Started.</li>
</ul>
<br>
<br>
</dd>
<dt><a name="alerts"><b>Recurring Transactions, Calander
Alerts</b></a></dt>
<dd>
Add support for automatic, recurring transactions, <em>
(1)Add support for automatic, recurring transactions, <em>
e.g.</em> mortgage payments, fixed-interest bonds, regular
salary checks, regular gas/phone/electric bills, <em>
etc.</em>
<p>Loans &amp; mortgages are one of the more complicated
recurring transactions. Consider the following dialogue
layout:</p>
<pre>
loan amount $_____________ currency _________ (pull-down menu)
Remaining balance $___________
Payment amount $___________
balloon payment $_____________
other payment $________ (e.g. escrow, tax)
Payment frequency (weekly/monthly/bimonthly/quarterly/yearly)
loan start date mm/dd/yy length -----(weeks/months/years/peyments)
loan time left (number of days/weeks/months, rounded)
number of payments left
interest rate %__________________
payee ____________
pay-from account __________________
next due date mm/dd/yy
</pre>
Note that in the above, not all fields are independent:
some can be calculated from others. The <tt>other
payment</tt> should bring up a mini-register, allowing user
to add any number of splits.<br>
<br>
<p>Recurring bills, salary income, etc. are simpler to
<p>(2) Recurring bills, salary income, etc. are simpler to
handle, since they don't have intersest rates, balloons,
etc. They do/will have multiple splits (<em>e.g.</em>
payroll gross, fica, futa, income taxes, payroll net).</p>
<p>Provide a calender-display of upcoming &amp; past
<p>(3)Provide list of upcoming &amp; recently paid
bills/scheduled payments/scheduled deposits for the next
1,2,3,6,12 months. Historical view shows payments crossed
out (!?)</p>
<p>(4)Loans &amp; mortgages are one of the more complicated
recurring transactions. Typically, there might be a years
worth of smaller payments, then a long string of larger
payments, followed by a baloon.
</p>
<p>(5)Provide a calender-display of upcoming &amp; past
scheduled payments. Clicking on a calander day should raise
up editable list of transactions. Calendering should
include generic red-lettering of important dates: taxes
@ -1276,11 +1317,6 @@ next due date mm/dd/yy
Technology: need to find/evaluate gnome-calender/dayplanner
for integration.</p>
<p>Provide list of upcoming &amp; recently paid
bills/scheduled payments/scheduled deposits for the next
1,2,3,6,12 months. Historical view shows payments crossed
out (!?)</p>
<p><b>Design Notes:</b> Most alerts &amp; data storage
should be driven out of the engine. This will enable
multi-user, distributed use. <b>Note:</b> alerts should be
@ -1308,6 +1344,7 @@ next due date mm/dd/yy
<ul>
<li>Need to create design doc, need to implement engine
pieces, need to hunt down gnome-calendering bonobo.</li>
<li>RLB thinks its 2-3 weeks for items 1,2,3.
</ul>
<br>
<br>
@ -1364,23 +1401,24 @@ next due date mm/dd/yy
<p><b>Status:</b></p>
<ul>
<li>Quicken import is implemented and mostly works. Work
needs to be done for recurring transactions, etc.</li>
<li>Quicken import is implemented and mostly works.
(Bill Gribble, Done, in version 1.4.0)</li>
<li>Work needs to be done for recurring transactions, etc.</li>
<li>
QIF processing, as used for on-line banking, is <em>
not</em> implemented. That is, staged import isn't
done.
<p>Note that since banks use QIF, the <em>correct</em>
Note that since banks use QIF, the <em>correct</em>
way to reconcile bank accounts on-line is through
QIF.</p>
<p>On one side, we have existing recorded transactions;
QIF.
On one side, we have existing recorded transactions;
on the other, the latest bank statement, in QIF
format.</p>
<p>Now, just put them together ...</p>
format.
Now, just put them together ...
Grib estimates 2 weeks for this.
</p>
</li>
</ul>
<br>
@ -1466,6 +1504,188 @@ next due date mm/dd/yy
stand-alone perl script run from <tt>crontab.</tt> This
will be done by writing scheme wrappers for the module
(???)</li>
<li>RLB has integrated with GUI, using scheme. Done in
version 1.4.0. Does this mean gnc-prices is dead, or is it
--batch ??
</ul>
<br>
<br>
</dd>
<dt><a name="install"><b>Install</b></a></dt>
<dd>
Install on Redhat, Caldera, Corel, SuSE, FreeBSD, TurboLinux,
etc.
</dd>
<dt><a name="currency"><b>Multiple Currencies</b></a></dt>
<dd>
Need to support multiple currencies.
Work is needed in the GUI. The engine currently supports
multiple currencies by treating them as securities, thus
allowing currency trading. The currency-trading register
needs a complete overhaul as it is obtuse and
unintuitive.</p>
<p>A simplfied way of dealing with one-shot currency
exchanges needs to be implemented, essentially just a
simple calculator popup.</p>
<p>
<b>Status:</b> Need to rethink wether the one-shot exchanges
should in fact be recorded full-fledged in the engine.
Also: EURO support is currently hacked in: the EURO is treated as
a 'special' currency. Virtually all the euro code can be fully
generalized (and should be).
</p>
</dd>
<dt><a name="double"><b>Forced Double-Entry</b></a></dt>
<dd>
The system supports double-entry: every transaction
indicates a pair of accounts: one is debited, and one is
credited.
<p>Double-entry is a powerful way of ensuring the integrity
of of the financial data. Currently, while double-entry is
supported, its use is not enforced: the user <em>can</em>
create dangling transactions, where only one account is
indicated.</p>
<p>Although this is acceptable for home use (arguably
desirable, since it allows the casual user the simplicity
they desire), it is not acceptable for business use. (The
counterargument is that casual users that aren't
accountants need all the help at getting things right that
they can get.)</p>
<p>It must be possible to enforce double entry, so that a
transaction cannot be completed until two accounts have
been specified.</p>
<p><b>Restricted Double</b> Note that sometimes, the words
'single-entry' have a an alternate meaning: they can mean
'a double entry account which can only be credited, or
debited, but not both'. We need to implement this.</p>
<p><b>Current status:</b></p>
<ul>
<li>April 1998 -- The engine has a couple of flags in it
that control double-entry behavior: it can be made lax or
strict, however, they are compiled in, and there is no
way to change them from the GUI.</li>
<li>Dec 1998 -- Scrubber functions implemented to crawl
through data, and find all unbalanced or orphaned
transactions.</li>
<li>May 2000 -- Default will be changed to double-entry
always. It will not be possible to disable this and move
to single-entry.</li>
</ul>
<br>
<br>
</dd>
<dt><a name="401K"><b>401(k), RSP</b></a></dt>
<dd>
401K, 403, IRA, Roth IRA, SEP, Keogh ... "Retirement Savigs
Plans"
<p>Retirement Savings Plans often do not put a high
priority on tracking costs, as the tax implication is that
amounts are taxable upon withdrawal, meaning that there is
little necessity to track capital gains. (huh??)</p>
</dd>
<dt><a name="note"><b>Annotate with News Stories</b></a></dt>
<dd>
Download, save, annotate investment news and research.
<p>Provide a way of storing news stories with accounts, and
possibly annotating individual transactions in the same
way.</p>
</dd>
<dt><a name="loan"><b>Loan and Mortgage Calculators</b></a></dt>
<dd>
Provide a variety of simple GUI utilities to allow user to
calculate the future value of loans, mortgage payments,
interest payments, etc.
<p> Consider the following dialogue layout:</p>
<pre>
loan amount $_____________ currency _________ (pull-down menu)
Remaining balance $___________
Payment amount $___________
balloon payment $_____________
other payment $________ (e.g. escrow, tax)
Payment frequency (weekly/monthly/bimonthly/quarterly/yearly)
loan start date mm/dd/yy length -----(weeks/months/years/payments)
loan time left (number of days/weeks/months, rounded)
number of payments left
interest rate %__________________
payee ____________
pay-from account __________________
next due date mm/dd/yy
</pre>
Note that in the above, not all fields are independent:
some can be calculated from others. The <tt>other
payment</tt> should bring up a mini-register, allowing user
to add any number of splits.<br>
<br>
<p><b>Status:</b></p>
<ul>
<li>Not Started.</li>
</ul>
<br>
<br>
</dd>
<dt><a name="overdraft"><b>Overdraft Alerts</b></a></dt>
<dd>
Overdraft alerts are popups that pop up whenever the user
enters a transaction that would move an account below some
minimum balance, or above some max balance (for a bank
account) or an expense/spending limit is reached (on an
expense account). A similar but different alert can be
implenmented for price highs &amp; lows. Note that these
alerts do <em>not</em> require any sort of calendaring or
recurring transaction support.
<p>Design requirements: implement multiple (not just two)
alerts for any account type. Alert should consist of</p>
<ul>
<li>value point or price point</li>
<li>movement direction</li>
<li>'is active' boolean flag (<em>i.e.</em> Should be
possible to 'turn off alert' without deleting it)</li>
<li>memo text</li>
</ul>
<br>
<br>
<p><b>Status:</b></p>
<ul>
<li>Not Started.</li>
</ul>
<br>
<br>
@ -1473,7 +1693,7 @@ next due date mm/dd/yy
<dt><a name="tech"><b>Technical Stock Analysis</b></a></dt>
<dd>Provide technical sotck analysis graphs, <em>e.g.</em>
<dd>Provide technical stock analysis graphs, <em>e.g.</em>
volume, 90 moving avg, beta, etc. See gstalker for example of
how to do it ...</dd>
@ -1579,71 +1799,6 @@ next due date mm/dd/yy
</pre>
</dd>
<dt><a name="currency"><b>Multiple Currencies</b></a></dt>
<dd>
Need to support multiple currencies.
<p>Work is needed in the GUI. The engine currently supports
multiple currencies by treating them as securities, thus
allowing currency trading. The currency-trading register
needs a complete overhaul as it is obtuse and
unintuitive.</p>
<p>A simplfied way of dealing with one-shot currency
exchanges needs to be implemented, essentially just a
simple calculator popup.</p>
</dd>
<dt><a name="double"><b>Forced Double-Entry</b></a></dt>
<dd>
The system supports double-entry: every transaction
indicates a pair of accounts: one is debited, and one is
credited.
<p>Double-entry is a powerful way of ensuring the integrity
of of the financial data. Currently, while double-entry is
supported, its use is not enforced: the user <em>can</em>
create dangling transactions, where only one account is
indicated.</p>
<p>Although this is acceptable for home use (arguably
desirable, since it allows the casual user the simplicity
they desire), it is not acceptable for business use. (The
counterargument is that casual users that aren't
accountants need all the help at getting things right that
they can get.)</p>
<p>It must be possible to enforce double entry, so that a
transaction cannot be completed until two accounts have
been specified.</p>
<p><b>Restricted Double</b> Note that sometimes, the words
'single-entry' have a an alternate meaning: they can mean
'a double entry account which can only be credited, or
debited, but not both'. We need to implement this.</p>
<p><b>Current status:</b></p>
<ul>
<li>April 1998 -- The engine has a couple of flags in it
that control double-entry behavior: it can be made lax or
strict, however, they are compiled in, and there is no
way to change them from the GUI.</li>
<li>Dec 1998 -- Scrubber functions implemented to crawl
through data, and find all unbalanced or orphaned
transactions.</li>
<li>May 2000 -- Default will be changed to double-entry
always. It will not be possible to disable this and move
to single-entry.</li>
</ul>
<br>
<br>
</dd>
<dt><a name="tab"><b>Tab-delimited ASCII file
format</b></a></dt>
@ -2001,9 +2156,7 @@ Password:
<li><a href=
"http://www.mail-archive.com/gnucash-devel@gnucash.org/">
GnuCash Mail archives</a></li>
<li style="list-style: none">-- alternate.</li>
GnuCash Mail archives</a> -- alternate.</li>
<li><a href="http://www.pathcom.com/~sstratos/">gstalker</a>
gtk/gnome stock grapher.</li>
@ -2134,9 +2287,7 @@ Password:
<ul>
<li><a href="http://www3.hmc.edu/~rclark/xacc/">X-Accountant
Home Page</a></li>
<li style="list-style: none">- this was the original site for
Home Page</a> - this was the original site for
the GPL'ed accounting package that eventually evolved into
GnuCash. Robin Clark wrote the first version while at school
at Harvey Mudd College.</li>
@ -2148,21 +2299,15 @@ Password:
there was talk of joining forces with X-Accountant.</li>
<li><a href="http://www.telly.org/freemoney/">FreeMoney</a>
Linux small-business accounting s/w.</li>
<li style="list-style: none">A proposal to build a business
package back by SQL.</li>
Linux small-business accounting s/w. A proposal to build a
business package back by SQL.</li>
</ul>
<hr>
Draft version 0.37 -- May 2000
<p>Linas Vepstas <a href="mailto:linas@linas.org">
Draft version 0.38 -- June 2000
Linas Vepstas <a href="mailto:linas@linas.org">
linas@linas.org</a><br>
</p>
<p>updates by Christopher Browne <a href=
updates by Christopher Browne <a href=
"mailto:cbbrowne@ntlug.org">cbbrowne@ntlug.org</a><br>
</p>
</body>
</html>

Write Preview
Loading…
Cancel
Save