a client/server
design, just to guarantee that the GUI guys won't mutilate the engine
functionality every time they implement a new visual quirk. Besides, I
want to make sure GnuCash allows doing all stuff Quicken does and
beyond.
--
Alexander L. Belikoff
Bloomberg L.P. / BFM Financial
A per se, I am not the most knowledgeable person over here.
To me, CORBA always meant "an ominously bloated piece of software
trying to solve too many problems to be used reliably in small- and
medium-scale projects". Maybe I am wrong...
[EMAIL PROTECTED] writes:
> It's been rumoured that Alexander L. Belikoff said:
> > 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
llow 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 missi
