Week of May 22-26

We've been working on finishing touches to our app and are almost done with all functionality other than the backend, which we were unable to get working.  Steven was able to get the search bar working which allows users to search for specific items.  Whit coded the checkout and settings pages to allow users to set their names, passwords and student IDs so they could be identified when they order.  For the checkout page, the items from the cart transfer over so the cost is successfully calculated even though users are not on the cart page.  Cart also successfully works so that users are able to add items from the menus to the cart from the menu page, rather than doing it manually through the console.  We also added menus for subway, marias and starbucks in addition to Belwood so that users are able to use more than one restaurant.

Tuesday, May 23

Today we continued to work on the UI behind the main delivery and pickup screens. As mentioned earlier, we faced troubles working with DataGrids and so we totally changed the direction of the organization of our objects and scripts. Rather than having essentially an array of objects which could be manipulated easier, we now have tons of individual objects which we will have to change and manipulate individually. Nonetheless, this approach is still 100% valid, the main difference is repeating code. We also spoke a little bit about the login screen and decided that while the online-universal functionality will not be active, we are going to allow users to input their information and we will save under their name and information the orders that they place or deliveries that they have accepted. Below is a screenshot of our incomplete UI for the main pickup screen.

Wednesday, May 17

During the block we worked on the various interactive screens for storing data.  Stephen worked on the page that displays orders that can be accepted.  Anacan worked on the menu page where items can be selected for the final order.  In the class, we decided to use data-grids to store our data for consistency in each item and easier coding (though this later turned out to not be the case), which meant Stephen and Anacan had to redo parts of their screens.  Whit worked on coding the cart page and finished the functions for adding and deleting items from the cart, as well as automatically updating the total price.

Friday May 19th

On Friday we were completely finished the UI of the main delivery and pickup screens, and we focused on inputting functions and storing data. We decided to use data grids to display the rows of pickups and orders; however, we faced countless problems making the data grids functional. Our primary reason for using data grids in the first place was so that we wouldn't need to repeat code for the multiple orders or deliveries that would appear on the main screen. We tried using the CLOCK LiveCode tutorial, which incorporates DataGrids to educate ourselves on how DataGrids are used and actually learn the steps to using them. After lots of time and struggling, we decided that DataGrids may not be the best model for storing deliveries and orders that we want, and we thus decided to move on and find other ways to do so.

Monday, May 15

Today in class we gave up on the idea of backending accounts (usernames and passwords) because LiveCode simply would not allow it. Steven continued to gruelingly work on the Deliver Page, having to create tons of boxes which we now have got to scroll. Anacan and Whit both worked more on the order page, starting to create individual menus and the cart page.

Friday, May 12

In class, We were struggling to get a scrollable group to display for list of restaurants in the village. Steven and Anacan both tried working with data groups and multiple other options in LiveCode, to no avail. Finally, Anacan figured out exactly how to get it to scroll, by limiting the group size but keeping the images locked. This allows me to have a group of scrollable images and labels, each of which are separately clickable. Whit has been working on usernames in passwords, and today he finally broke through the errors he has been having. He is creating a proxy server for the backend part of the program, since LiveCode has been unable to help him.

these images show the scrolling feature that Anacan added

Thursday, May 4

Today we presented our Moqups wireframes to Mr. Kim who helped pick apart new details and screens for our app. For example, we had included a screen that allows people to "view orders," however, we lacked a screen with the same functionality for the delivery people. This is a key function of the app so that users can view their future deliveries that they have taken on and will not forget when the time comes. This will also lead us to send notification updates about future deliveries. In addition to presenting to Mr. Kim, our team also began working on building the UI in LiveCode. We split up the initial work by have Anacan work on UI for the order-users, Steven work on UI for the delivery-users and Whit research the steps we need to go through to allow user accounts.
I have included images of how the splash screens look in LiveCode.

Tuesday, May 2

We started the wire-framing of our app today and we chose to use Moqups as it was simple, easy-to-use, and allowed you to add separate pages and input an iPhone image to work on. We created a list of pages that we needed to make and along the way we added extra features and screens to accommodate different functions of the app. For the loading screen, we put the title of the app, EagleMates, and found a cool GIF of an Eagle flapping its wings. After the app loads up, the users are given a splash screen where they can choose between "Order" and "Pickup." They are also given the option to press an "Info" button in the top corner which will dim the screen and provide descriptions for the purpose of each option.
Below I have included a list of all the screens that we came up with
- Loading
- Splash Screen
- Splash Screen Info
- Order Main
- Restaurant Page
- Restaurant Order
- Confirm Order
- View My Orders
- Delivery Main
- Order Summary

I have attached also attached a picture of our primitive Order Main page design-



We have decided to use a light color scheme with hints of navy. In addition, we used Courier font and built in icons from Moqups.