The second are just the changes you made the other day.
The third commit is the major change I would like to contribute. Previously you had the api urls hardcoded in the js. I added names to the regular views and in the room.template.html file I created global variables for each view and resource by reversing the url. This will make it more flexible to use the bigboard js code in locations other than the main view and allows the views to be accessed easily from any template or view without hardcoding the url. I modified all the urls in bigboard_mainloop.js to use these global variables and it seems to work just fine.
Now to use bigboard_mainloop.js users will either hsve to hardcode the urls in their script or do as I have done for the room template.
The first commit was to solve errors I was having with spatialite for my development version needing GeoManger objects (https://docs.djangoproject.com/en/dev/ref/contrib/gis/model-api/#geomanager).
The second are just the changes you made the other day.
The third commit is the major change I would like to contribute. Previously you had the api urls hardcoded in the js. I added names to the regular views and in the room.template.html file I created global variables for each view and resource by reversing the url. This will make it more flexible to use the bigboard js code in locations other than the main view and allows the views to be accessed easily from any template or view without hardcoding the url. I modified all the urls in bigboard_mainloop.js to use these global variables and it seems to work just fine.
Now to use bigboard_mainloop.js users will either hsve to hardcode the urls in their script or do as I have done for the room template.