On Sun, Sep 11, 2016 at 12:46 AM, Edward Leafe ed@leafe.com wrote:
Well, Paul McNett and I *tried* to do that when we created Dabo, which does pretty much everything that VFP does, but with an open license and a future path forward. It did require learning Python instead of Xbase, but other than that, it had data binding, support for multiple backends (even a DBF backend, if someone had maintained it). It's been production-ready for over a decade.
Dabo is NOT resurrecting Visual Foxpro. It's building something similar to replace it. Dabo is competing with Visual C#, Visual Basic.Net and alike. Then Dabo must prove itself to be a real VFP replacement in *ALL* aspects.
When I said "resurrecting Visual Foxpro", I was referring the one and only Visual Foxpro owned by Micro$oft. :)
Very few people were willing to make the effort to move to Dabo. Sure, you couldn't directly port a VFP app to Dabo, but new development work doesn't have that problem. It really seems that people are much more willing to invest in a product with no future from its owner than to invest in a product with a future. It's like people who lived on the coast who have been flooded as sea levels rose: instead of moving to higher ground, they keep propping themselves above the waterline and praying for a miracle.
If Dabo offered a tool to convert Visual Foxpro projects.... there was never a 100% conversion tool that really does it.
BTW, have your team ever considered to write a conversion tool that translates *ALL* VFP codes into Python, including its Report Writer?