Source directory restructuring
bhardwajs at gmail.com
Mon Aug 7 11:46:06 EDT 2017
This sounds like a great plan to me. It will definitely make understanding
the code easier than the current state.
On Mon, Aug 7, 2017 at 7:23 AM, Derek Atkins <warlord at mit.edu> wrote:
> Sounds like a great plan to me!!!
> Geert Janssens <geert.gnucash at kobaltwit.be> writes:
> > So after my houskeeping message in which I have announced the changes to
> > business and src/libqof, I'd like to bring up my eventual goal for the
> > tree.
> > My main motivation to do all this restructuring is to simplify. There are
> > currently plenty of directories and I often have to guess where to
> expect a
> > file. The qof vs engine story was one example. Is gnc-date something for
> > or for engine ? I find myself regularly searching for a file in the wrong
> > directory.
> > So here follows a first proposal for the directory structure I'm
> > * data (for things like art, checks, account hierarchy templates,...)
> > * doc (for all documenation)
> > * lib (for all source required to build "libgnucash", see below)
> > * ui (for all the user interfaces the project currently supports)
> > I am omitting some smaller directories here, such as util and macros.
> > will probably stay on the current top level for now.
> > I'm envisioning "libgnucash" as the core library that encapsulates all
> > related concepts (the accounting concepts such as transaction, split, as
> > as the data backends). This library is what all applications in the
> > sphere should depend on to implement the "gnucash" experience. The most
> > obvious is of course the current gnucash as we know it. However at some
> > this library should ideally also become the core of the Android app and
> > knows* one day an IOS app. And closer to the current state, it should
> also be
> > the library that the guile and python bindings depend on. So all
> > encapsulated in one single library, the API. In practice I think the
> > directories belong in this libgnucash: core-utils, gnc-module, engine,
> > backends, app-utils. (Note I would like to get rid of gnc-module still,
> > that's a whole other discussion and task).
> > The ui directory will have a subdirectory for each user interface we
> > This is not necessarily a *graphical* user interface though. At this
> > there are already a number of them:
> > gnucash
> > cutecash
> > bindings (with subdirectories for python and guile)
> > The bulk of the other directories are support directories for one of the
> > and I propose to make them subdirectories of each respective ui.
> > For example gtkmm is only used by cutecash, so let's store it there
> > another ui would also require it, which I consider unlikely to happen
> > The other directories (gnome-utils, gnome-search, gnome, register, html,
> > report, import-export,...) are all used only in the gnucash application
> > hence should be moved there. In the move I'd like to try and reduce the 3
> > gnome* directories to one and call it gtk as we're not using any gnome
> > specific technology any more.
> > In a later phase I think it would be nice if the core libgnucash could
> > spit out html reports, but that would require us to refactor the report
> > modules, which I consider too much work to be done at the same time.
> When this
> > eventually gets done the non-ui part of the report system can then be
> added in
> > libgnucash to the benefit of all consumers (gnucash/cutecash/Gnc4Android/
> > Feedback or questions ?
> > Geert
> > _______________________________________________
> > gnucash-devel mailing list
> > gnucash-devel at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 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
> warlord at MIT.EDU PGP key available
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
More information about the gnucash-devel