Classic Shell
http://www.classicshell.net/forum/

Classic Shell no longer in development. Source code released
http://www.classicshell.net/forum/viewtopic.php?f=17&t=8147
Page 3 of 3

Author:  f23948 [ Mon Feb 12, 2018 7:06 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Ivo, can you upload all start buttons, start menu skins and taskbar skins to GitHub please?

Author:  Ivo [ Mon Feb 12, 2018 9:50 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

I did not create the GitHub repository, but I believe the skins are there: https://github.com/coddec/Classic-Shell ... lSrc/Skins
And the images for the start buttons can be found here: https://github.com/coddec/Classic-Shell ... artMenuDLL

Author:  f23948 [ Mon Feb 12, 2018 10:03 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

oh ok thank you

Author:  f23948 [ Mon Feb 12, 2018 10:10 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

it seems it didn't upload all start buttons, start menu skins and taskbar skins, any suggestions?

Author:  Ivo [ Mon Feb 12, 2018 10:28 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

It has the ones that are part of the Classic Shell software. Any additional skins that you see on this forum are created by other people. You need to contact them for the actual source files and usage terms.

Author:  f23948 [ Mon Feb 12, 2018 10:40 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

ok thank you for reply. i will contact them

Author:  Classicmag [ Wed Feb 14, 2018 3:09 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

What about just sticking to developing it for LTSB or just updating when there's a new build instead of racing to keep up with the latest Windows updates?

Author:  Jcee [ Sun Feb 18, 2018 5:45 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

>actively maintaining compatibility for an obscure windows 10 release that less than 5% of Windows 10 users likely use
I mean if it currently runs on LTSB then it should continue to run on LTSB for 10~ years if you dont install anything beyond the security updates

Author:  Kguhino [ Thu Feb 22, 2018 3:11 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Ivo ... what about a lo-fi read-only version for another year after that, maybe things turn around. That shouldn't be that costly to host. Feels sad to see history being erased like this, in this time and age a powerful group which has their grip around the technology sector is only interested in pushing their things and overriding all other cultures, something like this could stand as a protest against that.

Especially if some of the programmer/hacker gurus get their head out of their butts, so many haxors around the globe and so little hardcore mods for windows, for example the termsrv.dll mod which allowed multiple simultaneous users through RDP on one PC plus a real physical user.

Maybe something would happen if someone who has a good amount of bitcoins would start posting "win project jobs" about "find a way to bring back this windows feature on this windows version and build" on TOR sites, there's absolutely going to be someone out there who would be willing to do it and do it really good for a price.

On this Win10 build I have right now, unfortunately, the UseWin32TrayClockExperience does not work, but I knew it worked on one of the version I had tested half a year ago, and I looked in detail, it was actually one tiny build number higher, so somehow now I have a little bit older version (probably because of the lack of that unnecessary update which was a tack-on) but it looks like that thing made this work. Because everything else works except this, so it's a pity.

Unfortunately no bitcoins, yet (oh well), but I'll say it anyway with a General Carville (RA2) voice: Commander, get me my Win32TrayClock Experience back!

https://i.imgur.com/LuUFTxE.jpg


Jcee wrote:
>actively maintaining compatibility for an obscure windows 10 release that less than 5% of Windows 10 users likely use
I mean if it currently runs on LTSB then it should continue to run on LTSB for 10~ years if you dont install anything beyond the security updates


Exactly, I have no idea what are most of these "windows gurus" thinking. You're not suppose to run Windows Update, you're not suppose to "move" to any OS, jeez!

Get another disk and put Win10 on, don't bother with dual boot, then alternate the disks, it's not a good idea if newer windows versions detect another windows installation, they'll try to mess with it or even push updates and promos.
Then install all the drivers and anti-spying and disable updates without connecting to the net, takes prep time to DL, after connecting then do the rest of the tweaks, and there you go, tweaks will keep working forever, no need to switch any OSes.

There's very little useful in updates, and if you do it, you do it with WSUSOffline and that's how I updated my Win7 twice in over a 5 year period, by manually using DISM tools to update over 80 updates at once.

However it took me like 2 days to manually scour thoguht the updates which are going to beneift and which ones were part of the Win10 promo crap as well as the ones which are high-risk for messing things up, but this is also a lot of experience on my part which plays in, an average person won't have the patience for any of this, but this is what is the difference from sheeple vs guru.

I've tested Win10 3 times through the years, but only for a few hours each time, didn't like a lot of it, but I wasn't even planning testing for much, from the get go it was clear it's going to be a crappy OS for the old cats, that's why I did not bother with any of it until 2 years later, this year.
Why? Because if you're a windows guru, you're suppose to know that everything and anything new from MS will have at least a year of the beta-test period, you're not suppose to take a new OS seriously in that timeframe, everyone that does is a trapped lab rat.

So this month I took the time to nail it, tweaked the crap out of it, took me a week of hard work full hour days, long long story, it's going to look like Win7 soon enough when I finish all my tweaks, including the full GUI and the boot logo.

I will also take it a step further in the following year (hopefully) and do something what does probably not exist yet, a full blown system icons change so almost every icon possible will have a Win7 version, including the mouse cursor.

That's what a windows guru is, you people are doing it wrong, time to stop being sheeple.

After all this, you would think, "OMG WHAT ABOUT SECURITY" ... if you're a PC guru, you're not suppose to keep anything highly private on such a computer you use daily and online anyway, so who cares if they hack or do a few viruses, they wouldn't find anything important.

But then, you would ask, "OMG WHAT IF THEY ENCRYPT EVERYTHING" ... if you're a PC guru, you have regular clonezilla full disk image backups, you're not suppose to deal with any OEM or Windows gimmick backup tools.

I'm just getting started!

Author:  conan.conan [ Thu Mar 01, 2018 2:07 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Sad to see this new..hix..

Author:  ZoNi [ Mon Mar 05, 2018 2:40 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

I just hope you can add "Apply" button to the Settings window (I hate to click OK, than reopen Settings, than again OK etc).

Author:  plaws [ Thu Mar 08, 2018 12:01 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Ivo wrote:
Sad news, everyone.

After months of deliberation, I have decided to stop the development of Classic Shell.



1) Thank you for Classic Shell - it's the only thing that got me to try Windows 10 (I'm not a fan of any Windows).

2) I'm sad to see that you are moving on, but I completely understand!

3) Thank you for licensing the source code so that others may continue the project (hopefully!). I wish more authors would do this when they inevitably move on from their "baby". :-)

Peter

Author:  waltz [ Wed Mar 14, 2018 7:46 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Ivo, thanks for Classic Shell!

Author:  Rskeats [ Sat Mar 17, 2018 5:41 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Well that is sad.

I thought Vista was enough to make someone loose their temper that they have to switch to something else. Like I am stupid and the automations and scripts can predict and think better for me like thumb view being set and filenames being hidden because it had one picture in a folder and have to do a lot to get it back at the time. One thing I absolutely hate is that BREADCRUMB they decorate over the address bar as it bloats the view and makes it unclear. As a lone technician it is unclear and confusing to look at. I don't always want to click it to find the rest of the details. Unnecessary or not it is stupid as limits the view. They could have given the user a choice as it might work for a particular situation but no. I know there are a few breadcrumb killers out there but this made it easy. There are a bunch of other things but I don't always care how it looks as long as it doesn't interfere with what I am doing.

I spend hours on customising customers things just to make it easy to use and thanks to this tool they eventually become literate as they can see what they're doing.

They say "People don't like changes and they have learn how to accept changes and so on". It is whether it benefits us or not but when it interferes and hinders our activities and where the users have no sense of where they stand and unable to learn and that is where there will be tools such as Classic shell.

After so many years of use it looks like everyone will have to start donating.

Over the years I have been annoyed with unclosable fixed headers/persistent bars that also cause the same annoyance and I found a Chrome plugin Header hider fixer for that by Emojistuff but then I see this project is closing down.

Author:  sirapacz [ Sat Mar 17, 2018 6:22 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

I have installed Classic Shell on >300 PCs since Win8 with it's tragic metro menu.
I can't imagine, how i will be able to help users with shitty Win8/Win10 interface. Seriously.

I can only have hope, that someone talented will move project forward.

Thank You for creating and maintaining this essential project for Windows users.
Michal Gut

Author:  jelabarre59 [ Mon Mar 19, 2018 8:59 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

I am concerned about at which point Classic Shell is going to *stop* working due to API changes in future MSWin10 releases. Would want to know so I can be sure to lock-down systems for family members at the last compatible MSWin version.

Yes, I know it's been open-sourced, but it will take time for other developers to become interested in the project, and more time for them to come up to speed on the code. Personally, I'd just as readily prefer to get my brother to move *his* machines to Linux, and at worst case the in-laws would have to buy some "commercial" replacement shell (presuming MS doesn't manage to break them as well). And my wife will either need to deal with degraded functionality in later MSWin versions or just run WoW under Wine/Crossover.

Author:  Jcee [ Mon Mar 19, 2018 3:53 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Nobody knows... but its likely microsoft will continue allowing users to opt in for beta updates... run one of these as a VM, and when the start menu breaks.. thats the time to lock your other computers ;P

Author:  smokeycockatiel [ Thu Mar 22, 2018 4:05 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

PLEASE PLEASE PLEASE Reconsider.

What will we do on windows 10 without classic shell

Back to the beginning.

No proper start menu (without classic shell)

Please sir :-(

Why not charge .50C or 50 Pence to download classic shell, or to help fund production

James

Author:  Chrysalis [ Mon Apr 02, 2018 2:44 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Registered solely to say thanks, and you have been valuable to the windows community.

Personally I run windows 8.1, I disagree with the principle of treating home users like beta testers on the twice yearly feature updates, one of the reasons been it breaks software such as classic shell. I believe in been control of my own system, even if it means I am less secure, so be it.

I use startisback for my menu but only because I already had a license when I realised classicshell does the same thing, on my family pc's they have classic shell for the menu, I use classic shell to enhance my explorer and IE tho.

I perfectly understand why you quit, I imagine for something you do as a hobby, having to fix it every 6 months made it seem more like a job, which is what I feared would be the result after microsoft released windows 10. The author of another bit of software I use also recently quit as well, I expect for similar reasons. I also wouldnt rule out microsoft deliberately breaking your program as well, I cannot remember the windows 10 start menu really changing on every update yet they seem to change code that forces you to have to fix it.

I also commend you releasing the source code, been open to the community to carrying on your work, I like that integrity whilst other developers can react differently, pulling download links etc.

Author:  Clemens [ Tue Apr 10, 2018 1:11 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Installed the insider preview of the spring creators update today...everything seems fine regarding classic shell on first sight...
https://puu.sh/A0pfx/1f9129d833.png

Author:  Snappy Phoenix [ Wed Apr 11, 2018 10:10 am ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

same here, installed the Windows 10 Redstone 4 RTM (not preview) and everything is working perfectly

Author:  JohnBurns [ Thu Apr 12, 2018 6:35 pm ]
Post subject:  Re: Classic Shell no longer in development. Source code rele

Thanks Clemens and Snappy Phoenix for posting. I was concerned about updating to the "Spring Update" 1803. This relieves my mind and I can sleep another week. lol. Thanks

Page 3 of 3 All times are UTC - 8 hours [ DST ]
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/