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

From Gramps
Jump to: navigation, search
(utils)
(merge)
 
(6 intermediate revisions by 5 users not shown)
Line 2: Line 2:
 
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)
+
: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)
 +
 
 +
::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". --[[User:Gburto01|Gburto01]] 07:56, 23 June 2008 (EDT)
  
 
== 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)
 +
 +
: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. --[[User:pez4brian|pez4brian]] 15:51, 22 June 2008 (CST)
 +
 +
::I saw config at higher level (src/config) because configuration is something that cuts across functionality from all of the existing four base directories - it's not something that is specific to just gen objects. My view of gen is that it's a place to hold objects that concern the Gramps data model and functionality that directly operates on the data model. --[[User:Gburto01|Gburto01]] 08:10, 23 June 2008 (EDT)
 +
 +
== What about Richard Taylor's project ? ==
 +
Ref.
 +
[http://sourceforge.net/mailarchive/message.php?msg_name=200702012224.09793.rjt-gramps%40thegrindstone.me.uk 2007]
 +
[http://sourceforge.net/mailarchive/message.php?msg_name=47BC0F8B.3060108%40thegrindstone.me.uk 2008]
 +
--[[User:romjerome|romjerome]]
 +
 +
== merge ==
 +
Shouldn't be merge under /gen and the relevant gui under /gui/editor, /gui/view or wherever appropriate? --[[User:Zfoldvari|Zfoldvari]] 14:02, 23 June 2008 (EDT)
 +
 +
:Agreed. It could also be controlled from the command line, in theory. --[[User:Gburto01|Gburto01]] 15:18, 23 June 2008 (EDT)

Latest revision as of 12:18, 23 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)
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)

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)

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)
I saw config at higher level (src/config) because configuration is something that cuts across functionality from all of the existing four base directories - it's not something that is specific to just gen objects. My view of gen is that it's a place to hold objects that concern the Gramps data model and functionality that directly operates on the data model. --Gburto01 08:10, 23 June 2008 (EDT)

What about Richard Taylor's project ?

Ref. 2007 2008 --romjerome

merge

Shouldn't be merge under /gen and the relevant gui under /gui/editor, /gui/view or wherever appropriate? --Zfoldvari 14:02, 23 June 2008 (EDT)

Agreed. It could also be controlled from the command line, in theory. --Gburto01 15:18, 23 June 2008 (EDT)