Rob Browning writes:
> gnucash --evaluate '(display "Hello world.\n") (gnc:shutdown 0)'
> For the command line arguments, I want something much more user
> friendly. We may need both a low-level --evaluate, and something
> higher-level as well...
>
> Thoughts?
One of the "lessons learned from" papers on an early GUI-based OS (at PARC,
I think -- I lost my copy) recommended that every significant program should
come in three chunks: a library of functions that do all the work, a GUI
application that calls the library, and a set of command-line programs that each
do a simple thing by calling a few library functions.
I don't know whether gnucash's internals would support this kind of
structure, but the idea is that instead of having a big gnucash program with
--dothis and --dothat options, that may or may not create windows depending on
the mix of options, you would get a gnucash program pretty much as it is now,
and gcdothis and gcdothat programs. And a clean GUI/library split would help
anyone trying to write a KDE front-end :-)
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
