Weekly Update (2017-01-26): Liam

This Week

I spent most of my time allowing the user to interact with the airplanes in the app. Benjamin and I implemented a system to select airplanes, and I worked on making the camera follow the selected airplane. I also made the airplane control buttons appear when an airplane is selected and disappear when it is deselected. I also made sure UI elements were density-independent.

This is the game initially:

And this is the game when an airplane is selected:

Completed Asana Tasks:

• Remove unused branches
• Add airplane selection system
• Implement plane movement
• Make UI elements density independent
• Refactor with singleton

Next Week

Next week I plan on making the game a lot more playable. I'm going to implement a lot of user controls for airplanes, like navigating to waypoints and altitudes.

Current Asana Tasks:

• Add airplane controls
• Add airplane constraints

Weekly Update (2017-26-1): Benjamin

This week, I worked on improving the UI system and fixed minor problems and annoying bugs.

Status Line

One of the major systems completed this week is the status line. In the game, this line will display context information and respond to user commands. This line appears on the bottom of the screen, and adjusts height based on the screen resolution to match the font size. ("Status line")

A challenge encountered in implementing the status line was that there was no way to access the log method from everywhere in the application. This was solved using the singleton design pattern. (Further work done by liam: "Refactor with singleton")

Small Changes

• I added a small feature to disable the airplane tracking system when you attempt to pan. ("Stop following airplanes after panning")
• I decreased the size of airplanes so that they were less ridiculously large. ("Make airplanes smaller")
• I finished up the ui branch and merged it into master ("Merge ui with master")
• I made several text displays in the game scale size based on screen resolution ("Scale font size to resolution")

Next Week

I am planning on making another refactoring pass over all of the code. There is a lot of commented out code sitting around that can be removed, and a lot of things left over from before ProjectIcarus had singleton. We are aiming for full airplane control next week.

Guy 1/26

1/26/17

This Week

This week I worked on creating screens. I looked at several different examples, initially trying to implement this example, however, there were a number of documentation changes since this was posted, making my attempt at implementing challenging, and eventually I moved on from it. I then tried reading the documentation, however, my problem didn't seem to have a fix. I moved to this example, which proved more useful. I got to a point where I had only one error, and looking at the documentation again I believe that the problem has to do with setting the screen as a game and not a screen instead. This led to the end of the day on Friday.

Next Week

For next week I plan to finish implementing different screens to allow change on the press of a button or another action possibly. After that I may try and figure out pop-ups, however, we are not at that point yet.

Asana Tasks

• Menu(incomplete)