This from Nigel Coates was useful:
>As you say - why should you change? The 'proper' technique should be the one >you feel happiest with. After all YOU are developing it, why make your own >life more difficult. I would recommend checking out the forms designer and VCX >library to see if it could make some things easier but if you're happy with >the non-visual approach, why change?
However, this from Albert Ballinger pinpoints the problem:
>I would like to have both visual and text forms convertable from one to the >other at any time. The visual tools give a handy organization. The interface >becomes cumbersome when global editing operations are done. Try renaming a >property in a visual class and all methods that access the property.
I occasionally use the forms designer to mock-up a new layout (and sometimes use GENSCO to convert to a prg). But as 95% of my development time is spent making the controls interact with one another programmatically, the visual approach is not much use to me. I now work with testbed project where I can cycle through run/modify with standalone prgs. All the controls are well in place long before I am satisfied with their interaction.
Once working properly, a module is copied into my main project and hooked up to menus, buttons and other forms. Instead of using the class browser, project-wide classes are in a SET PROCEDURE TO prg. Locally used classes are at the end of the local prg.
I'm wondering if FoxDoc is changed in vfp6.0 - this is my mainstay.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only