![]() However, classes don't work exactly the same way. I was in heaven! My customers got more software for less money, and I could win every single bid I made. ![]() I ended up with a form that did what I needed if I set a dozen or so properties if I needed a similar form, I just usedĪnd set the same dozen properties, and the form was up and running in minutes. Gradually, most if not all of the code in the original form migrated to the class. I could base a form on this "form template," assign a value to the MainTable property, and the form would run as expected. My own approach was to build a basic form and then slowly move code out of it into an underlying class, changing form references to a specific table name to the contents of a property, so if I changed When Visual FoxPro came out, for the first time we had the ability to write generic form class code and inherit forms from it. But subsequent design changes could be painful. There was a template capability that allowed us to migrate features to the template and then stamp out similar forms like a cookie- cutter. ![]() ![]() If we needed a similar form, we cloned and modified the code. Many FoxPro developers began with version 1, which didn't have object orientation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |