So whilst you were tinkering away on the backends, I was perfecting our calendar UI.
Bad news: it's still not perfect
Good news: the framework for most anything we want to do is in place!
That means (some of these aren't completely implemented):
automatic adjustment of overlapping calendar events (check out css :nth-of-type — it's not as convenient as it seems)
If we hover on a feed item, that item lights up in the calendar.
Click on a calendar item, and a nice popover shows.
Click on another cal-item and the first popover goes away and a second one shows (NOT TRIVIAL that fuckin bitch took me like half an hour)
Show, hide any calendar events (i'm imagining the checkboxes on YBB worksheet) through categories or organizations, and the view automatically updates (UNLIKE WHAT YALE DID TO YBB THOSE FUCKERS)
a Gandalf.dispatcher event dispatcher so that we can communicate through views! (in gandalf.coffee)
Still to do:
Rendering events that span multiple days (both in the feed and calendar -- we should talk about that)
Persistant hiding and showing of events (this will be more useful in browse, but should exist in the personal calendar too). this involves interaction wtih the "subscription" model, which i've been dreading, so we should talk about that too.
In addition, I refactored some more of the code. it's important, i think, for organization and standardization that we keep a @model or @collection in each View. Also, instead of passing lots of variables between view events, i made the variables that didn't change often into class variables.
That's a wrap.
Your code was awesome, but it didn't work on my computer—did you have instructions for what I need to do?
So whilst you were tinkering away on the backends, I was perfecting our calendar UI.
Bad news: it's still not perfect
Good news: the framework for most anything we want to do is in place!
That means (some of these aren't completely implemented):
Gandalf.dispatcher
event dispatcher so that we can communicate through views! (in gandalf.coffee)Still to do:
In addition, I refactored some more of the code. it's important, i think, for organization and standardization that we keep a
@model
or@collection
in each View. Also, instead of passing lots of variables between view events, i made the variables that didn't change often into class variables.That's a wrap.
Your code was awesome, but it didn't work on my computer—did you have instructions for what I need to do?