Messages
Reply
Edit
Delete12:52 pm
3SO0RLJHO
| From: | San2013 |
| To: | Jeff Barefoot |
My WebProcess.prg also grows fast.
I am going to check the VFP Built-In Class Browser (Menu/Tools/Class Browser). At least, it will allow me to quickly jump to any method or property.
I had to replace
DEFINE CLASS WebProcess AS WWC_PROCESS
with
DEFINE CLASS WebProcess AS wwProcess OF classes\wwprocess.prg
in order to be able to open the prg in the Class Browser.
My WebProcess.prg contains all of the custom functions that do the work and call the individual pages in my WebConnect application (pretty standard...I think that's the way that it would normally work). It's working just fine, but becoming a little unwieldy. It currently contains 30 custom functions, and about 4000 lines of code. Not huge...I know...but I'd love to be able to organize my functions by type (reporting, security, utility, viewing data, etc).
What is the "Best Practice" for WebProcess? Is it easier to keep everything in a single .prg and bounce up and down to access, or is there an easy way to create multiple .prg's to contain the neatly organized functions? If there is an easy way to make the change, can you point me to an example of how to make it work?
It's not a big deal, and I don't want to spend a lot of time on it....was just hoping that there might be a quick way to reorganize my stuff.
Thanks,
Jeff