Visual FreePro Update

[foxmuldr3]

I wanted to let everyone know I had a personal life tragedy occur in late 2024. Since then, I have not been able to work on Dori (the current version code name of Visual FreePro). I'm not sure when I'm going to be able to resume because the change to my life is rather substantial (since late October).

When I left off, Dori was around 85K lines of custom developed code, another 100K lines in 3rd party libraries (freetype, math, crypto, etc). I had a solid framework for forms, data, reports, and networking. About half of the functions were coded. About 40 common commands. Everything was in progress, moving along well, and there were no barriers to coding except for the time needed to complete it.

This is the second time I've been stopped by something huge/significant when I pushed forward very hard to get this project completed.

I've tried so hard to bring this project to light. I apologize to everyone. :-(

--
Rick C. Hodgin

 

[Pieter Koemans]

I’m so sorry to hear about what you’re going through. I hope things get better for you soon.

 

[Joe Crescenzi]

Hang in there are take care of yourself and your family. There is nothing more important than that.

 

[Don Child]

I wanted to let everyone know I had a personal life tragedy occur in late 2024. Since then, I have not been able to work on Dori (the current version code name of Visual FreePro). I'm not sure when I'm going to be able to resume because the change to my life is rather substantial (since late October).

When I left off, Dori was around 85K lines of custom developed code, another 100K lines in 3rd party libraries (freetype, math, crypto, etc). I had a solid framework for forms, data, reports, and networking. About half of the functions were coded. About 40 common commands. Everything was in progress, moving along well, and there were no barriers to coding except for the time needed to complete it.

This is the second time I've been stopped by something huge/significant when I pushed forward very hard to get this project completed.

I've tried so hard to bring this project to light. I apologize to everyone. :-(

--
Rick C. Hodgin

Take care, your time chief.

 

[trial03]

I feel sorry and thanks for the contribution. Hope everything getting better for you soon.


Regrds,

 

[Scott24x7]

Rick,
Is there anything I can do to help? Either with your setback, or the project?
I've had major events in my life over the last several years as well, and I know how it can knock you on your backside.
Anything, no matter how big or small, please don't hesitate to ask.

 

[Chris Miller]

While many of us surely would eagerly get on something new, there's no need to apologize for not delivering. You already made clear previously you're not sure you'll release it publicly once it's completed", but as a library for integrating xbase like features into C/C++ programming. (https://www.tek-tips.com/threads/visual-freepro-update.1831455/)

I agree with the others it's much more important you solve your problems than to have progress in VisualFreePro/Dori. I think there will still be an audience for this anytime in the future, and the active users in this forum are only the tip of an iceberg of FoxPro programmers still using it and ready to get on something that allows modernizations.

As a developer of larger projects I also know how it hurts to put something down before it's ready for a release. I fortunately only had stale projects that never saw the light of the world which I put down in an early stage.

All the best for your future.

 

[foxmuldr3]

Rick,
Is there anything I can do to help? Either with your setback, or the project?
I've had major events in my life over the last several years as well, and I know how it can knock you on your backside.
Anything, no matter how big or small, please don't hesitate to ask.

Thank you, Scott! I assume since you're in this forum you're well versed in FoxPro. Do you know C/C++ and the basics of the Win32 API?

 

[GTGeek88]

I wanted to let everyone know I had a personal life tragedy occur in late 2024. Since then, I have not been able to work on Dori (the current version code name of Visual FreePro). I'm not sure when I'm going to be able to resume because the change to my life is rather substantial (since late October) . . .

Yes, take care of yourself. What do you envision this project being? Also, how would it compare to VFP Advanced?

 

[foxmuldr3]

GTGeek88 said:
"Yes, take care of yourself. What do you envision this project being? Also, how would it compare to VFP Advanced?"

Dori intends to be a drop-in replacement for Visual FoxPro. 99% compatibility. It has a new forms engine, new report engine, new network abilities, new graphics abilities, new edit-and-continue debugger, in addition to supporting everything that VFP9 has today the way it has it today. The goal is any code that runs in VFP today should run in Dori with zero change, except possibly renaming the _vfp object to _dori.

Plans include porting it to GCC so it can support other architectures. I also want to make a native Android app that runs VFP/Dori code on mobile using the same programming paradigm we have on the desktop.

I think Dori will be the official release name.

 

[foxmuldr3]

Here's in general where the program's at:
1. I'm working on the new forms engine. I'm going to have all of the VFP compatible MODIFY x developer screens pop up in that new forms engine internally. It will look very similar to our traditional VFP screens, but internally it will be using the new forms engine for all processing. All of the legacy SCX and VCX code will come up using a format that looks like the traditional VFP-like engine. There will also be a new ability and a MODIFX command (which will be a new extended modify command introducing the new abilities). The legacy ones will be there, along with new features MODIFX will add.
2. I'm working on getting the command environment setup so every component from any existing project can be loaded, edited, and saved back using the Dori framework.
3. And the final thing I'm working on is getting all of the functions and commands working so everything operates as it does in VFP. These will go in the order:
4. Functions, commands, trivial SQL commands, and tables, indexes all fairly equally.
5. Reporting features.
6. Networking features.
7. Non-trivial SQL commands.
8. Loose ends.

I would like to ask for anyone who has large SQL expressions, if you could include table structures, and SQL expressions, then I could make sure my SQL parser works with all of them. I think that's going to be the last thing I get working 100%. All xbase and traditional data processing commands will be done sooner, and will be able to be debugged sooner.

I would like to ask for prayer if you pray, and if you do have C/C++ coding abilities, I would welcome the assistance.

 

[Scott24x7]

It's been a while foxmuldr3 but yes, I've experience in C/C++ and C#.