Friday, March 31, 2017¶

Implement milestones as activities¶

I did #1546 (Use courses.Course as milestone_model). This is a great example of how flexible Lino applications are.

Some days ago I added the courses and cal plugins into Lino Noi. That was for my quick demo last Saturday for Lino Vilma. This made me realize that an “activity” (AKA “course” or “workshop”) in lino_xl.lib.courses is equivalent to what we have been calling a milestone until now. And that the “room” of the calendar module is equivalent to what we called a “site” until now.

So now I removed the models deploy.Milestone and tickets.Site. Existing deploy.Milestone objects must be migrated to courses.Course, existing tickets.Site to cal.Room.

I also removed tickets.Competence because that notion is not useful. Existing rows can be thrown away. Note that I plan to change the verbose_name of tickets.Project from “project” to “mission”.

Side effect I stumbled over a little bug which caused a TypeError: unorderable types: str() and <type 'str'>. And I fixed it.