title: Making bootstrap calendar render when data change in meteor
body: <p>I'm still struggling to get a calendar to re-render when data changes using meteor blaze. I have put in place an observerChanges function that is firing happily when added, removed or changed are triggered, but I have NO idea how to actually make the calendar update its state.</p>
  
  <p>The handler code is </p>
  
  <p>Meteor.subscribe("reqEvents");</p>
  
  <p>allReqsCursor = Requests.find();</p>
  
  <pre><code>var handle = allReqsCursor.observeChanges({
    added: function (id, user) {
      console.log("Request added");
    },
    removed: function () {
      console.log("Request removed");
    },
    changed: function() {
      console.log("Request changed");
  //    $('#calendar').fullCalendar().today();
    }
  });
  </code></pre>
  
  <p>And the render function itself is</p>
  
  <pre><code>Template.packLayout.rendered = function(){
    $('#calendar').fullCalendar({
      //dayClick:function( date, allDay, jsEvent, view ) {
      //  Requests.insert({title:'Request',start:date,end:date,color:'red',className:'todo'});
      //  Session.set('lastMod',new Date());
      //},
      eventClick:function(reqEvent,jsEvent,view){
        Session.set('editingReqEvent',reqEvent.id);
        Session.set('showEditEvent',true);
      },
      eventDrop:function(reqEvent){
        Requests.update(reqEvent.id, {$set: {start:reqEvent.start,end:reqEvent.end}});
        Session.set('lastMod',new Date());
      },
      events: function(start, end, callback) {
        var events = [];
        reqEvents = Requests.find();
        reqEvents.forEach(function(evt){
          event = {id:evt._id,title:evt.title,start:evt.start,end:evt.end,color:evt.color};
          events.push(event);
        })
        callback(events);
      },
      editable:true,
      weekMode: 'liquid',
    });
  };
  </code></pre>
  
  <p>How do I hook these together? I've tried a few things (as per the commented out code) but it either blows up or renders the calendar twice.</p>
  
  <p>Is this even the best way? Should I put a deps.autorun in somewhere else?? If so where?</p>