A feature to download aircraft data again from the URL that was provided at install time. Maybe just ask for the password again (if it was previously provided or the server responds with 401).

Happening on Cupertino and probably on iOS only.

Using OCR: https://pub.dev/packages/google_ml_kit

Not much to say.

Only on week and day views.

• progress spinner should be really blocking (e.g. a semi-opaque overlay should be applied)
• initial loading and scrolling is really frustrating when there are few events
• use month name fancy backgrounds (see library examples)

The calendar widget has hard-coded use of the Material widget, so Cupertino theme never applies.

• read API for Google Spreadsheets + log book abstraction
• basic list UI
• aircraft data integration (google sheet ID and name, "no-name pilot", fuel types, ...)
• real event loading
• better handling of long pilot names in list view (especially the "no-name pilot")
• helper indicators and error handling (first time error, infinite loading error)
• be defensive when reading sheets data
• i18n

• Use a different color for each pilot (generated from name or photo or configured from aircraft data?) or maybe the avatar?
• Show event notes in schedule (and day view?)
• Show event times in week and day views

We'll need an appointmentBuilder. Be careful to overflows and text size and color.

Seriously, the scrolling pickers are awful from a UX standing IMHO. Find a better way or plugin.

Integrated into Fastlane.

Flutter: https://medium.com/@nocnoc/automated-screenshots-for-flutter-f78be70cd5fd (https://pub.dev/packages/screenshots)
iOS: https://docs.fastlane.tools/getting-started/ios/screenshots/
Android: https://docs.fastlane.tools/getting-started/android/screenshots/

Fix and improve metadata in the platform-specific projects (app title and description, versions, icons, etc.).

• Android
• iOS
• Linux
• Windows

MacOS is not available yet.

There are still some TODOs left about locale (e.g. dates, time, some numbers...).

Just use the iPad screenshots, but we need to find a way to automate it (device is not supported by screenshots utility).

Also, divide the screenshots.yaml file into two files (one per platform, the screenshots utility doesn't like it).

Currently using the Material ones since functionally they are way better than the Cupertino ones.

https://pub.dev/packages/modal_bottom_sheet

There are some issues when refreshing an aircraft. Look out for "/tmp/aircrafts/aircraft" directory being read over and over.

And the first time zone issues begin to appear :-)
Bookings made from the old app are not time zone compatible with the new app. Determine if it's our problem or a calendar's problem (or both).

A screen showing:

• aircraft picture
• aircraft picture takes some time loading: show something while loading
• aircraft callsign
• aircraft parking location with link for maps to the place
• pilot names and avatars
• logout/disconnect button (for returning to the install aircraft screen; it might require a full provider integration with AppConfig)
• version information and links
• Cupertino version
• i18n

Maybe register some URL handlers for automating the aircraft data download process. Or a QR code containing the URL to the file. Avoid a central registry at all costs.

https://github.com/juliuscanute/qr_code_scanner
https://github.com/AmolGangadhare/flutter_barcode_scanner
(+ something to generate QR for inviting others)

Split this issue into smaller ones after preliminary analysis and create a milestone.

A daily (as in timeline-like view) journal for maintenance notes, stuff to do, problems to solve (with a "solved" marker). Probably backed by a Google Sheet.

• #60
• Timeline view
• Card list view
• Backend storage
• Show entry details (popup or full screen dialog)
• Edit entry
• Create entry
• Mark entry as done
• Filter entries
• Due dates view (how? Maybe same as timeline view but sorted by due date?)
• Expiration indicator in items (use specific colors for expired/not expired)
• Server-side: automatic sort by date
• Server-side: automatic sort by priority desc, date asc

Unit:

• backend services
• models (mainly bean tests, e.g. equality)

Widget:

• hour meter widgets (mainly behavior)
• ...?

Integration:

• modal issue in book flight test (with conflict)
• book flight: form fields
• flight log: list view + create button appearance
• flight log modal

Consider using golden tests.

Use AIP notation (e.g. H24, HJ, HJ30, SR-SS ...) or some other notation in aircraft configuration to limit flight hours and warn the user when booking a flight. Beware events spanning multiple days (overnight hours should not be taken into consideration of course).
Calendar start and end times should be affected by this setting as well (approximately, e.g. before minimum sunrise and after maximum sunset).

• investigate on a way to do this in a more iOS way (e.g. spinner only, no text)
• there is a damn shadow below the dialog that I can't get rid of

This is a common feature so I'm not adding any feature label (but it is somewhat a bug).

https://api.flutter.dev/flutter/cupertino/CupertinoActivityIndicator-class.html
https://api.flutter.dev/flutter/cupertino/CupertinoPopupSurface/CupertinoPopupSurface.html
https://api.flutter.dev/flutter/cupertino/CupertinoAlertDialog-class.html
https://stackoverflow.com/a/59660740/1045199

An error dialog showing "Future not completed" is really misterious (it's the TimeoutException).

• loading events
• save/update event
• delete event
• aircraft data download

When editing or adding a flight, if hour meter values don't match with previous and next flights (if any), warn the user before saving.
Beware of paging issues (a previous flight might have not been fetched yet).

A small tool that takes some data in input (configuration? Questions?) and builds an aircraft data file.

Flutter won't use provided value by the operating system for setting time dilation (see flutter/flutter#10101). Although there is a way to get these values apparently, starting API level 17:

• Settings.Global.ANIMATOR_DURATION_SCALE
• Settings.Global.TRANSITION_ANIMATION_SCALE
• Settings.Global.WINDOW_ANIMATION_SCALE

I'm not sure which one to apply directly to timeDilation... and the transition scale should probably be applied only to transition animations (manually?)

Also open another bug to Flutter for this.

https://titanwolf.org/Network/Articles/Article?AID=304f1ee4-07a2-4138-85fb-a843c9ddb4bf

After booking a new flight, move the calendar to the day/week/month of the booking that was just created (highlighting the new item would be a plus), keeping the current view mode.

Showing "Day 1 / 1".

Actually there isn't any explicit scroll either for CupertinoScaffolds (Material works though). Does it mean we always need a (SingleChild)ScrollView? What about pages with an implicitly scrollable view (e.g. ListView)?

The new appointment builder doesn't handle events spanning multiple days.

• write API for Google Spreadsheets + log book abstraction
• basic modal with form
• fancy odometer fields
• odometer popup dialog (Material)
• Material form
• Cupertino form
• odometer popup dialog (Cupertino)
• validation and save logic (+ admin checks)
• delete logic
• i18n

A weird padding appears on top of the flight log list on iOS. It might be because of wrong use of RefreshIndicator (which is Material). Fix this with a proper cupertino widget.

stryder-dev/flutter_platform_widgets#194

A test doesn't exist because it requires mocking the HttpClient (which is specific to the platform in this case, it should be abstracted/mocked/whatever).

Mainly for desktop systems - but be sure to make it work on mobile too.

https://api.flutter.dev/flutter/dart-io/HttpClient/findProxyFromEnvironment.html

Probably because of the custom background we use in the dialogs.

After activating the booking modal directly from a time slot in the calendar, when selecting a partially occupied slot, be sure to set the start and end time to avoid any conflict (and notify the user of the change with a tooltip or something).

Maybe something that resembles the actual odometer.

https://github.com/martindobrev/animated_digit_display/tree/final_result_preview

Aircraft data can be used to determine which features of the app to show. Already partially implemented, it needs to be refined and tested with all features.

Even when idle. It might be a template bug, try creating a new project.

Soon to be developed into a nice tool 😎

Write down a checklist of stuff to do for creating the necessary account, API key, cloud objects and all for making the app work for a new aircraft. A preliminary checklist could be:

• create management Google account (will be used for all of the following actions)
• Google Cloud: API key for calendar and sheets
• Google Cloud: service account
• Google Calendar: new calendar owned by the management account or one the users (writable by service account)
• Google Sheets: new spreadsheet owned by the management account or one the users (writable by service account)
• Google Sheets: sheet automation (for now just #56)

These actions could probably be automated via some service account doing all the work... but one step at a time :-)

The Google Sheet has some stuff to be initialized... we could use a template or program it in the (future) tool:

• create flight log sheet
  • first row (in bold): A1 should contain count formula, other colums are simple title headers
  • hour meter continuity check
  • automation scripts (just #56 for now)

Use JSON Schema for the JSON parts and use stricter validation rules.

Also take the opportunity to refactor the download and parse code, especially the validation and open methods. There is also duplicate code between the about screen and the aircraft data screen.

Give the chance to pilots to be assigned a color from the aircraft data file and use it to paint the background of events and maybe flights in the log book one day.

IT'S TIME!

• use tags for triggering releases instead of pushes to the release branch
• README
• some sort of project changelog
• some sort of release tooling (version bump, what's new generation, tag creation)

https://github.com/conventional-changelog/standard-version

https://medium.com/@diegoveloper/flutter-collapsing-toolbar-sliver-app-bar-14b858e87abe

Somehow the format isn't right.

A filter view, opened from the right side, allowing filtering flights by:

• pilot
• start/end location
• duration
• date interval

Some stuff needs to be refactored for web.

• TZ data
• use of dart:io for files
• use of dart:io for HTTP
• ...