Inspired by the Tiny Pomodoro project, use the same AppComponent trait to split the view components into separate modules. This helps separate the main egui App, individual data structures, and how the view is displayed based on App state.

I also discovered why my main library causes the app to run slower. Every frame is sorting/grouping the library items. All library views should be stored in the app state or separately in some sort of library database.

Use Confy so reasonable paths are used. The toml feature didn't work, so I'm using the Yaml feature. Confy looks like it isn't being actively developed, so this may be worth refactoring into a sub-crate.

When loading large music libraries the main ui thread becomes blocked and the app is unresponsive. For now, offload the work to a background thread. The threads communicate with a mpsc channel.

This PR add functionality of saving the app state in a json file. I opted to go without the persistence feature from egui because there were issues with rodio not finding an audio device as well as not playing any audio at all. It seems as if it only works when the audio device is created outside of the egui app, which is what I'm doing here.

Temporary error handling was added just to get the app to work without an existing saved state. Some things to fix next:

• Figure out error handling
• Use confy or something to handle storing the data in reasonable places.

Additionally a large amount of refactoring was done to start making the app easier to manage. The next refactoring should start extracting components for each feature.

Add support for track number from the id3 tag. Implement the player functionality in the Player menu bar item. Change the track state footer to show only the filename that is currently playing instead of the full path.

Start work on the menu bar with features that will be included.

• Moved create playlist button into "New Playlist" option from the File menu.
• Move track state information to the footer.
• Add an exit feature.

Utilize the new Grid widget. I still need to figure out how to select a full row and extend the grid to the full width of the parent widget. Additionally supported a currently playing indicator in the row of the currently playing track.

The app should no longer be creating LibraryItems after the library is loaded. This lead to a bug where items in the playlist were missing the data from the library. Additionally they are all cloned, which means they can have separate state. That is one aspect of a refactoring I would like to look into.

The app now changes the window title when a track is selected to play.

Instead of keeping two separate structs, use the LibraryItem. It not only holds the path, but it also holds the id3 tag data, which can be used by several views.

Itertools group_by indicates items must be consecutive. The list given to the group_by needed to be sorted. In addition, LibraryItems missing id3 fields will result in a None so the frontend can unify the "?" being displayed.

Add the most basic support for a music library.

• Can select a folder/directory
• Parses ID3 tags only
• Displays via album titles
• Double click to add to a playlist. This is awkward. Figure out key events.
• Double click tracks in library to add to the playlist.
• Synchronous library building, which can block the UI thread :(