Split original "Classic Shell" bundle into separate development teams

[coddec]

@jdunn0
@ibuprophen1

coddec#19

Classic Shell currently consists of a few separate components that are developed and released with one installer that can install one or all of them.

The different components however do different things and I think it would be better for development to make each component, a new software project with it's own name, installer, GitHub issues section and separate releases.

I don't really see any reason to keep all the components under one GitHub repository when they do different things.
One component is a Start Menu, one adds a toolbar to File Explorer (The Windows 8+ name for the Windows Explorer File Browser) and one restores the IE6 look to IE7+,

Each component having their own name would also help with the things talked about in issue #13 as each component could have their own, more accurate name instead of just being a component of Classic Shell.

It also benefit the users that only use one component of Classic Shell as it could be installed on it's own.

The "Classic Shell Update" tool wouldn't really work anymore but it could be replaced by a new software project that handles automatic installation of new versions of each the different programs.
The replacement software could be a build of Google's Omaha project which can handle the automatic checking for updates and update installation for multiple software projects.

Omaha is the project behind Google Updater that handles automatic update checks and automatic update installation of all Google software.

Omaha is a little bit complex but when setup, it can work quite well.
Here is how Omaha works:

1. Each program has their individual installers that automatically install Omaha when they are installed if it isn't already installed by another program.
2. The installer registers the program with Omaha via registry entry.
3. Omaha runs in the background at various times via the Task Scheduler function of Windows to check for new updates.
4. If an update is available then the programs new version installer is downloaded and installed slightly in the background when the program is not running.
5. Omaha will be uninstalled when the last program to register with it is uninstalled.

The fork could be called "[New Organization] Updater" where "[New Organization]" is the name of the new organization in GitHub as discussed in issue #13.

All the newly split out components could be repositories under this GitHub Organization too.

[XenHat]

I renamed the title to better fit the idea your comment tried to carry. I agree. Far from promoting abandon, we could attribute people who are interested in contributing to Explorer and IE components to the respective projects, without requiring full access to Classic Start.

I don't particularly want to maintain Classic Explorer, nor IE components as I do not use them myself, and was actually planning to disable them by default in the installer.

I will have a lot more free time in the following month(s). I will clone the repository a few times, and clean up the "extra" components per-repo to preserve the code, but only build one component.

EDIT: As a start, I will look into changing build system to build components separately without including each other into a single installer. (3 installers, 1 per component)

[coddec]

@XenHat
Yea, as discussed before, I'm only interested in Start menu part too.

[Ibuprophen]

I agree with you @XenHat!

I've never really found the want/need for those specific features because I use the software for what, I believe, is the true purpose for what the software was meant for "A Classic Style Start Menu".

~Ibuprophen

[DavidXanatos]

Dont get ridd of classic explorer, i use it all the time.

[Ibuprophen]

@XenHat and @coddec...

Instead of abolishing the additional software in question, can't they be separated as a whole in an addon/enhancement software way?

Either 2 Classic Start Menu downloads with one of them only with the Classic Start software and another that includes the additional software?

Or just one with the Classic Start Software only and a separate installer addon software with the other features in a form of a complement to the Classic Start software (for those who already have the Classic Start installed).

I hope that I had explained this okay via text... :-)

~Ibuprophen

[XenHat]

Oh no, we don't want to abolish the other two components of the original "Classic Shell" software and I'm not against doing some critical maintenance on it, but I do not use it, nor do I really feel comfortable touching Explorer right now (waste of efforts, MS is bulldozering it every week lately) and IE is dead. Sorry.

I do not want to package it by default, but a separate installer for Classic IE and Classic Explorer (either combined or separate) will do.

[DAOWAce]

Classic Explorer is essential for me in Windows 10 because of how they're forcing you to use the details pane and all the other terrible changes. (no sorting headers unless in details view)

All I want is the Windows XP/Vista explorer, and Classic Explorer is the only thing keeping it alive.. albeit with problems in Windows 10. (no copy menu replacement, and 10's comparison is GARBAGE)

To me, both the Start and Explorer pieces are essential. As for the Internet Explorer thing.. that's so long out of date nobody has a use for it anymore, right? Microsoft works on "Edge" now, which is arguably a lot better, but I still use a fork of Chrome (Cent) instead. Doubtful anyone uses IE.

[Ibuprophen]

My last suggestion here was only intended as a suggestion to Separate them but, I don't have any problems with the way it is now since the software already provides those options within the installation process already.

The only thing that I would recommend/suggest is better/clearer "Noob Friendly" verbiage when the installation process reaches that point of the installation options.

Thanks a bunch! :-)

~Ibuprophen

[pkar70]

I'm using IE :)
Both IE and Edge - Edge for web apps, and IE for web sites. Why? Because I can disable scripts, ActiveX, and all of this stuff, and make IE impenetrable by threats. Only my bank web page has permission to use scripts. And IE is much faster and have much smaller memory footprint.
This post I'm writing in IE...
From Classic IE, I'm using some options, but only one is essential: 'show zone'.