Difference between revisions of "Talk:GEPS 008: File Organization"

From Gramps
Jump to: navigation, search
(Some initial comments)
 
(utils)
Line 1: Line 1:
 
== utils ==
 
== utils ==
 
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. --[[User:Gburto01|Gburto01]] 12:35, 22 June 2008 (EDT)
 
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. --[[User:Gburto01|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. --[[User:pez4brian|pez4brian]] 15:47, 22 June 2008 (CST)
  
 
== config ==
 
== config ==
 
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. --[[User:Gburto01|Gburto01]] 12:35, 22 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. --[[User:Gburto01|Gburto01]] 12:35, 22 June 2008 (EDT)

Revision as of 13:48, 22 June 2008

utils

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)

config

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)