>>(2) Visual FoxPro did some things wronly, and pursued some paths that I liken as "the Microsoft
>>way of thinking," which I desire greatly to never be a part of in those things to which I can directly
>>control (such as Visual FreePro's design).
>
>For new projects it doesn't matter, but for moving old projects that's a big issue. I couldn't move even
>my some application from FPD to VFP9... :(


I had similar issues moving software from FPW 2.6 to VFP9. As a result, I wrote an app called FCON which reads in the FPW 2.6 source code outputs, and migrates them to a form compatible with VFP9, doing fixups here and there as they were encountered and I realized they were necessary.

Visual FreePro will include a lot of importer converters, which allow code that no longer works in Visual FreePro to still work identically after it is run through the converter. There will be very few things that need fixed up beyond those abilities, and those will mostly relate to removed functionality.


>>The source code is and will be freely available. You can find it here (James 4:15):
>>https://github.com/RickCHodgin/libsf and https://github.com/RickCHodgin/libsf-full
>>(includes my 32-bit operating system source code, and the full development history
>>dating back to July, 2012)
>I don't care about it's source code, I just meant source codes developed by VisualFreePro...

I will never add any specific protections to Visual FreePro's binary executable files. The only thing I offer is that source code does not need to be distributed. However, the entire framework, design, function names, variable names, sizes, types, classes, flowers, everything designed in Visual FreePro will be exposed and visible to anyone who receives the application.bxml file. If they have that BXML file, they can use any of the functionality within by a simple copy-and-paste function, moving it from that BXML into their own application with everything required to make it work in tow. The only limiting issue will be that the copy-and-paste developer will not have the source code. To that end I pray people will begin including their source code because there is far greater growth had by all when distributing source code with the product. It is far greater gain than hoarding the source code, as the effort of the many greatly exceeds the effort of the one, even when that one is prolific.