Feeling better about the codebase

I am seriously debating making a dedicated blog so I can write about my thoughts and ramblings instead of this page in the documentation, but that’s a future-me issue. This ended up happening so, here it is.

After changing the way I work with Codex, it’s been a lot more enjoyable to work with the codebase. I started taking a more hands-on approach to modifying the codebase, which has helped me gain a better understanding of exactly what is going on. After some work, and using Codex as a learning guide, I’ve managed to rectify the majority of the key issues I was having with the codebase before.

The state system I had before was terrible. While the tool window has been almost completely refactored with a cleaner structure and has become more editable, the next snapshot will focus almost solely on the application-level settings pane and the settings featured there. It may also include some extra work toward improving the Blender API stub implementation so that the stubs are set up properly.

After that, the last thing I want to reimplement from the earliest stage is proper Blender configuration sandboxing. This is a feature I feel is extremely useful to ensure that developers are working in a clean environment, free of any modifications they may have made or any extensions interfering with their work.

Overall, I am feeling much better about the future of this codebase. I will probably start finalizing some graphics this weekend for the project and maybe—just maybe—set up that blog so I stop rambling here.

One more thing I really should implement is adding SHA-256 checksums to the main website where users download the file, so they are more readily accessible instead of requiring a visit to the Codeberg repository.