IntenseFinance/gnucash
3
0
Fork 0
mirror of https://github.com/Gnucash/gnucash.git synced 2025-02-25 18:55:30 -06:00
Code Issues Packages Projects Releases Wiki Activity

updates of status

Browse Source 
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@496 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Linas Vepstas 1998-02-03 00:04:47 +00:00
parent 8407a1104c
commit d63add89bf
1 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
Docs/projects.html
View File

@ -96,6 +96,10 @@ architectural goals.
separation would make the design and implementation of new ledger separation would make the design and implementation of new ledger
windows much simpler and easier. windows much simpler and easier.
<p> <p>
Current Status: the latest alpha-development releases (version
1.1.x) contain such an object. Its currently motif-based, but
should be easily portable.
<p>
<dt><b>C++</b> <dt><b>C++</b>
<dd>The current code is written in C, in an object-oriented fashion. <dd>The current code is written in C, in an object-oriented fashion.
@ -141,7 +145,8 @@ architectural goals.
<dd>The current system makes a distinction between the data (account, <dd>The current system makes a distinction between the data (account,
transaction) and they GUI that displays it. This distinction should transaction) and they GUI that displays it. This distinction should
be further strengthened, and a set of financial objects, residing in be further strengthened, and a set of financial objects, residing in
their own library, should be created. their own library, should be created. Current Status:
ready to split this stuff off into its own library.
</dl> </dl>
<p> <p>
@ -171,8 +176,13 @@ immediately, independent of the major goals.
<dd>All menus, markup and help-text should be internationalized, <dd>All menus, markup and help-text should be internationalized,
so that X-Accountant could be usable in any country. This so that X-Accountant could be usable in any country. This
would include the printing of currency values in the local would include the printing of currency values in the local
country conventions. Current status: most messages have been country conventions. Current status: most English-language
moved to a single header file. messages have been #defined and moved to a single header file.
Still looking for an infrastructure for choosing a message
catalogue. Looking for routines that can parse and print
monetary values in different formats, as well as date/time
parsing/printing routines. (xacc contains such parsing
routines, but they're not very powerful or i18n'ed.)
<p> <p>
<dt><b>Navigation</b> <dt><b>Navigation</b>
@ -382,7 +392,7 @@ Your name here as project contributor!
</ul> </ul>
<hr> <hr>
Draft version 0.13 December 1997<br> Draft version 0.14 January 1998<br>
Linas Vepstas <a href="mailto:linas@linas.org">linas@linas.org</a><br> Linas Vepstas <a href="mailto:linas@linas.org">linas@linas.org</a><br>
Robin Clark <a href="mailto:rclark@hmc.edu">rclark@hmc.edu</a><br> Robin Clark <a href="mailto:rclark@hmc.edu">rclark@hmc.edu</a><br>
</body> </body>