5aji / beartime-web Goto Github PK

Right now, whenever I pull I have to manually change the frontend API url to localhost:3000/api/week from /api/week. I'm musing, would it be feasible to run the webpack dev server through the existing backend? There's a way to integrate it, and that way, it wouldn't require any changes--that'd be run in unison.

I may not be explaining this clearly enough but it's just an idea

I think we need a way to communicate with our users seamlessly. I was thinking on adding a changelog request to the server which returns some sort of version number and some text. We could store the 'last seen' version is localstorage. Then, we can check for any newer versions, and display them in some sort of modal maybe? After they close the dialog we can update the localstorage "version".

Tristan notes it's very hard to discern the difference between blocks 2 & 3 and 6 & 7. Maybe an 'easter egg' of sorts to apply it?

[Create a theme using colors from the old schedule I have in OneNote?]

Class Bug.zip

@kincaidoneil I know you are aware of this, but bug tracking is important.

So there’s no indication of “passing time” before advisory, or if assembly ends early.

For example, for someone who has College Seminar two days per week and free block the other two.

I'm still working on my mobile app. I need an api. I don't remember what you said about it but there was something (?)

Just a random thought I had: would it be useful to have some custom UI for free blocks? E.g., if I have block 4 free, maybe I can indicate that somehow and then that UI element becomes transparent into the background? Here's a mockup:

(NOTE: not just when a new block begins, when every block ends! i.e., the end of the school day)

It's kinda ugly right now. The font isn't aliasing, there are no highlight modes on things, no transitions, etc.

• Fix fonts
• Highlight + animation for buttons and title
• Make things have a background (Lunch and TASC)
• Transitions. The world needs transitions. It shouldn't be hard. Maybe just put fade or just something.
• Size. Everything is too big.

A couple students couldn't initially figure out that they needed to click the underlined "First" or "Second" to toggle.

Otherwise, there'll be a bug in half day special schedules, as it will all be aligned to the bottom of the page.

Right now, after a certain point, the app renders one column. However, there is so much extra room, so it could render 3. Instead of squishing columns until a certain point, it should squish and then remove one column and repeat until there is one left.

Use a global store such as vue-simple-store?

Now, days can't end later than 3pm, and if all the days in a week end before 3pm, there's going to be empty space at the bottom of the screen. While it's unlikely such a scenario would exist in the foreseeable future, it might be a good idea to future proof it.

Triple clicking BearTime does something cool?
Maybe from 2am-5 BearTime turns into "GO TO SLEEP"?

The code looks alright but isn't leveraging the full power of vue. We should abstract blocks to a vue component, maybe use vue-router to add a settings page and the week stored as a url param. Also it is bad code practice to get every schedule on launch, I still think dynamic-loading is the way to go.

• Use a mixin with vw units for responsive sizing
• Use media queries to hide each day based on .notToday class
• http://www.degordian.com/education/blog/best-practice-for-responsive-typography/