-
Notifications
You must be signed in to change notification settings - Fork 2
Future Features ideas
Selecting various entries is already possible in the flights dialog, however currently only batch deleting is supported.
It would be nice to batch-edit pilots or tails, for example:
- to group pilots together by adding company information that was previously omitted.
- to change an aircraft variant. When adding 1 by 1 over time, user has entered B 737 800, B 737 800 W, B 737 800 WSFP and wants to unify all entries to display the same
- Determine what fields are eligible to be batch-edited (e.g. names should not be)
- write the batch execution logic for Db
Most people already have an electronic logbook. In order for them to be able to continue without having to manually add all data, it would be nice to have the possibility to import data from other logbook formats.
- Determine the various formats other apps use
- Develop framework for parsing CSV, xls or JSON
- Develop DB functionality to mass-import entries
In some areas it is common to log time in decimal format, i.e. 1h45m would be 1.75
- No changes to database required, time is already logged as minutes and would only have to be parsed differently
- Adjustments to views
- NewFlightDialog needs support added for decimal time
At the moment we provide 2 default views of the logbook. It would be nice if the user could customize what layout and data he would like to see displayed in his logbook.
- Create a dialog(or wigdet) in which the user can create his own view of the database.
In the pilots and aircraft widget, the user can select to sort his display based on each of the shown columns by clicking on the table header and/or by saving the default sort column in the settingswidget. Unfortunately, QSqlTableModel only allows sorting by one column. It would be nice to sort by a second column as well, for example, sort pilots by company, and then by name, similar to how excel sorts multiple columns.
Either:
- Write logic that sorts by one column first, and then by the other, effectively calling the sort method twice. This would be quite clunky to implement
- Subclass QSqlTableModel to include this functionality. This would be the preferred solution.