|
|
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.
|
|
|
|
Post by OrthodoxWin32 on Jun 23, 2022 13:33:59 GMT -8
Good luck for the rest of your project, I fully understand your desire to create your own website for SCT. On the other hand, even when thinking about it, I do not understand what would benefit SCT from transforming it into an proprietary software. But I suppose that reasons escape me.
Please keep open-source the color/metric configuration page. This is the only correct tools it exists to configure Windows colors.
|
|
evnl
New Member
Posts: 18
|
Post by evnl on Jul 2, 2022 8:48:48 GMT -8
I always feel is SCT is giving many people problems because you're trying to obscure what you're actually doing. If you would just offer separate executables/batchfiles with clear explanations what they do then it would be much easier to troubleshoot. Another thing I ran into often is that auto update is on by default. Several times I had a working setup but once there was an internet connection SCT update and everything broke again. Going closed source will obscure things more but if it works it works.
|
|
|
|
Post by OrthodoxWin32 on Jul 2, 2022 9:27:51 GMT -8
I always feel is SCT is giving many people problems because you're trying to obscure what you're actually doing. If you would just offer separate executables/batchfiles with clear explanations what they do then it would be much easier to troubleshoot. Another thing I ran into often is that auto update is on by default. Several times I had a working setup but once there was an internet connection SCT update and everything broke again. Going closed source will obscure things more but if it works it works. I agree ; None of the recurring problems of SCT seems to be linked to the open-source nature of the program, but rather a general lack of clarity, as leet himself says. This took me a long time to understand the desired goal of certain features, it must be even worse for a non-experienced user. |
|
|
|
Post by leet on Jul 2, 2022 13:37:11 GMT -8
This is not what SCT is intended to be. If you just want some batch scripts that install Classic Theme, you can use 6sicsix's or anixx's Classic Theme methods. SCT is intended to be more than just a scripted Classic Theme installer: The goal is to abstract Classic Theme into something that any user understands and can use. I admit that a lot of work is needed to get there. The main reason why an update of SCT takes months to complete is that I don't have the time to write extensively write full code. I keep adding little bits to the code, and every time I come back to it, I need to look at what I was doing for 15 minutes again. I hope to release SCT 1.7 as a project that achieves this goal, so it will probably still take months for that to come out. A lot of work is needed, and I want to be sure it's a smooth and easy-to-use experience.
I never said anything about closed-source making SCT better. In fact: I specifically stated that I will not discuss why I made that choice. I intend to keep it that way.
|
|
|
|
Post by OrthodoxWin32 on Jul 3, 2022 3:09:25 GMT -8
leet Thank you for archiving the original sources.
|
|
|
|
Post by daemonspudguy on Jul 21, 2022 19:41:59 GMT -8
I don't understand why you're closing the source of SCT, but I respect your decision and appreciate that you posted this ahead of time.
|
|
|
|
Post by bunnyboy29 on Aug 13, 2022 20:19:22 GMT -8
I can't wait for the next release because I cannot get this working at all on Windows 11 21H2. I get that context menu bug and I cannot even get the borders and stuff to apply at all. Like when I hit Configure Colors and apply Windows Classic or anything really SCT freezes and I have to force end it. Also the Ribbon turns white and the forward back buttons disappear.
I literally do not know what I am doing wrong. I followed your guide step by step like 4 times and it doesn't work for me and idk why. I want this to work so bad, I am not mad at you I just wish I knew why it wouldn't work for me.
|
|
