|
Templates, Tools and Utilities
for Clarion Developers
|
 |
 |
|
Add a comment to an Icetips Article
Please add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list
Search Articles
Add Comment
Printer friendly
Direct link
ABC: How to use your own abc derrived classes in new apps
1998-05-14 -- Richard Taylor
Newsgroups: topspeed.products.c4
> So again to re-phrase my original question, where is the means to make
>my own classes the default for a new app, so that the only classes that I
>have to set up manually, are those that are not used in every .app? I
don't
>see it documented anywhere. IMO it should be a setup parameter. I don't
>see them named in an .ini file.
OK, here's a simple but effective work-around: Create an APP with all the
defaults set the way you want them and call it "Master" (turn off "Require a
Dictionary" in Application Options so you don't need to name a DCT) and
don't ever do any real development with it. Then, whenever you want to
create a new APP just open "Master" and do a Save As to create your new APP
with all your defaults already set the way you want them, name the DCT to
use, then run the AppWizard!
> That's what I am doing now. But when I start a new .app, I have to set
>them all up again. That's what I want to avoid. I want the defaults to be
>what I have set them up to be.
>
> Using OOP in a program is piece of cake. I gave several examples
>earlier of how to change thinking and make it incredibly productive and
>useful. I've had lots of code waiting in the wings for C4 to get real.
Now
>that CW4 is real, I and likely a lot of people, will want to inherit the
ABC
>classes as a base to keep the templates happy, and extend the functionality
>of the ABC classes for use in their programs. Here's is why:
>
>First, we will be adding functionality to that language that we want to
have
>available in every program.
>
>Secondarily, we don't want to modify the standard ABC classes because they
>get hosed with every update, if they get extended, the template generated
>code likely use the new methods, and when they make changes to to the
>compiler and adjust the base classes back, we want to automatically take
>advantage of the fixes with no code maintenance to our classes.
>
>Thirdly, if we make our own classes that simply make use of their classes,
>the problem is we have to set up the classes every time by hand in the
.app.
>That just increases labor, maintenance, and debugging time. Having classes
>that are not used in every .app should be done manually, but not those used
>in every .app.
>
> So again to re-phrase my original question, where is the means to make
>my own classes the default for a new app, so that the only classes that I
>have to set up manually, are those that are not used in every .app? I
don't
>see it documented anywhere. IMO it should be a setup parameter. I don't
>see them named in an .ini file.
Today is November 21, 2024, 7:03 am
This article has been viewed 35332 times.
Google search
has resulted in 2 hits on this article since January 25, 2004.
Back to article list
Search Articles
Add Comment
Printer friendly
|
|
|
