Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
When is too many .VCX is too many?
Message
 
 
To
07/03/2011 12:07:15
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01502837
Message ID:
01502852
Views:
63
>>Thank you very much. This is helpful as I also know very well all the names in my project and separating each BIZ into its own classlib would be helpful for project maintenance. Although I don't understand what you mean by "virtual categorization."
>
>Actually, I've found it much simpler to keep bizobjects in prgs - they have no visual representation anyway, so no reason for a vcx. And, besides, the prg-based classes make the exe much smaller and the instantiation is faster.
>
>Our old friend Peter R Robinson went to the extreme and made all his forms prg-based, and guess what, the size of his exe went down by at least half, and it instantiates in about 2 microjiffies.
>
>My rule is one prg per bizobj, except when I have subclassed it by only changing some properties and/or one or two methods, when they go in the same prg with their parent class.

All my BIZ objects are based on the custom class and they are all visual. I prefer - for ease of working with them - to have them in the VCX files.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Previous
Reply
Map
View

Click here to load this message in the networking platform