Integrate the Desktop Notifications API into the site.

• Notify tutors if students enroll in their session
• Remind tutors/tutees when their tutoring session starts (Session starts in 15 minutes at location).
• Integrate with chat messages

It would be nice to have an array of predefined colors the user can select (generic green, blue, yellow, etc.) and allow the user to add their own custom colors (may work nicely with the eyedropper tool).

For the session/chat/whiteboard, we need permissions. This will determine who can read, write, or anything in between. It would be nice to have a permissions system inspired by Google Docs.

Permission Modes

1. Private - Nobody can access this item except the owner.
2. Public - Anybody logged in can view the session/chat/whiteboard. It is publicly listed. Have the option for people logged out (anonymous users) to access as well.
3. Unlisted - Session/chat/whiteboard is hidden from the public. Only specific people with a generated link can view the item. Have the option for people logged out (anonymous users) to access as well.

Within each "mode," the owner can decide whether the group can read/write. (Ex. Everyone with shareable link can edit the whiteboard, or anonymous people can only read the whiteboard.)

All of these permissions can be overwritten by the owner, who can manually add people to the session/chat/whiteboard, and specify their permissions. (Ex. [email protected] can write on the whiteboard).

Scopes

It would probably be best to setup the permissions in a flexible 'scopes' system, which can be used to give a user any mix of permissions. The basic permissions should be something like:

• read - User who has the read scope can view the component.
• write - User who has the write scope can edit basic things (add markings to whiteboard, send message in chat).
• moderator - This possible scope may not be applicable to all components, but could allow a user to have more permissions than the regular person (Invite other people to the whiteboard/chat, possibly even change permissions?)

These scopes are just general guides. You can split these scopes up, remove some, or add other scopes that may be applicable to a specific component. The owner should automatically have permissions of all the scopes, and the owner may not remove any of their permissions.

Ability to add text and transform it

Add a tool that allows for the creation of basic shapes (squares, circles, ovals, etc.)

permission denied at ./ error from firebase when trying to directly access /session/:id or /scheduling and possibly other pages, but after re-navigating to the component the error is gone and data is returned normally.

Paper.js has a helpful .bounds property, which stretches a path to fit a rectangle. When the shift key is pressed, the shape should maintain its original aspect ratio (square if polygon, circle if ellipse, etc.) The .fitBounds() method may come in handy.

Have an eye dropper tool to grab the color of an existing object on the whiteboard. If the user selects the center of an object, it should grab the fill color. If the user selects the side of an object, it should grab the stroke color. It would also be nice to grab the background color if it is selected.

Wrap the whiteboard in an Angular Component that can easily be deployed across the platform

Create an eraser tool that can hide markings from the whiteboard display

Have a "$user joined" and "$user left" when a user joins or leaves a chatroom. If the user is not logged in, it should probably say "An anonymous user joined" and "An anonymous user left".

pagination when displaying sessions and other stuff

Make the app mobile-friendly

Use Firebase to provide instant messaging.

Something like a click and drag box which would select all the markings/shapes in that area. Allow for markings/shapes to be moved, allow shape dimensions to be changed, etc.

Allow for peer tutoring sessions to occur at specific intervals (Ex. A tutor and tutee meet every Wednesday after school, etc.) Also allow these session intervals to be cancelled permanently or possibly temporarily (if a user goes on vacation or something? sick?)

Allow tutors and tutees to input times they are available, and suggest pairs based on these free times. Allow the user to input their available times per week day (when they're free Monday, Tuesday, etc.) or possibly by MICDS schedule day rotation (Day 1, Day 2... Day 6) or possibly both (every Wednesday, Day 3).

When week view is opened in the session-calendar component, ngonchanges, which is originally only listening to changes in the 'session' @input for the component, starts to listen to all of the mouse move and scrolling events, calling ngOnChanges() handler in the component.