CAP FlightLog

Adding Features

I have begun adding features and putting data where it needs to go. I added a settings tab which includes Cadet Information such as Name, Grade/Rank, and unit. It also has the import and export features, and includes the ability to erase all data from the site. I added the print button here as well, but there are some minor issues with that button in particular, it prints the wrong page. I plan to address this with my next edit.

Next, there is now separation between the logbook and dashboard tabs, the dashboard tab greets the cadet by name and grade as well as has their unit listed. It shows some brief information at a glance: Hours, a less-detailed breakdown of hours, average flight length, and the most recent logs. I have also added the acronym (CAP) into the app. This shows in the corner where the app says CAP with a little plane, and the title says “CAP Flight Logbook” now instead of just, “Flight Logbook.”

What’s next?

My next goal is to add in a requirements page that displays everything from practical exam (the one where you fly the plane) to whether or not your medical grade is registered. I want to fix the printer button, and have a breakdown of hours left vs what they have and the percentage of the way the cadet has on his license. The final two goals for this next edit are: Making things look better, and adding in the API key function to fetch all airports in the U.S.

What’s after that?

After those next few edits, I want to build a decent looking webpage to provide basic information on the project, how to implement it properly into the unit, and some documentation. I would also like to try and add google drive integration because CAP cadets have google accounts provided by the government, this would allow to sync the backups to google drive instead of doing manual backups and would negate the need for a vps to host this app’s database and authentication system.

This includes two iterations because I originally started it and before making my devlog, I started the second piece. The first iteration was just to test browser storage and missed 99% of features, it only included the date, aircraft tag, and hours, it was as boring as the website could look. The second version is that same idea but with an actual UI, color and design, it also featured the hour breakdown tool and allowed more input options on the log. It featured a json export and import with a simple format shown below in a photo, and finally included the print button also shown below in the photo. At this point, I was just focused on the logbook and haven’t added any of the fancy features or the designs that make it look like it was built for CAP. All of that will hopefully be in the next edit.