Status Report

This week I wrote test code for my implementation of Dijkstra's algorithm and fixed a couple of problems with it. I also continued to work on the UI. Unfortunately, I don't think I will be able to have an interactive map, because implementing it will be just to complicated for this project. I think instead I will include a map that the user can scroll around an zoom in and out of using code from the apple website. Then I will have a list of rooms that the user can select from. Obviously this is not ideal, but I know I can write this new UI by the end of the semester.

Status Report

I used Dijkstra's algorithm to find the shortest path between points on the map. However, I am still struggling with an actual visual representation of the map. I will be meeting with Mary Glackin either his week or early next week to discuss which map formats would work better for this project.

I have drawn up some potential screenshots of the app's UI:

The first screen the user would see is the map, with tabs along the bottom to switch between floors. There would also be a button along the top to allow the user to take a photo of one of the QR codes and have the app scan it. Once scanned if the code corresponds to a room in the library that room would be selected. In these drawings a selected room has a red dot in the middle of it.

Once a room has been selected, either by scanning a QR code or by the user touching a room on the map, a second room can be selected by touching the map. Bathrooms and exits will be clearly labeled. As soon as a second room is selected directions will be calculated and displayed. There are two possible ways to display the directions. The directions can be read as a list of scrollable instructions or they can be seen displayed on the map.

Clicking the clear map button would return the user to the first view with no rooms selected. The user would be able to scroll around the map and maybe even zoom in and out.