Monday, September 30, 2013

Emails with Client



Daniel Turkington (who is the POC for our development questions) addressed a few of the concerns we were having about the project. We were wondering if we needed a certificate in order to install onto the device but Daniel said that the fls file contains a developer certificate which contains all the MAC addresses of development machines. Therefore he believes that we shouldn't have any problems with building the application in that respect.




Daniel also showed us how to access the printer log by
1. Type "<printer ip address>/se" in your browser
2. Click "Embedded Solutions"
3. Click "Log File"


We still need to have the OAuth issue addressed about needing to log in with a browser on the device despite not having a browser. I did just now find this document https://developers.google.com/accounts/docs/OAuth2ForDevices. 

 The document states that for a printer device we will have to display a url for the user to navigate to on a device with a browser and they will have to put in the user code that we provide. Once they have done this, our application will have to poll the endpoint to see when the user has allowed the app access to their calendar. We will need to store the the access token as well as the refresh token.  The access token expires after a given amount of time so we will need to check the validity of the access token and use the refresh token if the access token has expired.

Sunday, September 29, 2013

Architecture Assignment Meeting

Today Gavin, Daniel, and I met to discuss and complete the architecture assignement.  Gavin address a huge concern that he was having about authentication.  Apparently OAuth authentication with google requires that a user login to Google through a browser after which an authentication token will be created and passed back to the application.  The problem is that as far as we know, the printer doesn't have a browser and thus OAuth may not be possible.  If it's not possible then we will either have to access public browsers or figure out a different means of authentication.

We started out the meeting discussing the user stories and we built up a high level overview from this.  From there we fleshed out a fairly comprehensive class diagram over the course of the next 2 hours.  Some major design points that we discussed was adding interfaces for the Google Calendar Service as well as the Google Authentication Manager which are CalendarService and AuthenticationManager respectively.  The reason we did this was to allow for other calendar services to be plugged into  the AppController without requiring modification to it's logic.

We also decided on implementing an MVC architecture so that we could keep the business logic separate from the view.

As of now we are also unsure of another major design decision which has to do with multi-threading.  We are not positive what facilities are available to us for multithreading but we feel it will be necessary as we are hoping to show a short dialog during printing and sending an email and having a callback being invoked when they complete, however we don't want to block as the user may still want to look through the different meetings for that day while the email is sending or while printing.

Authentication Problem
Spawning a new thread for printing.

Preparation for Group Architecture Meeting Tomorrow

Saturday September 28, 2013

Our team has a scheduled meeting tomorrow to discuss and finish the Architecture Assignment.  I have already begun exploring the SDK to get a feel of what our major components will be.  Daniel Turkington had explained in the initial meeting that our development would have to center around an OSGi based system for our code modules.  So today I learned about the basics of OSGi and the main concepts that would be useful.

OSGi as I understand it will involve bundling our package files into a jar file with some extra metadata which will contain such information as the modules interface, the modules dependencies, and what services the module provides.


Tuesday, September 17, 2013

Initial meeting with Lexmark

Yesterday, Gavin and I had our requirements workshop with Lexmark.  Jason explained the app in very good detail and provided us with a spec sheet that served as a foundation for a long conversation which went on to answer many of the questions and concerns we had.

Daniel (the developer) explained how the development workflow would be going as far as testing and running the app and also provided us with the sdk zip file so that we could start exploring it.  We will basically be VNCing into the the printer remotely and will be able to run our app that way after uploading it on to the printer via ftp.

We will be having weekly meetings with Shaun Love on Tuesdays at 6pm via Skype to discuss the project.

Jason explained some of the technologies that we would be needing to get familiar with including ActionScript for the Flash UI development and told us that we would be needing to get used to developing for a 1.3 JRE which doesn't include a lot of the things most developers expect out of Java like Generics, enums, etc...

Here is a list of topics that were discussed in the meeting which spanned about 90 minutes.

  • sdk zip file
  • vnc into machine remotely (one at a time)
  • ftp application files directly onto the printer
  • talked about double bookings
  • discussed what happens when you get out of a meeting early (what if a meeting gets cancelled), still concerned about what will happen if you get out of a meeting early, how will it know what to display.
  • Action Script (Flash) to program the UI and Java for nonUI components however only have a 1.3 jre to work with so no generics, enums, etc.
  • Shaun Love wants for us to take a tour of the facility and meet developers in the near future and take us out to dinner.
  • Skype
  • Schedule weekly skype meeting time with shaun
  • Still need better grasp of what the lexmark design guidelines are
  • OAuth authentication
  • OSGi bundles ???
  • Show Agenda 
  • Print out Agenda for rest of day
  • Print a map of meeting location
  • User is able to configure the number of minutes til meeting that shows yellow, green, and red.