PSA about Simple Classic Theme Jun 23, 2022 12:41:05 GMT -8
Post by leet on Jun 23, 2022 12:41:05 GMT -8
A PSA regarding the future of Simple Classic Theme and upcoming subcomponents (if any):
I recently have been thinking a lot about the current state of SCT. People are frequently experiencing issues with getting it set up because of clarity issues and the lack of proper guides. SCT is currently in a midway state between being a full theme suite, and a tool to quickly enable Classic theme.
There will be three main changes with SCT, in the hopes of making support better, making SCT easier to use, and making it easier for me to maintain code.
First and foremost: SCT will be a full Classic Theme suite. This means I will drop support with getting SCT to work with ANY other Classic Theme tool/method. This is a big change, and to combat the drawbacks of this, I am going to implement custom hooking and scripts that will replace functionality in current setup with SCT and existing explorer hooks. My hooks will be mainly focusing on getting Classic Theme working within Explorer and restoring popular features like clientedge and the old address bar. The Multi-user Classic Theme (MCT) component is the first step towards this and it will be an important step for making the user experience of SCT more secure, easier and extensive.
I have already mentioned the second change on ClassicServ, but I am in the process of making a separate website for SCT. WinClassic has allowed the program to become what it has become today, but I think it is time for SCT to separate from it. I will still visit WinClassic from time to time, but all SCT related development updates, releases, discussion and support will be moved to SCT's website once it is done.
Before I mention the last change, I will say this: I know this is a controversial change and against things I have said in the past, but I think it will be for the better for SCT and its development. I am not going to discuss or argue about why or why not, so do not ask me, but from this point forward SCT, and any tool I make regarding it, will become closed-source, proprietary software. The only exception will be MCT, I will soon create a separate GitHub page for it, and it will remain open-source for the foreseeable future.