thayer@t writes:
> On Mon, Oct 12, 1998 at 11:56:35PM -0500, Linas Vepstas wrote:
>
> <snip>
>
> > I envision creating the reports as html, and using the XmHTML widget to
> > display them. In fact, I am very excited contemplating this technology.
>
> Here's an idea that might be helpful, or it might not:
>
> Rewrite the GNUCash engine as a PHP module. (alternately, as an Apache
> module).
This is a nice idea, yet it adds more dependencies with no
scalability. No matter what interface you use, there will be at least
one whiner, complaining about a lack of an interface for something
else.
I've been thinking a lot recently about a way of doing such things
right. Now it seems to me the right approach would be splitting the
application by two distinct parts: and engine and "clients".
Here by an "engine" I don't mean just Linas's API for accounts
management. Instead, I mean something like a server, which manages
accounts. This server knows about file (or database) I/O, it knows
nothing about GUI, it doesn't care about WWW, and it supports a set of
high-level API via sockets. Ideally, it should allow loading shared
modules w/ encryption, database I/O and additional import/export
facilities.
Once this is done, it'll be relatively easy to create clients using
various GUI kits - all of them will use the same API.
Am I right in this approach, or there is something I'm missing?..
--
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial Research Ltd.
[EMAIL PROTECTED]
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
