Page History

...

• Calendar View: Posters are displayed by week and users can either scroll to a week or select it off a calendar.

     Image Removed

  ...

  • •   Calendar View:  Image Added
  • Similar Events View: Posters are grouped by tags event organizers assign to them (e.g. talk, social etc). Posters with multiple tags are placed in multiple categories. Clicking on a tag allows users to browse events in that category. This functionality circumvents the need to need to have an explicit search button which would require typing and our studies show that typing on a vertical surface is very tedious.
    •  Similar View : 
    • Browse Tag Category:  
  • Add poster view: We implemented a slide-in panel for adding posters where the user can select a poster file, event date and time, and tags. These selections require no typing, they are accomplished through calendar widgets and drop downs. Similarly for entering email, we prompt the user to swipe their id at the RFID reader and auto-populate the email field.
    • Add View: 
  • Detailed view: When a poster is clicked on (in the calendar or similar events view), the poster is focused and the user is able to scribble on it, change scribbling color, view previous scribbles, continue a previous scribble, like/dislike a poster, get a reminder for the event by swiping an RFID card and delete the poster, also by swiping a card.
    • Detailed View Example 1: 
      Detailed View Example 2: 
      Send email reminder functionality: 

  ...

  We forwent using QR codes for adding an event to a user's calendar settling instead for sending an email reminder to the user on swiping their RFID card. * ** event organizers didn't want to create them either * **

  One of the users could not find the button to select the poster file so we made sure that the button was clearly set apart with a sufficient color contrast

  ...

  We also contemplated saving the sketches as the user sketched instead of waiting till the user was done sketching but that approach was more bug-prone and given the time limitations, we opted for the less bug-prone approach of saving when the user clicked the Save button.

  ** * Need to talk about how we used RFID reader to remove need for typing ***

  - the actual board was not functional until the week before GR5 was due. It was missing a crucial connecting cable to allow the smart board to communicate with the computer. After several tens of hours of conversations with Customer Service and three sets of incorrect cables, we finally got the board working. So resolution, fit to big screen cow;don't happen very well.

  ...

  The project turned out to be much more hardware focused than we expected since our application was heavily dependent and limited by the SmartBoard and RFID equipment. As mentioned above, the SmartBoard was not fully functional until the last week of classes.

  ** * talk about personalization: possibilities, why we didn't do it. How would we do it * **