OK, it's been 3 days since I announced that the tests for UCC v4.1.4 have been put on HOLD. I promised more information, after 3 days of working on it I feel more comfortable to share so here goes.
Some Background:
As you are well aware, There was a problem found lately with UCC V4.1.3.2 Updated 3.0 and an Hotfix was released that disable/bypass the feature responsible for the said problem.
Due to the fact that I couldn't re-create said problem and as result couldn't solve it I've decided to abandon the archaic method of Batch scripting altogether and try to re-create UCC in a different Scripting language.
Why Now?
Well, solving problems and even getting things to work correctly with a Batch script become more of an headache than I ever wanted or expected, having to result into combining Batch/PowerShell/VBScript together made for decent visual result but a huge headache when it comes to problem solving and troubleshooting.
How will it work?
You may remember that I previously said I don't have the knowledge to re-create UCC in a better programming language, that is still true, "REAL" programming languages such as PHYTON, C++ and others are, for now beyond my skills and reach.
So what am I gonna do? Well, instead of a full blown programming language as described above I decided to go with another Scripting language, one which is both closer to programming and more compatible than Batch ever was and also relatively easy to learn on the go and more protected from Script stealing than Batch files.
What Language is that?
Well, I chose to go with AutoIT for the purpose of re-creating UCC, it appear to have all the options & features I need/want and is, as I previously stated above, relatively easy to learn on the go, which is a big PLUS for me.
What's the plan?
The original plan was to stay with the format I planned for UCC v4.1.4 when I tried to do it with Batch/Vbscript hybrid format, using message boxes, I since found out how simple it is to create simple GUI with AutoIT so much of the new version screens will be just that, simple GUI screens with timed display, other places, where user input is required will either be Message Boxes or Simple GUI screens with buttons that require the User to press OK to continue.
Overall, for the time being it will stay true to the way it was in the past, a fluent, text based script that will be shown in GUI format instead of Command Line Console.
Is that it?
No, that's only the first stage, once the script is completely re-written in above said format & released I plan to attempt and upgrade it to a full User Interface program, much in line with what you may know from UltraArc but still very different.
But that is a long way away.
How much time will it take?
The first stage, upgrading the 4.1.4 script from Batch/VBScript to AutoIT is already in Progress but relatively in the beginning stages, still, I'm attaching some first preview photos below that shows some proof of concept.
As for time, it's hard to say, my guess it could take anything between weeks to months, depends on how quickly I can progress and how hard it will be to program some of the more complex parts of the script.
As for the 2nd stage, the Full GUI program upgrade, I won't even hazard a guess before I finish the 1st stage.
Final Words:
That's it, the reasons for UCC v4.1.4 being put on hold & the future plans for it are laid out before you, I hope you'll be patient with me.
It does not mean in any way that I'll stop supporting the current & previous versions of UCC while I develop the next generation of UCC with AutoIT, if you have any problems I'll still be around to help and fix bugs wherever possible.
Screenshots:
Below are some screenshots from early development of UCC v4.1.4 with AutoIT, as well as a Concept of the GUI for the 2nd stage I mentioned.
AV Warning
Startup Screen
Source & Output
Stage 2 Concept
