Quoting Daniel Espinosa <[EMAIL PROTECTED]>:
> Are there any point to take apart the "internal functionality" and the
> "DB work"?
No.
> Are we thinking about to use the power of the DB in data managing? Are
> there a point where we can "change" the core in that way? and
> implement a "plugin to import 'old format'?
No.
> Sorry, but I need to study some code before make sure about you're
> talking about but, I don't want to try to implement the GC "internal
> functionality" forcing the DB to that, without consider the power or
> problems, when you use a DB.
The DB is just a data-store to gnucash. Nothing more.
> Have you consider to implement this backend using GObject, and
> implement a interface to QOF to avoid re-write the entry core, but
> make the first steps to implement a new arquitecture in the Core.
Considered it? Yes. Plan to do it? No. We DO plan to change QOF
to be based on GObject, but the database itself still needs to just
plug in to the QofBackend API. See lib/libqof/qof/qofbackend*
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
