Closed shankari closed 1 year ago
When a user jumps to a date from a year ago, are we allowing them to scroll up and down? I don't believe so, so therefore when they select a date, it just displays that date's trips, correct?
That is not what I assumed. So you are saying that if the user selects a date, they only get to see data for that date? But otherwise, they can scroll up and down?
That does not seem like a great user experience. If we allow people to "infinite scroll", they will assume that they can scroll all the time. I recall you saying that you want to remove the buttons near the calendar date selector because people will just scroll. Without scrolling, we run into all the original issues about knowing which dates actually have data and so on.
Closing this given that we have merged @tyleryandt18's changes and now have a label screen that is fairly close to the diary and opening https://github.com/e-mission/e-mission-docs/issues/902 for the pending changes.
www/js/diary
andwww/templates/diary
list.js
andlist.html
inf_scroll.js
andinf_scroll.html
In angular1, the UI is in
.html
and the javascript controlling the UI is in.js
in a type of class called acontroller
The functionality in both of them is almost the same. Our goal is to modularize and unify the two so that we have one codebase and the users have one place to go do label trips.