>HI,
>
>I'm new in FoxPro.
>
>And my doubts are about how to make the visual class architecture. This visual class architecture should be used for many app projects. The main point is to padronize the user interfaces.
>
>I'm creating my visual class in just one vcx: "visual.vcx". This vcx is about 3.5Mb.
>I'm developping an app that uses almost only 10% of this vcx. And my project that can be with a few kbs, have 4Mb.
>
>My asks comes here: Is my "visual.vcx" in a bad architecture? Do any of you project visual class on two or more vcx? Anybody has a problem with it?
>
>Thanx,
>Marcos Lima.
Hi Marcos,
While it is possible to keep everything in one VCX, it is not a good design for bigger applications. You should separate the classes by functionality and inheritance levels. A smaller building blocks (VCXes) are easier to maintain and reuse.
Even small application will benefit from using the framework.
A good idea will be to look how the commercial frameworks are organized, if you want to build your own. If you are not using the commercial or one of the free frameworks, you must, rather than reinventing the wheel. It will save tons of time for developing and testing many classes/utilities that already exist in the frameworks.
Try these links
http://fox.wikis.com/wc.dll?Wiki~VFPCommercialFrameworkshttp://fox.wikis.com/wc.dll?Wiki~VFPFrameworkDomainshttp://fox.wikis.com/wc.dll?Wiki~EvaluatingFrameworks~SoftwareEngDo a search on fox.wikis.com on "framework" and you will get much more info.
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro
"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison