Far as I can tell, the 4.4.123 is only for updates to the Classic Shell IE portions, not the main shell. I left it alone and told Sumo to shut up about it for a while!4.4.118 is current, like in Josey's link to Github. I think MG is still showing 4.4.109. So... it's all up to date in various stages everywhere. The band is still tuning it's instruments, but it plays well.
Thanks for replies - just checking to make sure I haven't screwed it up somewhere. Will just be patient - at least it's being worked on.
I have actually been trying to follow the project on GitHub, but it's mostly over my head but I figure when they do come out with a new version we'll see it there first since the updater in 109 is nonfunctional
Anyone need help with Classic Start ?
Please note: Expect new artwork shortly :)
Tim
ARS N9NU
Neo Classic Team
@N9NU
Hi, Tim! i Think what we were wondering is what/where/etc. is .118? I pulled it off Github on 7/08, and it appears to be nowhere now. I have it running fine on all Insider builds. Ref my post here: Classic Shell no longer in development, and now open source - Page 42 - Windows 10 Forums
NeoClassic-UI/Menu
NOTE: For some of those following this project on GitHub I know it may be a bit confusing on the way things are shown on the various pages there and I just wanted to briefly describe how this type of developmental & file repository environment works. For the end user, it's just click on a new release and install. The entire project can be 'used/viewed' in two different ways:
1. (For most users)- Downloading and installing the pre-compiled .exe/.msi versions (located on the 'Releases' page or tab). As of this date there is no 'stable' or 'RTM' release, however, you can consider the versions shown stable for just about all at this time.
AND/OR
2. (For the impatient..heheh...and die hard geeks like myself) - This involves building and compiling the source code shown in the 'Master' branch under comments). This is what's called a 'rolling release' type of development environment where files are updated individually or versus the whole package being re-released as a new update...so to speak.
You will notice the dates of certain files are older and some that are very new. This is the way it works here. Work is always being done and files will be updated as needed on a continuous basis...all of which are available to you as soon as they are uploaded. When 'x' amount of changes have been made and reflect most of the bugs addressed or new features added, etc., a new 'version' or release will be posted (i.e. 1.0.0.9, 1.1.0.0, etc) on the 'files' page. These will be pre-compiled .exe/.msi/.zip files.
The absolute latest files will be located in the 'Master' branch: GitHub - NeoClassic-UI/Menu: Reborn of Classic Shell (Ivo Beltchev) - Classic Start (passionate-coder) - Remember that these files are the source code and need to be 'built' and compiled by executing certain files within the 'ClassicStartSrc' folder. There are MS dev (developmental) files that are needed to do this. These can be obtained by referring to the 'readme' and other help files within that folder.
This process is not difficult and just requires a bit more work to get them compiled and installed. This IS, however, the only way to get the absolute latest files. For those having issues these updated files may or may not help with your specific problem. It may require additional updates. To download the source code from the master branch, please click on the GREEN button on the right hand side and from there choose the .zip file option.
PLEASE feel free to post on the 'issues' page/tab if you have any problems. I have been trying to relay certain issues as fast as I can so they can be addressed in a timely manner.
Direct link to Issues (bugs/requests, etc): Issues · NeoClassic-UI/Menu · GitHub
Direct link to the pre-compiled .exe/.msi binary files (versions/releases): Releases · NeoClassic-UI/Menu · GitHub
Direct link to the source code (latest files available & must be compiled and installed): GitHub - NeoClassic-UI/Menu: Reborn of Classic Shell (Ivo Beltchev) - Classic Start (passionate-coder)
There will be a new 'release' or 'version' for the complete package shortly. I know a lot are seeing individual files with new dates and possibly new comments/versions being shown. These reflect files that will be included in the forthcoming release.
Tim
ARS N9NU
Neo Classic Team
@f14tomcat
Yo....yeah I was out of town so I missed some of what went on. I will check to see exactly why it was pulled.
NOTE: Anyone can request a file or release to be 'pulled' by going into the page/tab called 'pull requests'. It is either one of three reasons:
1. There was something significant enough to impact the installation or operation of the program (a severe bug or other)
OR
2. A pending release of a 'stable' version based on a temporary pre-release or hot-fix version posted for testers to...well...lol...test - I know.....huh? LOL
OR
3. ???
I will check in
Tnx
Tim
Thank you, Sir! And thank you for the in-depth how/what/why/where post Classic Shell no longer in development, and now open source - Page 42 - Windows 10 Forums
Quote
