Justas, I followed your suggestions and created the score system container off of the application root. Also, I created the generations package in schooltool.requirement and put the first evolve script there. The new branch I pushed, lp:~aelkner/schooltool.gradebook/requirement_scoresystems, is a lot easier to follow than the last one because I didn't need to move any of the views or tests. I only had to make the appropriate changes to remove the use of the ScoreSystemsProxy.
Please review my branch for the upcoming meeting. Thanks, Alan On Thu, Apr 28, 2011 at 11:34 AM, Justas <[email protected]> wrote: > Hi Alan, > > A short note, continuing on discussion > http://schooltool.pov.lt/irclogs/%23schooltool.2011-04-27.log.html#t2011-04-27T17:33:26 > > I think there is no need for a "RequirementRoot". Please create > ScoreSystems, a new container class for score systems and put an instance in > app["schooltool.requirement.scoresystem_container"]. > > If the need arises to, say, store some settings or such in the future, we > can put a persistent settings object in > app["schooltool.requirement_settings"] for example. > > Evolution... I think we can introduce generations schema manager for > schooltool.requirement and do the evolution there. > > As for the database startup... I'd rather look into that after vacation. > Once you're done, please re-assign the bug to me. > > Justas > > > _______________________________________________ > Mailing list: https://launchpad.net/~schooltool-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~schooltool-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~schooltool-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~schooltool-developers More help : https://help.launchpad.net/ListHelp
