@Steve

Conventional commits are sooo nice. I’ve started using them after just dumping everything I was working on into one big commit and it’s so worth it.

I’ve also been working on shoring up my current structure, dependencies, and all that good stuff to make it more maintainable. That’s what this project is supposed to teach me after all and I think I’m getting the hang of it. Also tidied up the ui a bit and am working on making the plugins page with settings. That will be interesting compnent-wise because each setting for a plugin has several different types and has to update based on that. We’ll see how that goes.

I’ve been working on the ui, made with typescript and scss. This is what I have so far. I’m making it super nice and maintainable with typescript features. I also made a whole component system that automatically handles get/set functionality for the properties. I used that for each sidebar item and each notification.

I also made a sorting system that has yet to be functional at all.

I’ve been having a lot of fun with abstraction/object oriented stuff. With it I set up a whole system that loads plugins and gives them methods to call like a logger, setNotification(), etc. Also the system calls it’s getNotifications() function every 5 minutes (will be configurable).

I’ve also moved the implementations of my school’s grade/homework system and email imap to the new schema, along with implementing slack. The big thing right now is to design/create the web ui. It will be able to handle everything eventually.

I designed the UI for the app, and am currently working on setting up the main structure for the backend. I’m setting up the plugin system and in the process learning object oriented concepts in ts. Instead of having all the db calls inline where I serve the routes like I did before now I have an interface for my database! It’s a lot of fun

I’m currently getting used to the MVVM structure of avalonia and learning how that works. It’s not too terribly different from HTML since it’s xaml but it does take quite a bit of getting used to.

I’m currently working on the import page. Right now you can select a drive or folder on disk, and it will pull all the RAW photos out of that folder, quickly grab each of their date taken attributes, sort them into “shoots”, grab and scale the embedded jpeg to 300x300, and display all the photos to the user in a grid.

I think I won in UX over lightroom with my shoots because what I do is look at the time a photo was taken and if it was taken 6 hours after another, I put it in a new shoot. You can put those shoots into a hierarchical category tree as well. I’ve created classes for Shoots, Categories, and Photos.

I also hooked everything up to a SQLite3 database that will hold all those shoots, categories, and photo metadata, along with file location, in reference. I’ll store the files on disk in a folder structure by year, month, and day and then have the catalog hold where eveything is. You’ll be able to move things between drives from within the app.