carthage webdev

One of the only problems that has slowed us down while developing our CMS has been the steep learning curve associated with changing some functionality in the built-in admin without writing it as a custom view. This problem reared its head again when I was building the score module which essentially extends our calendar module (i.e., some calendar events happen to be athletic competitions, and athletic competitions have additional information like scores, etc.) The way we have laid things out, creating a score happens on its own page (separate from the main calendar editing page) and involves selecting the calendar item to establish the foreign key relationship between the score and calendar item. The problem was that the list of calendar items was too long – at best I could filter it so that it would only display sporting events, but I really needed to filter one step further to the specific sport.
(more…)