This is probably not news to a number of you who are already set up this way and work with VMWare under Windows Vista 64.
I bought a new laptop a few weeks back and decided on the recommendation of Jack Leininger at Fabtex ( a CHT customer) to buy a nice, compact 14 inch HP laptop with 4 gig of RAM and Windows 64 installed. I was going for maximum mobility here, not screen size so I asked specifically for the smaller screen size and a good, thin case.
Again on Jack's recommendation I added VMWare and installed 32 Bit Windows XP as a working O/S to use with Clarion 6.3.
That all went well and this arrangement is flawless. The Clarion installation and CHT in this environment run quickly, and efficiently. It's also a great way to multi-task with Clarion 6 and CHT Compile Manager in the mix, since you can minimize the 32 bit environment when it's busy and do some correspondence or other work back in the 64 bit environment or even in a second or third Virtual O/S set up this way.
Windows Vista 64 has proven to be painless experience compared to earlier Vista 32 encounters. If you're into multi-tasking and 32 bit O/S variants this is a great way to go.
Cheers...
Gus M. Creces
http://www.cwhandy.ca/
http://news.cwhandy.ca/
Wednesday, August 27, 2008
CHT Build Update 12C1.01 Posted
We've just updated the 12C1.00 build to 12C1.01.
This includes some necessary changes for better backward compatibility to C6.1 and C6.2. Perhaps a waste of time since it appears there are only 2 of you in our subscriber base still using these older Clarion 6 builds.
It also includes some unfinished business with some of the SQL demo apps, particularly HNDSQL9.APP which uses ListBoxBrowseExtender, plus two of the new SQL extensions to build a browse application very similar to a HandyMarkerBrowse (like HNDSQL8.APP) but without using an ABC browse at all. All aspects of filling the listbox are entirely under your control. This app was constructed by a combination of ABC and CHT templates (ABC Window + ListBoxBrowseExtender + QueryparsingFilterControl) and a few hand-embeds. This browse does away with a lot of ABC code that slows data access and makes browses waaaay more complex than they need to be.
If you think this is useful to you, we're willing to formalize this approach into a single procedure template that lets you build a procedure like this without the hand-embedding. The procedure template will populate the necessary pieces for you and complete the embeds based on your completion of template prompts.
On the other hand, if you don't think it offers anything new, we're also happy to leave this just as it is, an example of how to build an SQL browse without an ABC browse template. I'll wait to hear from you all.
We've put off documenting C121.01 until these final changes were complete. At the same time I've personally been occupied with contract development work that takes up a lot of my time these days. I've got time this week, to get some of those 12C1.00/01 features to you now and perhaps a few new videos.
We've taken SQL tracing even further in 12C1.00/01. You're now able to trace directly from a specific browse directly to CHT SQL Trace without turning on full SQL tracing. This new mode is called "Direct Trace". You can experiment with this using HNDSQL7.APP, HNDSQL8.APP and HNDSQL9.APP if you recompile them in debug mode. The browses in these apps will output directly to CHT SQL Trace if you put it in [DIRECT TRACE ON] mode.
Also in HNDSQL7.APP and HNDSQL8.APP, take note of two alternative ways to fill the browses, particularly OBJ.SQLSelect().This method lets you fill an ABC browse queue using an SQL select statement. The method interfaces to the ABC method SetQueueRecord() for queue filling, in a manner that stores the VIEWPOSITION as required by all ABC browses.
And in HNDSQL9.APP take note of a method called OBJ.SQLSelectQ() which fills your list box queue for you exclusive of an ABC browse being present. Take note also of a record fetch method used in this app called OBJ.SQLSelectRecord(). If you're familiar with SQL you'll find these new methods, and others I've added to be more compact and more transparent than standard ABC file object syntax.
The latest docs can be found in your installation or here:
CHT Templates By Category
CHT Demo Applications
CHT Templates New/Revised In 2008
Cheers...
Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca/
http://news.cwhandy.ca/
This includes some necessary changes for better backward compatibility to C6.1 and C6.2. Perhaps a waste of time since it appears there are only 2 of you in our subscriber base still using these older Clarion 6 builds.
It also includes some unfinished business with some of the SQL demo apps, particularly HNDSQL9.APP which uses ListBoxBrowseExtender, plus two of the new SQL extensions to build a browse application very similar to a HandyMarkerBrowse (like HNDSQL8.APP) but without using an ABC browse at all. All aspects of filling the listbox are entirely under your control. This app was constructed by a combination of ABC and CHT templates (ABC Window + ListBoxBrowseExtender + QueryparsingFilterControl) and a few hand-embeds. This browse does away with a lot of ABC code that slows data access and makes browses waaaay more complex than they need to be.
If you think this is useful to you, we're willing to formalize this approach into a single procedure template that lets you build a procedure like this without the hand-embedding. The procedure template will populate the necessary pieces for you and complete the embeds based on your completion of template prompts.
On the other hand, if you don't think it offers anything new, we're also happy to leave this just as it is, an example of how to build an SQL browse without an ABC browse template. I'll wait to hear from you all.
We've put off documenting C121.01 until these final changes were complete. At the same time I've personally been occupied with contract development work that takes up a lot of my time these days. I've got time this week, to get some of those 12C1.00/01 features to you now and perhaps a few new videos.
We've taken SQL tracing even further in 12C1.00/01. You're now able to trace directly from a specific browse directly to CHT SQL Trace without turning on full SQL tracing. This new mode is called "Direct Trace". You can experiment with this using HNDSQL7.APP, HNDSQL8.APP and HNDSQL9.APP if you recompile them in debug mode. The browses in these apps will output directly to CHT SQL Trace if you put it in [DIRECT TRACE ON] mode.
Also in HNDSQL7.APP and HNDSQL8.APP, take note of two alternative ways to fill the browses, particularly OBJ.SQLSelect().This method lets you fill an ABC browse queue using an SQL select statement. The method interfaces to the ABC method SetQueueRecord() for queue filling, in a manner that stores the VIEWPOSITION as required by all ABC browses.
And in HNDSQL9.APP take note of a method called OBJ.SQLSelectQ() which fills your list box queue for you exclusive of an ABC browse being present. Take note also of a record fetch method used in this app called OBJ.SQLSelectRecord(). If you're familiar with SQL you'll find these new methods, and others I've added to be more compact and more transparent than standard ABC file object syntax.
The latest docs can be found in your installation or here:
CHT Templates By Category
CHT Demo Applications
CHT Templates New/Revised In 2008
Cheers...
Gus M. Creces
The Clarion Handy Tools Page
http://www.cwhandy.ca/
http://news.cwhandy.ca/
Subscribe to:
Posts (Atom)
