Export Schedule to JSON

[davilima6]

As discussed with @turicas on IM, it'd be nice to export the schedule in a developer-friendly way, in a format such as JSON. Moreover, if the JSON scheme could be implemented based on the following examples [1] [2], it'd be immediately possible to have a jQuery Mobile interface to serve PythonBrasil schedule. I'm talking about the Clips project, a Django-based web app launched last FISL with lots of help from @tarsis @douglas and @willemarcel

[1] https://raw.github.com/willemarcel/gradefisl/master/public/json/data.json
[2] https://github.com/douglas/fiscrapping/blob/master/README.mkd#o-que-eu-fa%C3%A7o-com-esses-arquivos-

There's good test coverage for Clips so I invite you to help implement features like HTML5 offline storage and somekind of notifications or alarms (not sure if possible without going native). See our issues: https://github.com/willemarcel/gradefisl/issues

[turicas]

@davilima6, did you write any test that checks consistency of JSON? It can help us when implementing this feature.

[davilima6]

@turicas: Does this help? https://github.com/willemarcel/gradefisl/blob/master/grade/tests.py

[davilima6]

@turicas Since Guidebook will be the official app for PythonBrasil 2012, I'd like to know if you're still interested in implementing this issue.

[turicas]

@davilima6, yes! There is no problem in having more than one system. I'll update this issue when I implement the schedule with all talks/days/hours.

[davilima6]

Great, @turicas I also think there's no problem having two apps available, some competition should be good =)

BTW, Guidebook is an excellent and mature choice, we used it in the last two PloneConfs. We can only hope that Clips turns into an equivalent Python opensource alternative in the near future.

[turicas]

@davilima6, sorry for not implementing it. I didn't have time to do it (actually, we didn't update the database with dates/hours of each talk -- it was dony manually).
I'm closing this issue since it does not make sense anymore.

[davilima6]

I think that if there are any plans to reuse this codebase for future conferences, it does make sense to keep the issue open.