We've completed, recorded and posted for viewing and download, our CHT DOT NET Seminar Series #1 (6 videos Approx 15 Hours). The series is currently being edited to shorten it a bit (to approx 12 hours) and to smooth out some of the rough spots.
Editing will take at least another month, probably longer, before we're prepared for a retail release of this. In the meantime, some of you have expressed interest in viewing and interacting with this video series "in the rough" since you couldn't fit the live presentations into your busy schedule.
If you're still interested, visit this page (http://www.cwhandy.ca/dotnettraining.htm) to find out more. Below the "Cost" section near the bottom of the page is a "Seminar X Details" list that elaborates topics covered and even provides a ten minute preview of each of the 6 videos.
Seminar videos may be streamed for on-line viewing or downloaded for more at-your-convenience interaction. Approximately 100 source code samples in C# and Clarion# are included along with a free 267 page PDF book by Charles Petzold called ".Net Book Zero".
Purchasers of the "rough cut" videos will, of course, be given both stream and download access to the "final cut" at no extra charge, just as the "live" seminar participants are being given access to both the "rough cut" and "final cut" videos.
Cheers...
Gus M. Creces
The Clarion Handy Tools Page
usersupport@cwhandy.com
The CHT Blogger
Thanks for your interest in The Clarion Handy Tools, an awesome collection of productivity enhancements for Clarion developers. These tools consist of an ever-expanding set of Clarion Templates and OOP Classes that extend or complement the normal functionality of the Clarion Application Development System from SoftVelocity.
Friday, June 11, 2010
Wednesday, June 9, 2010
Build Update Posted (14B1.01)
We've just posted the 14B1.01 Build (Dated June 7, 2010) for C6 and C7.
For a list of new and revised templates consult these links:
http://www.cwhandy.ca/chttemplates2010.html
http://www.cwhandy.ca/chttemplates2010.pdf
Have a look also at a new demo app called HNDTESTUTILITIES.APP. This app, while not quite finished illustrates use of a CHT dll called HNDUTILITIES.DLL which repackages HNDUTIL.INC/CLW as a set of MAP procedures (like Clarion's Builtins). This DLL can be attached to any dll-style application to add 100+ low level functions globally into your app. Take a look at HNDTESTUTILITES.APP for examples of things that this DLL can do.
The list of functions with explanations of what they do can be found in your libsrc directory and is called HNDUTILITIES.CLW. You can also recall this list of functions from the global template GlobalIncludeHNDUtilitiesDLL.
There's nothing this DLL does that our HNDUTIL class doesn't already do but it can be used as a DLL based alternative in situations where you might normally use the HNDUTIL class. The procedure packaging as I've said in this case is not class-based but MAP based so the calling convention is different and the prototypes and procedure names are not necessarily the same.
My intention with this and another couple dozen CHT classes is to produce these as stand-alone products for C6 and C7, that I can sell separately to developers who just won't buy into the subscription scene and who buy bits and pieces here, there and everywhere and then complain like hell that their supplier hasn't kept his product up to date with the latest Clarion version. I'm including these, of course, as part of your full CHT subscription package (even the source code for the DLL itself - see next paragraph)so you can use them or not as you see fit. They may help you decide to ditch some specific-use 3rd party functionalities that you didn't know were already in CHT.
If you're interested how the DLL was created, look at an app called HNDUTILITIES.APP. This is the app that I use to actually create the DLL and export functions from it. Be careful with this app as it will generate a second copy of the DLL and a file called HNDUTILITIES.CLW. If you do decide to compile this DLL, make sure to get rid of the HNDUTILITIES.CLW file that it generates as it name clashes with the MAP file that we've inserted into your libsrc directory with commented prototypes for the DLL.
I welcome suggestions and comments on these new components so feel free to make them.
Cheers...
Gus Creces
The Clarion Handy Tools Page
www.cwhandy.com
gcreces@gmail.com
June 8, 2010
For a list of new and revised templates consult these links:
http://www.cwhandy.ca/chttemplates2010.html
http://www.cwhandy.ca/chttemplates2010.pdf
Have a look also at a new demo app called HNDTESTUTILITIES.APP. This app, while not quite finished illustrates use of a CHT dll called HNDUTILITIES.DLL which repackages HNDUTIL.INC/CLW as a set of MAP procedures (like Clarion's Builtins). This DLL can be attached to any dll-style application to add 100+ low level functions globally into your app. Take a look at HNDTESTUTILITES.APP for examples of things that this DLL can do.
The list of functions with explanations of what they do can be found in your libsrc directory and is called HNDUTILITIES.CLW. You can also recall this list of functions from the global template GlobalIncludeHNDUtilitiesDLL.
There's nothing this DLL does that our HNDUTIL class doesn't already do but it can be used as a DLL based alternative in situations where you might normally use the HNDUTIL class. The procedure packaging as I've said in this case is not class-based but MAP based so the calling convention is different and the prototypes and procedure names are not necessarily the same.
My intention with this and another couple dozen CHT classes is to produce these as stand-alone products for C6 and C7, that I can sell separately to developers who just won't buy into the subscription scene and who buy bits and pieces here, there and everywhere and then complain like hell that their supplier hasn't kept his product up to date with the latest Clarion version. I'm including these, of course, as part of your full CHT subscription package (even the source code for the DLL itself - see next paragraph)so you can use them or not as you see fit. They may help you decide to ditch some specific-use 3rd party functionalities that you didn't know were already in CHT.
If you're interested how the DLL was created, look at an app called HNDUTILITIES.APP. This is the app that I use to actually create the DLL and export functions from it. Be careful with this app as it will generate a second copy of the DLL and a file called HNDUTILITIES.CLW. If you do decide to compile this DLL, make sure to get rid of the HNDUTILITIES.CLW file that it generates as it name clashes with the MAP file that we've inserted into your libsrc directory with commented prototypes for the DLL.
I welcome suggestions and comments on these new components so feel free to make them.
Cheers...
Gus Creces
The Clarion Handy Tools Page
www.cwhandy.com
gcreces@gmail.com
June 8, 2010
It's Time To Connect With The DOT NET Coding Revolution
Since the release of Microsoft's C# 1.2 -- in October 2003 -- and the evolution of DOT NET 1.0 through to DOT NET 4.0, a lot of things in the application development world have evolved in ways that have not included Clarion. That is, until recently, given the ever-so-gradual evolvement of Clarion Sharp.
In March of this year, it occurred to me that it was time that Clarion# was taken out for a few hard laps around the track to compare -- or perhaps contrast -- its capabilities feature-for-feature against C#. Since C# is the defacto .NET language, despite the introduction of numerous "Sharp" languages in the last seven or eight years, I wanted to see whether SV's Clarion# language implementation was a worthy member of the .NET language community, which includes, C#, F#, A# GTK#, Qt# and others.
Since having adopted C# as my second-favorite development environment after traditional Clarion, I came to realize that much of what I was doing as a toolmaker for Clarion Win32 involved expansion of the language to fill the ever-widening gap between Clarion and the operating system. Suffice it to say, I found myself in the last couple of years, backfilling missing pieces in Win32 Clarion using C# DLLs hooked into Clarion six and seven using an intermediate technology called COM. Perhaps the time had come to think seriously about making .NET
my default coding environment.
What I found was an eye-opener! The Clarion# language is ready to be used today even before a template generator is added into the Clarion.NET IDE. It implements most coding concepts available to C# - with a few exceptions such as operator overloading - and runs as fast as C# - with a few exceptions such as methods using boxing and unboxing techniques.
The only problem -- getting Clarion 6 and 7 users to believe it! Not that I blame them for having reservations, since I didn't really believe it myself until designing and giving a DOT NET Seminar Series based on a free PDF book by Charles Petzold called .NET Book Zero.
During the months of April and May 2010 these six seminars were given on-line, three times each week using GoToMeeting. We recorded the Friday (3rd presentation) of each of the six seminars and have packaged them - warts and all - for interested developers who couldn't fit the on-line seminars into their busy schedules. Read about how you can take these seminars yourself, what prerequisites are needed to take them, and view a summary of each video's contents. Click here to do that.
Cheers...
Gus Creces
The Clarion Handy Tools Page
www.cwhandy.com
gcreces@gmail.com
June 1, 2010
In March of this year, it occurred to me that it was time that Clarion# was taken out for a few hard laps around the track to compare -- or perhaps contrast -- its capabilities feature-for-feature against C#. Since C# is the defacto .NET language, despite the introduction of numerous "Sharp" languages in the last seven or eight years, I wanted to see whether SV's Clarion# language implementation was a worthy member of the .NET language community, which includes, C#, F#, A# GTK#, Qt# and others.
Since having adopted C# as my second-favorite development environment after traditional Clarion, I came to realize that much of what I was doing as a toolmaker for Clarion Win32 involved expansion of the language to fill the ever-widening gap between Clarion and the operating system. Suffice it to say, I found myself in the last couple of years, backfilling missing pieces in Win32 Clarion using C# DLLs hooked into Clarion six and seven using an intermediate technology called COM. Perhaps the time had come to think seriously about making .NET
my default coding environment.
What I found was an eye-opener! The Clarion# language is ready to be used today even before a template generator is added into the Clarion.NET IDE. It implements most coding concepts available to C# - with a few exceptions such as operator overloading - and runs as fast as C# - with a few exceptions such as methods using boxing and unboxing techniques.
The only problem -- getting Clarion 6 and 7 users to believe it! Not that I blame them for having reservations, since I didn't really believe it myself until designing and giving a DOT NET Seminar Series based on a free PDF book by Charles Petzold called .NET Book Zero.
During the months of April and May 2010 these six seminars were given on-line, three times each week using GoToMeeting. We recorded the Friday (3rd presentation) of each of the six seminars and have packaged them - warts and all - for interested developers who couldn't fit the on-line seminars into their busy schedules. Read about how you can take these seminars yourself, what prerequisites are needed to take them, and view a summary of each video's contents. Click here to do that.
Cheers...
Gus Creces
The Clarion Handy Tools Page
www.cwhandy.com
gcreces@gmail.com
June 1, 2010
Subscribe to:
Posts (Atom)