I originally started with the editors because I wanted something as simple as line numbers displayed and the ability to move the edit window from the VFP main window to a second monitor. I also wanted other features as well like column selection. I didn't want to lose the code completion and intellisense capability -- so these were added in as well. I found the CodeMax editor control several years ago and thus started the "adventure" (this was sometime during VFP7 days).

I had thought about offering the toolset as commercial, but then I would have to add better support. Also, I have found much help and ideas on UT that I felt it would be good to share back with the community.

I don't work in VFP anymore as a profession (I am a SAP consultant and work with Java/ABAP and the Netweaver toolset), so I don't have the time for support. But as a consultant I do have evenings in a hotel room -- not much on TV so I would rather develop code. I have always liked VFP and have developed some applications that I personally use (a budget manager and a Bible study program) in VFP (the budget program goes back to FP days). I have other ideas for development that I also want to pursue as well and to make improvements to the two programs that I currently am using.


>My need for this is part of the Edit Property / Method Dialog Replacement (version 3 to be released soon).
>
>As such, unfortunately, it can't use any outside tools (in fact, it had used CTL32 balloontips, but they had to be removed due to potential conflicts).
>
>Thanks for the info, though. When I have time, I'll be looking forward to taking your VFP Form Editor replacement for a ride.
>
>Am most curious, though -- what prompted you to start such a project?
>
>>Cesar/Jim--
>>
>>I wrote the VFP Form Editor replacement and also have a Visual Class Editor replacement as well. I have not yet released the VCX editor as I am still testing it and some copy functions (copy of classes from another file or to same file) are not yet complete/tested. The basic functionality is working fine now with my use over the last few months. In both of these editors I have extended the memberdata to be essentially unlimited (I store the memberdata into the user memo field fully intact). You can then choose as to what fields are included in the 'normal' memberdata string that is stored that VFP uses. I have also found that VFP is not good at cleaning up the memberdata string -- if you delete a property the memberdata value is not removed (although this is fixed in the VFPx property editor replacement).
>>
>>If you would like to try the VCX editor -- let me know and I will forward to you (I would disable the functions that are still not complete/tested).
>>