From: Brian M. <br...@gr...> - 2009-01-16 16:24:11
|
I've added support for sub-directories in the plugins directory. I'm going to start incrementally moving plugins into their respective subdirectory. So watch out for files moving around if you are editing them. File files may take longer to move than others. For a time, some files will not be orgainzed. So if you have a particular file that you would like to stay put for a while, let me know. ~Brian |
From: Douglas S. B. <db...@cs...> - 2009-01-16 16:36:13
|
Brian Matherly wrote: > I've added support for sub-directories in the plugins directory. > > I'm going to start incrementally moving plugins into their respective > subdirectory. So watch out for files moving around if you are editing > them. > > File files may take longer to move than others. For a time, some > files will not be orgainzed. So if you have a particular file that > you would like to stay put for a while, let me know. Great, thanks Brian! This will make managing things much easier, especially for those that are just getting familiar with GRAMPS. I'll split DefaultGramplets.py so that each is in its own file, once you have the directory structure set. We can save the Makefile.ams and POTFILES changes the last item to change, since there will be many changes. In fact, if there are widespread changes to Gramplets, I can take care of those changes; just send me a note if there is something specific that you want. -Doug > ~Brian |
From: Brian M. <br...@gr...> - 2009-01-16 16:54:33
|
> > I've added support for sub-directories in the > plugins directory. > > > > I'm going to start incrementally moving plugins > into their respective > > subdirectory. So watch out for files moving around if > you are editing > > them. > > > > File files may take longer to move than others. For a > time, some > > files will not be orgainzed. So if you have a > particular file that > > you would like to stay put for a while, let me know. > > Great, thanks Brian! This will make managing things much > easier, especially for those that are just getting familiar > with GRAMPS. > > I'll split DefaultGramplets.py so that each is in its > own file, once you have the directory structure set. We can > save the Makefile.ams and POTFILES changes the last item to > change, since there will be many changes. The directory structure is already in place. I didn't make the "common" subdirectory because I'm not sure if we will make a "common" directory, or if common code should go in PluginUtils. I plan on crossing that bridge when I come to it. I just made the first commit that moves the relationship calculators into plugins/rel. I edited the Makefile.am and POTFILES, so I'll probably just keep changing them as I go. > In fact, if there are widespread changes to Gramplets, I > can take care of those changes; just send me a note if there > is something specific that you want. Would you object to being in charge of moving all the Gramplets into the gramplet subdirectory? This isn't terribly urgent, so you can do it at your leisure. Thanks, ~Brian |
From: Benny M. <ben...@gm...> - 2009-01-17 08:19:10
|
2009/1/16 Brian Matherly <br...@gr...> > > > In fact, if there are widespread changes to Gramplets, I > > can take care of those changes; just send me a note if there > > is something specific that you want. > > Would you object to being in charge of moving all the Gramplets into the > gramplet subdirectory? This isn't terribly urgent, so you can do it at your > leisure. > I suggest you guys start with the case of the records gramplet and records report that are in the same file to find a good solution of the problem of common code bases. Benny |
From: Brian M. <br...@gr...> - 2009-01-17 12:33:58
|
> I suggest you guys start with the case of the records > gramplet and records > report that are in the same file to find a good solution of > the problem of > common code bases. My strategy has been to move all the files that don't share anything. Then, I'll take the other files one by one so I can handle each one on a case by case basis. records.py hasn't been moved yet because, as you mention, it has shared code. ~Brian |