>bump

LOL...

Why the post? From my previous comments I stated that I wish for you success in this endeavor. I hope that you will succeed. But what is success? You have to define that... Is this a completed programming tool that you are using or is this a completed programming tool that the current VFP community is using? I would wish for the latter - a community platform. But for this to happen people have to be comfortable with the migration away from VFP. This means that your platform has to be completely compatible in the forms, classes, tables, and programs that are currently being used in VFP. Otherwise, your platform is just another platform that is an alternative to VFP and not a replacement for VFP. The would-be users/developers have to feel comfortable in their ability to move back to VFP.

The community would like a VFP 10.0 and beyond. Those left in VFP had a choice years ago when it was announced the end of VFP would be 9.0 to then move to another platform. Many did. Those that stayed believed that they could continue in VFP at least for their careers. For these VFP developers (which are whom you seem to be targeting) to move now to a new platform that would possibly provide a conversion path but then they are left in the new platform what is the overall advantage? They are being asked to move to a platform that they don't know when it will be sunsetted. It could be the day that they move -- you are hit by a bus... No more development of Visual FreePro. This is why I said that there has to be more developers in the core code of Visual FreePro. I think most will be 'skiddish' to move - unless they have a clear path back to the safe haven of VFP. Some might 'explore' it but again to risk moving they must have confidence of a long term platform (at least whatever long term means to them).

I started out developing GKK Editors mainly for my benefit back before the announcement of the end of VFP -- I initially wanted a VFP based editor that at least would show the code line numbering. I have continued to refine and add features to these editors based on my needs or interests. I was not as concerned with the adoption of others to use my editors. When I first introduced the editors, there were quite a few bugs that needed to be worked out (my goal was to expose the bugs by others using what I may not have used). I suppose these bugs discouraged others from using them -- they feared the loss of their form or visual class if it became corrupted. I certainly understand this. So I pulled the editors back for the past few years and continued to use on my own and try to squash the bugs. But others I suspect are still squeamish to use the editors for fear of losing their work. It is a risk many may not want to take. For me, it is a less risk -- I can hack my way to just about anything in the SCX or VCX to fix if I had to; others may not be as fortunate. I am not discouraged because my goal at the start was an improved editor that I would use. I have made the editors with code available to many that asked -- they can now make their own improvements if desired. I want to move the code onto CodePlex but I have to take the time to learn to use the repository for the code and then setup the page. Time is limited right now.

So what is your goal?