Talk:GEPS 008: File Organization

From Gramps
Revision as of 11:56, 23 June 2008 by Gburto01 (talk | contribs) (utils)
Jump to: navigation, search


I suggest that we have utils directory (or some similar name) at each level to hold common code that is shared. So for example src/gen/utils, src/gui/utils etc. --Gburto01 12:35, 22 June 2008 (EDT)

I would agree with this. However, I think that a LOT of things that we have under "utils" should actually be their own modules. A "utils" directory is easily misused as a "I'm too lazy to think of a good name and apply proper abstraction" directory. So as long as it is used with caution, I would support it. --pez4brian 15:47, 22 June 2008 (CST)
Class abstraction should take care of most shared code so we should be looking to fit any shared code into the appropriate level in the class inheritance trees. However there will always be some bits of shared code which does not easily find a home unless we invoke some Gramps uber-class from which everything inherits. Perhaps "shared" or "common" would be a better name rather than "utils". --Gburto01 07:56, 23 June 2008 (EDT)


How about src/config (or maybe src/gen/config) for holding the application configuration code? This code is pretty much cross application and I think important enough to warrant it's own location in the directory structure. --Gburto01 12:35, 22 June 2008 (EDT)

Right now, I would really like to see there be only 4 base directories (gen, gui, cli, plugins). I could probably be talked out of this but if we go with that rule, then config would be in src/gen/config. --pez4brian 15:51, 22 June 2008 (CST)

What about Richard Taylor's project ?

Ref. 2007 2008 --romjerome