Skin Editing can sometimes be a thing of mess, especially for those who aren't quite good at editing files and pictures. So here's a idea/project aiming to make everything easier.
So the basic idea is using an "Asset Library". In a sentence, elements from skins can be imported, then sorted and stored in a "Asset Library". Without needing to hurt your eyes finding the approachcircle.png in your folder, we can have a dialog pop up, showing you all the different approachcircle.pngs in the library for you to select. This idea also works in audio replacing.
Another feature(maybe?) is a editor for skin.ini. As you might guess, no more notepad.exe for editing skin.ini.
Status: Very Early Stage
I am using WPF and C# for this project at the moment. Material Design In XAML Toolkit [Link: https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit] is used for better appearance. No plan for UWP or Win32. No plan for linux and Mac. I will stop developing when osu!lazer is *ranked* and the built-in skin editor works better than this project (current one isn't fully developed).
Currently working on the first, usable alpha version. Will post it on Github when finished the first version.
Idea
When the player wants to change an element, let's say approachcircle.png, people usually open the file explorer, and start replacing the elements manually. I want everything done just in a *click* ---- find the element and select.So the basic idea is using an "Asset Library". In a sentence, elements from skins can be imported, then sorted and stored in a "Asset Library". Without needing to hurt your eyes finding the approachcircle.png in your folder, we can have a dialog pop up, showing you all the different approachcircle.pngs in the library for you to select. This idea also works in audio replacing.
Another feature(maybe?) is a editor for skin.ini. As you might guess, no more notepad.exe for editing skin.ini.
Dev Blog
* 2022-1-15Status: Very Early Stage
I am using WPF and C# for this project at the moment. Material Design In XAML Toolkit [Link: https://github.com/MaterialDesignInXAML/MaterialDesignInXamlToolkit] is used for better appearance. No plan for UWP or Win32. No plan for linux and Mac. I will stop developing when osu!lazer is *ranked* and the built-in skin editor works better than this project (current one isn't fully developed).
Currently working on the first, usable alpha version. Will post it on Github when finished the first version.
Current Issues
- Copyrights & Rules: Is it legal to use elements created by others? If skins created using others' elements can be released in public or not? Should I, as developer, take active actions to avoid users from infringing copyrights or just put a disclaimer and do nothing? What license should I use? Is there any risk that I may violate the rule?
- Slow Development: As a senior high school student, I don't have that much time on this project (only weekends usually). Should I keep developing on my own or seek help in the community?
