Closed kyleoliveira closed 8 years ago
I think this would actually be better to do before #34 because it would be easier to integrate the charting library in this step without the dynamic requirements of doing the full dashboard.
Once this is in place, we'd basically use this display has an initial state for the dashboard and plot a line or something over it to show actual progress. Subsequently, consider creating the actual display functionality as a partial.
Also, if it makes more sense to drop the modal display of the schedule and instead change the link so it sends the user to the Schedule #show page, go for it. Depending on how the loading for these chart libraries works, I could see where keeping the modal might kill loading time on the Schedule index page since all content in the modal is actually loaded as part of the page. Just something to consider...
Resolved by #87
Probably related to/holds until #34 , but we need a better way to visualize the Tasks in the Schedule. The current implementation was born out of necessity / lack of time. It gets the job done, but it ain't pretty.
We should implement a timeline graph showing the progression of the Schedule and where each Task comes in. Refer to systems design docs and team discussions for ideas.