Title: Lisa's First Class

Date:
Clarion Date:
Duration:

Download Recording

Hosts: Arnold Young, John Hickey, Lisa Daugherty, Mike Hanson


Presenter: Mike Hanson, Lisa Daugherty


Description:
Using Local Classes offer many advantages over local routines but only take a small amount of additional work, i.e. the declaration of the each local procedure. If you start with local classes from the beginning you'll avoid the work Lisa has to do to convert. Since these are procedures you can pass them values and return values. One of the benerfits is the code is encapuslated inside the class. It should be possible to move the code outside of the procedure and into its own class file. This would allow reusing the code in multiple procedures or projects, and inheriting it to create new classes. It would also allow testing the code using Clarion test.
So instead of creating a routine like "MyLittleBitOfCodeRtn ROUTINE" instead create a local procedure in a class:
MyLittleCls CLASS
BitOfCode PROCEDURE()
END
MyLittleCls.BitOfCode PROCEDURE()
CODE
RETURN

Announcements:


Old Business: None


New Business: None


Word.Of.The.Day:


Topics Covered:


Additional Downloads: None


Slide Show:


Time Events:

Time
Event
0:00
0:09
0:22
1:08
1:11
1:14
1:17
1:19
2:44
2:51
Webinar Introduction
Bob Zaunere - Clarion News, Clarion 9.1, Clarion.Net 4.x
Diego showing Touch in Clarion 9.1, Tile Class buttons
Code Smell: Refused Bequest - a derived class that doesn't use much of the base class
Free tools - XML Schema Generator
Bruce shows XML files opened in the #IDE unhide an XML menu with validate, create schema, run XSLT.
Bruce discusses C8 to C9 conversion issues
Lisa's first class. Local routines converted to procedures, then to a class.
Review and summary list of converting routines to a class
Wrap up and future topics


Webinar Recording


Fourth Rule Of The Webinar:


Discussion:


comments powered by Disqus