Full template re-work continues. Latest revised templates are marked "Revised October 2018". Latest revisions have RED tabs and white backgrounds. Approx 210 of 408 templates revisions complete. Jumpstarts (85-Yet-To-Do)
Target full completion date approx mid december 2018.
Template Revision# - 22D.00.00.07
Full template re-work continues. Latest revised templates are marked "Revised October 2018". Latest revisions have RED tabs and white backgrounds. Approx 200 of 408 templates revisions complete.
Target full completion date approx mid december 2018.
Template Revision# - 22D.00.00.06
Full Template Re-Work continues. Latest revised templates are marked "Revised October 2018". Latest revisions have RED tabs and white backgrounds.
Template Revision# - 22D.00.00.05
Full Template Re-Work continues. Latest revisions are marked "Revised October 2018". Latest revisions have RED tabs and white backgrounds. Newest Template interfaces look great both in C10 or C11.
Template Revision# - 22D.00.00.04
*** BEGIN BACKGROUND ***
Peter found he could not install our C11 version on his machine because our installer could not find C10 installed on his machine - because it wasn't.
*** END BACKGROUND ***
*** BEGIN REPLY ***
Our C11 installer at present, is a C10-to-C11 "cross installer".
We explained this on our website September What's New Pages when C11 was released as well as on our user forum.
-- SEE SEPT 18, 2018 ( http://www.cwhandy.ca/september2018.htm )
-- RUN OUR FORUM APP /ACCESSORY/BIN/HNDBRWCL.EXE from your C10 installation.
Since our implementations for C11 and C10 will continue to use exactly the same CHT templates and classes, and most (but not all) of the same componentry, we decided that for the purposes of "evolving" developers interested in using Clarion 11 with their apps, we would initially provide for Clarion 11 testing, a Clarion 11 "Cross-Installer".
This cross-installer installs some CHT-for-C11 components from it's own container while at the same time it cross-copies a lot of components from your C10 install. That's why it checks to see if you have our latest C10 version installed on the same machine. Clarion 10 and Clarion 11 can co-exist on the same machine quite readily, no conflicts that we've encountered.
However, we're still busily revising our C10-C11 template interfaces to conform to what is now two different template interfaces (C11 has larger template interfaces). This is being done, in order to keep our templates exactly the same for both C10 and C11.
We will maintain the C11 installer in it's "cross-installer" state until at least mid December 2018. At which time we will introduce a standalone C11 installer that does not require Clarion 10 be installed on the same machine.
*** END REPLY ***
In the meantime, we're updating our templates on a regular basis as we continue to revise the interfaces to our satisfaction. These revisions come numbered in the following not-standard-to-CHT format: 22D.00.00.01, 22D.00.00.02 and so on. Last night's release was numbered 22D.00.00.03.
CHTSETUP.EXE (for C10) looks as follows:
CHTSETUPC11.EXE (for C11) looks as follows:
OMG (Oh My God!) Clarion 11 Gold Released!
Nothing wrong with that, I suppose. It HAS, after all, been 3 years of Clarion 10. That's more C10 time than most of us dared to expect. Plenty of time to fix its major bugs.
The problem, as we see it, with Clarion 11 going gold today, is that it's NOT ready.
First of all, the primary reason any one of us might have wanted take a chance on Clarion 11, is missing. SV didn't get it working, that is, the "Unicode/RTL/Compiler/Drivers Implementation" (See next image)
At the same time, Clarion 11 has re-introduced some bugs (regressions) already fixed in C10. These regressions are, in our opinion, the result of SV branching to C11 from an earlier C10 version that contained these bugs and then not fixing them in the C11 branch as they were being fixed in the C10 branch, that the rest of us were using.
Don't get us wrong, here. Clarion 11 IS GOOD ENOUGH to start using it. The two products, are really not that different!
In light of this C11-Gold release we will proceed with our C11-Stand-Alone installer as soon as feasible. (APPROX DECEMBER 2018)
Our present C11 installer, CHTSETUPC11.EXE is what we're calling a "Cross-Installer". It cross-installs critical CHT components across from your C10 installation. And it's not a complete install, in that it only installs absolutely essential features, required to allow you to test it with your own apps and a sampling of ours.
If it is your intention is to continue only with C10 for the next 3 years, we wouldn't blame you a bit!
In spite of this announcement from SV about C11, CHT will continue to forward develop for BOTH C10 (for the next 3 years) AS WELL AS C11.
Our templates being shipped now are THE SAME for C10 and C11 anyway. And your subscription enables you to install both C10 and C11 versions of CHT without extra cost.
So it doesn't matter to us what you decide to do about C11-vs-C10. We're ready for you to decide for yourself which way to go.
The following information pertains to Clarion 10 and Clarion 11 as regards code-generation speed and efficiency.
It is a long-known fact that the more templates you register, the bigger the .TRF file becomes. That stands to reason, of course, since the .TRF (Template Registry File) is a data table and every template registered (multiple templates in any .TPL chain) becomes a data record. (Not exactly, but close enough for this discussion).
It is also a long-known fact the more frequently you re-register your templates, even the same ones, over and over, the bigger the .TRF file becomes. Though you might have only 3 .TPLs registered, as we do here, the template registry file can grow to enormous size over time because we're constantly re-registering our HNDTOOLS.TPL file as we make changes to our templates.
It is likewise a long-known fact that the bigger the .TRF grows, the slower the .IDE performs. That's because the IDE has to search through a much bigger .TRF to find the necessary template code required by the APP. As data base developers, you know this already, that the bigger the data table (especially ISAM), the more time it takes to find a particular set of records.
So, why are we telling you this again now, in the context of Clarion 11, when the knowledge imparted above is not new?
Take a look at the accompanying image.
# Item (1) shows the size of our template .TRF file after installing Clarion 11. Note that we renamed this to TemplateRegistry11.OLD to get rid of it. It was full of Clarion templates from SV that we NEVER use and will never use. Including now the legacy templates for heaven's sake!
# Item (2) is a list of registered templates that we re-registered into a new TemplateRegistry11.TRF. These are:
ABC, HNDTools, SVReportToPDFSupport. Yes, that's all the Clarion templates we use in 100% of our 230+ CHT demo and utility applications!
# Item (3) shows the new size of our TemplateRegistry11.TRF after getting rid of the old one and registering only the required 3 templates that we need and use. After all, why keep templates we're never going to use registered at all? They just get in the way and slow our IDE to a crawl.
That constitutes a size reduction from 256,904,564MB to 12,882,296MB. The new .TRF is 19 times smaller than the original .TRF!! We haven't measured whether the experienced speed increase of our IDE is also X19 but, nevertheless, the speed-up effect of a smaller .TRF is obvious in practice.
Template re-registration happens now in a fraction of a second. Our apps generate blazingly fast.
Why is that? We attibute this speed increase to having the smallest possible .TRF.
Since the same effect is possible in Clarion 10, have you looked at your Clarion 10 .TRF lately? How may templates do you have registered that you're not even using? How many times have you re-registered the same templates over and over again, in the 3 years since you installed Clarion 10? How unnecessarily large has your Clarion 10 .TRF grown? What, if anything, have you done about it?
This follows on TRF Best Practices #1. We suggest you read that first if you haven't already done so.
We practice what we preach on this .TRF size best practice information imparted in our earlier essay.
Check out this image:
The upper part of this image, labelled (1) shows a chronological list, newest to oldest of .TRF files ranging from newest (at the top) to oldest at the bottom.
In every one of these .TRF files we had only 3 templates registered, as shown in the image labelled (2). These are again, ABC (ABCHAIN.TPL), SVReportToPDFSupport (RTARPDF.TPL) and HNDTools (HNDTOOLS.TPL).
The same 3 .TPL files were registered the whole time, yet the .TRF file sizes range from 568,117,984 to 12,865,296!!
Remember, as we indicated in our previous post, that .TRF size varies, for at least two reasons:
• 1) the number of templates registered
• 2) the number of times templates (the same ones) are re-registered
In our case, we re-register our templates A LOT, especially at times like the present, when we're working on them A LOT.
The way we see it, the only practical way to manage .TRF size, in order to keep your IDE code generation working at it's optimum, is as follows:
• 1) Unregister any template sets you're not using in your apps.
• 2) Re-build your .TRF from scratch on a regular basis, especially after unregistering templates you're not using.
But what templates are you using in your app? How can you find that out without spending hours opening and looking at every procedure in the .APP.
Our toolkit has a template on AACHTControlPanel called "Templates By Proc" which makes a list of EVERY template (not only CHT templates) being used in your application on a procedure-by-procedure basis. Run that template, with your app loaded, and you'll know ahead of time the templates required by that APP.
Using that information, you can trim your registered templates down to just those that you need for the apps you work on most of the time. Once you know that, rename your TemplateRegistry10.TRF (don't delete it) and have the .IDE create a new TemplateRegistry10.TRF containing just the .TPL files you need for your apps.
You will be amazed how much better your IDE performs with a fresh, LEAN and CLEAN, .TRF!!!
When you begin to put Clarion 11 candidate-release through preliminary testing, here are some suggestions for configuration that we think are imporant.
Above Image Explained:
When your Clarion 11 icon is placed on the Windows 10 desktop, right click it and configure the link to "Run As Administrator". Also, any time you install a later version of Clarion 11, you will need to repeat this step, since re-installing removes the old desktop icon and creates a new one which is missing the "Run As Administrator" setting.
Above Image Explained:
In the "Application Options" area, under "Embed Editor" check (SET ON) the item that asks, "Edit Source Embeds in Context by default (Embeditor)". This switch defaults to OFF for some reason, that defies logic. Check this switch, and set it to ON. That'll save you a whole lot of frustration when you're fixing typos in any embedded code. In fact, keep both of these switches in the "ON" state.
Above Image Explained:
Again in the "Application Options" area, under "Generation" uncheck the "Conditional" generation switch. Keep this switch OFF. This makes full application regeneration after code changes more likely to be applied.
Above Image Explained:
In the "Application Options" area, under "IDE" uncheck the switch that asks, "Edit Embedded Source Errors in Generated Code". This will keep your embedded code fixes inside the Embeditor so that you're always sure that after saving any change and compiling it, the change is actually applied into newly generated code.
These are the settings that we've found are important to the way we work. In all cases these settings are not the defaults with which a new Clarion 11 IDE is installed, so you have to manage them yourself.
In a later post, we have more configuration information coming which discusses "Options" settings, ".RED" file settings, as well as template registry file (.TRF) maintenance.
Our Clarion 11 -- Cross-Installer -- CHTSETUPC11.EXE -- is up and available on our developer download site. The URL for this is: CHT Developer Download Site
Since this is a "cross-installer", it requires that you have the latest CHT version -- i.e. Build 22D.00.00 -- installed on your hardware, and that you have Clarion 11 installed on the same hardware.
This cross-installer checks your required credentials and expiration date from the Windows Registry entries placed by your Clarion 10 installation.
You must initially update your Clarion 10 installation by running CHTSETUP.EXE until it offers to run WEBUPDATERC10.EXE by prompting you. When that prompt appears, run WebupdaterC10 through all 6 steps in the usual way. You can find the latest CHTSETUP.EXE also at our developer download site:
CHT Developer Download Site
Once that's done, download CHTSETUPC11.ZIP and run it, after first extracting it as instructed at:
CHT Developer Download Site
Once that completes, register HNDTOOLS.TPL to your Clarion 11 IDE and after that, you are ready to try and compile some apps containing CHT templates. You will find a few C11-ready test apps and .DCT's located in the /hndapps/ directory below your Clarion 11 root.
If you have questions or need assistance, feel free to contact us at: email@example.com
All the best from CHT!
Depending on your time zone, active CHT subscribers can expect an email from us today - sent approx 6pm EDT, October 1, 2018 - containing our new Clarion 11 "Cross-Installer". This will set you up to use CHT with your Clarion 11 pre-release, so that you can begin testing existing apps and creating new CHT-based apps in Clarion 11. This cross-installer will be called CHTSETUPC11.EXE and is packed in a zip along with security a certificate. It also extracts it's own container, containing some Clarion11-specific CHT componentry - more about this below.
As we discussed earlier on our support forum, and on our September 2018 "What's New" pages, our "Cross-Installer" assumes you have the latest version of our toolkit, Build 22D.00.00 (available as of Sept 30, 2018) installed to your Clarion 10, and that you have your Clarion 11 installed on the same machine as your Clarion 10.
The "Cross-Installer" copies the necessary C10 directories, utilities, and drops our new C11 template DLL to your Clarion 11 directories. It also prepares any necessary "blank" directories under
/accessory/hnd/ as required by our templates, and creates the necessary Windows Registry entries pertaining to CHT for Clarion 11.
Also, a certain number of CHT utilities, such as HNDCMP.EXE, HNDPREVIEWER.EXE, HNDBACKUPCONFIG.EXE (about 12 utilities in all) have been re-compiled and re-configured in Clarion 11 to use a different registry location to store their config information, so that these utilities may run independently of their Clarion 10 equivalents without interference between them. These utilities are not "Cross-Installed" from C10 as they are shipped separately in your CHTSETUPC11.HZO. (The installation container provided by CHTSETUPC11.HZO).
The templates and classes for C10 and C11 are identical at this point and we hope to keep them that way. Most components, except those mentioned above, ARE and WILL CONTINUE to be identical.
This is how we will proceed with Clarion 11 at least until it goes gold, at which time CHT for Clarion 11 will become a stand-alone installation and Clarion 11 receives its own WebupdaterC11.EXE. At that point you will be able to run Clarion 11 and CHT for Clarion 11 on hardware that does not necessarily (BUT COULD) have a CHT for Clarion 10 installation.
Even at the point where Clarion 11-Gold is announced, we will continue forward development of CHT for Clarion 10 in exact parallel with CHT for Clarion 11 into the forseeable future.
Any CHT developer that intends to test the Clarion 11 pre-release in the near future, should update their CHT version to Build 22D.00.00 as soon as possible, starting today.
And look for an email from us, with a link to our CHT C11 Cross-Installer.Gus Creces
If your Webupdater C10 is dated prior to OCT.01.2018, you should visit our Download Site to download our latest CHT "Pre-Installer", in the form of a file called CHTSETUP.ZIP as you've let your CHT toolkit fall behind the rest of us. The latest CHT version is currently Version: 22D.00.00 - OCT 1, 2018.
CHTSETUP.ZIP contains CHTSETUP.EXE and two security certificates. The included certificates are optional. However they are provided, in order to moderate the challenge raised by Windows 10, when you take the time to install the certificates first, by clicking on them one-by one. If you decide for the certificates first, please install them to "Trusted Root Certification Authorities" or best results.
CHTSETUP.EXE is what we call a "Pre-Installer". Feel free to run it any time in order to get a "news brief" about what we're up to. It opens a text file on your desktop, called CHTTODO.CLW that we hope you'll read regularly, bi-weekly, or even daily. What's in this text file is explained briefly below.
CHTSETUP.EXE also provides the latest versions of 4 or 5 CHT UTILITY APPS that we're currently featuring. We change these periodically to bring them foremost to your mind. They tie in with some of the "PLEASE TRY THIS" tasks which are part of our CHT "NEWS BRIEF". Included currently is a newer version of HNDBRWCL.EXE, the CHT forum browser, and 3 others.
CHTSETUP.EXE also creates a small, separate set of menus on your PC, located under the "&" symbol near the top of your Windows 10 menu. We'll keep this menu short, under 10 items, with some items changing from time-to-time. However, always found in this list are two key items: "@CHT SETUP-C10", and "@WEBUPDATER-C10". They're our key installation and upate applications.
If you encounter problems or have any questions, please contact us using the email link at the bottom of this page, with a description of the problem or with your questions.
If you have any thoughts or impressions to share, feel free to get back to us via email using the hot link provided here.
Click the link below. It will start your email client with our email address inserted: