MyTimetable 2.4 is currently in the state: stable. These release notes are work in progress, and planned features may change at any time. MyTimetable 2.4 is tracked using the git branch: rb-2.4.
MyTimetable 2.4 will focus on redesigning the database backend in order to be able to use multiple databases at the same time and implement a new backend provider to show activities retrieved from a custom database table. This document gives an overview of the planned features, but please keep in mind that planned features may be delayed or cancelled at any time.
Functional changes
- Multiple database support — MyTimetable will be able to read from multiple databases at the same time, and will be able to transparently merge these databases. The user will only have to choose the appropriate database when adding a new timetable subscription.
- Custom activity support — A new backend type will be added that gives customers the ability to add custom activities that will be retrieved from a custom database table. All-day activities will also be supported.
- Replaced department filter by posdepartment filter by default — Due to this, filtering of module and studentset listings will better match the expected behaviour; modules/student sets in search results now should match either the department directly, or the department through their pos (formerly the latter scenario was not included, leading to missing results when filtering on both pos and student set).
The following changes have been made to the MyTimetable backend and underlying software, and have no direct impact on MyTimetable functionality:
None as of yet.
Removed and deprecated features
The following features from earlier MyTimetable versions have been deprecated, removed, or partially removed and are not supported anymore:
None as of yet.