Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Classes that aren't in the QStart Project
Message
From
12/01/2002 00:13:54
Paul Williamson
Williamson Enterprises, Inc.
Livingston, Montana, United States
 
 
To
11/01/2002 21:29:40
Gil Munk
The Scarborough Group, Inc.
Baltimore, Maryland, United States
General information
Forum:
Visual FoxPro
Category:
The Mere Mortals Framework
Miscellaneous
Thread ID:
00603270
Message ID:
00603878
Views:
14
Hi Gil,

I just noticed that the a stuff (in addition to the c and k stuff) is pointed back to the MM directory also. I just assumed (shame on me) that Quick Start only copied the class libraries for the generic (a-classes) into the new project. I have much more digging to do in the framework!

I guess that makes sense since I will eventually be putting the classes, class libraries, tables, views, dbcs, etc.... back into the generic project.

I finally had a good day today) with the framework. I got my first MM form/class working. I am on a roll. Things are finally starting to click a bit! This is exciting (Monster!)!

Thanks,

-pw


>>Hi,
>>
>>Very, very basic MM question here!
>>
>>If there isn't a class I need in the application project created by Quick Start (like a form class or control class), do I copy the class library from the MM directory into the application directory or do I just point to it.
>>
>>In otherwords, does the class have to physically be in the temporary/application directory? If so, should I create a common or pwcommon directory for the, or just put them in the libs directory with the existing classes?
>>
>>Thanks,
>>
>>-pw
>
>Paul,
>
>If the MM framework class already exists, it should show up in you Project under the Classes tab. If it's a form class, you'll subclass that, as described in the Guide, andd save it to your aforms library. If it's a control you can drag and drop it onto a form.
>The guide gives a good talk on subclassing framework classes, with advantages and disadvantages on where you decide to subclass (where inheritence is broken) so read that and go from there.
>Your first application created using the framework should be thought of as a learning ground (you'll get better as you go) but with keeping the guide by your side and reading reading reading it and reading the comments in the parent class's methods you'll do just fine.
>
>Kevin's classes are a great jump start too and highly recommended.
Previous
Reply
Map
View

Click here to load this message in the networking platform