The past week we have been working hard on the following topics:
- Improved the album handling during adding operations. More smart logic has been applied to detect albums better as well as adding support for pictures. Pictures can be identified from tags (optional) or from folders involved in the add process. We have verified that the adding of files is fully compatible with Helium’s data model by running it on a new database from the new application and then by opening it in Helium 11. Many unit tests have been created to ensure that the album and picture handling will remain stable and easy to refact and improve.
- UI dialogs. We have created some specific controls to form Helium’s nice graphical look which can be seen in the most dialogs in Helium 11. The new look will support variable DPI font-sizes as well as vector graphics to be smoothly scalable.
- File properties. As a “test” for the new UI dialog components we have implemented a first look of the File Properties tool (far from complete though) to test off that the UI behaves well.
- Various async components so that several “heavy” operations can be used from background theads without locking the main UI. All async components should generally be cancellable.
- Basic crash reporting system. A first version of an automated crash reporting system has been implemented. This system is implemented in the main application as well as in the Tag test tool (read more below).
- Some preparations/proof-of-concept tests for the upcoming Music Explorer view.
Apart from the main changes above, we have also released a first version of our tag tester tool to a couple of selected testers.
This tool will scan a selected folder recursively and identify all audio files with the folder and it’s subfolders. After that each file found will be loaded with our new tag engine (running in the background with a cancellable progress dialog of course). After the scanning is completed, a selection of the tag and file properties will be show for the end-user in a list and a list of “problematic” files is also show (if any).
The intial tests has been very successful, the most seems to run very stable and quick and problems identified as been able to be fixed quickly thanks to the crash reporting service.
If you are interesting in testing our tag test tool, please contact us at firstname.lastname@example.org.