I think the best approach would be to ship a series of .lernid files that outline how to get connected to an event but then the event name is in the ical description.
So as an example, we could ship this .lernid file:
When Lernid starts it would present the different classrooms to connect to (read from the .lernid files), the user selects a classroom, and then Lernid processes all of the events and groups together events with the same Event name.
This approach would rely on classroom sessions having the exact same event name, but I think this is reasonable, and it would allow Lernid to not need to be patched. This solution does not include start and end dates for the events, but I am not sure if that is such a big deal.
I think the best approach would be to ship a series of .lernid files that outline how to get connected to an event but then the event name is in the ical description.
So as an example, we could ship this .lernid file:
[Ubuntu Classroom] url.to/ classroom. ical /wiki.ubuntu. com/UbuntuClass room classroom- chat
icalurl: http://
homepage: https:/
classroom: ubuntu-classroom
chat: ubuntu-
but then for each event in the description there would be:
[EVENT: Ubuntu Open Week] jonobacon. org/files/ presentation. pdf]
[SLIDES: http://
When Lernid starts it would present the different classrooms to connect to (read from the .lernid files), the user selects a classroom, and then Lernid processes all of the events and groups together events with the same Event name.
This approach would rely on classroom sessions having the exact same event name, but I think this is reasonable, and it would allow Lernid to not need to be patched. This solution does not include start and end dates for the events, but I am not sure if that is such a big deal.