>I was wondering what you guys think? Is there any need or benefit in this?

Need - depends on what it is (has to be unique, not available in VFP, and a must-have); benefit - that depends on the acceptance...

I would expect that it would have to be free or provide some functionality that is not already available and that functionality would have to be a "got-to-have" for someone to pay for it. If there are other alternatives that are free, then it will be less likely to be accepted. I suspect that is why Anatoliy's controls have not been widely used - there are other alternatives or it just isn't a "got-to-have"...

On Anatoliy's point that it is absolutely bug-free before release (I would add even at beta) -- I would have to concur strongly. I developed over the past number of years replacement editors for the form, visual class, menu, tables, and procedures -- initially there were a number of bugs. Now I am actively using these editors in my work and finding no problems. The editors offer many features beyond the editors in VFP, but I believe that the perception of these editors were that they were buggy (which initially they were); and hence, because of this perception, I don't believe anyone is using them or would try them. I pulled them from the downloads area probably several years ago. Now I am using them in my work as I initially started these editors for my benefit and did not initially intend to sale them.

In general, I have found that people are scared of the potential of the editors possibly corrupting their development work -- but I have had VFP do this to me now more than my editors. In the case of VFP the corruption always causes a complete loss of the form/class; however, in all cases when I encountered a bug in my editors I have been able to recover all my method code with no loss in the past. I have to wonder how many people have also experienced bugs in VFP that caused a loss of the form/class which now will never be fixed? I believe that people will "trust" an established company name for delivering a product rather than an individual.

So now you have to decide if it is worth your time investment in a project for a dead software platform... Don't get me wrong -- I have and will always like VFP and will use it for my work when I am developing an application for a small use (meaning a single user or only a few users on a network).