What's on your wish list for Visual FoxPro 10.0? I know there are some request and wish lists on other sites (universalthread is one I can think of), but we've gotten so many great features in versions 8 and 9, what else is left to add? Tell the world here!
I'll start with a real biggie that's probably on your minds too...
Port Visual FoxPro to 64-bits! With Windows XP 64-bit edition already released to manufacturing and a 64-bit version of Windows Server 2003 in the works, it's clear that true 64-bit native functionality will quickly become the standard. Running VFP in Compatibility mode is okay for backward compatibility for a few years, but for VFP to have a strong and viable future, it must keep pace with this new architecture. It was dealt a blow when Microsoft excluded it from Visual Studio .NET, but I feel the port will be a crucial milestone that must be met.
If you think porting 64-bit is not an issue, how many 16-bit programs do you have that aren't considered outdated? That's because we've had 32-bit operating systems for about 10 years now and anything less is virtually ignored and considered as "legacy" program languages. Yes, I know they usually still work but usually with each new version of Windows more quirks and incompatibilities arise. The biggest concern is they aren't considered up-to-date anymore. Looking 3 years into the future, how many program designs and proposals do you think would get approved and aplications sold if VFP were still a 32-bit program? So a 64-bit port is critical to our survival!
Yes, I know the Visual FoxPro team hasn't said yet what's in store for version 10.0, but I for one wouldn't mind at all if the only major change or addition was a 64-bit port. Rah, rah, sis, boom, bah... for 64-bit!
Awaiting anxiously, dbMark
I'll start with a real biggie that's probably on your minds too...
Port Visual FoxPro to 64-bits! With Windows XP 64-bit edition already released to manufacturing and a 64-bit version of Windows Server 2003 in the works, it's clear that true 64-bit native functionality will quickly become the standard. Running VFP in Compatibility mode is okay for backward compatibility for a few years, but for VFP to have a strong and viable future, it must keep pace with this new architecture. It was dealt a blow when Microsoft excluded it from Visual Studio .NET, but I feel the port will be a crucial milestone that must be met.
If you think porting 64-bit is not an issue, how many 16-bit programs do you have that aren't considered outdated? That's because we've had 32-bit operating systems for about 10 years now and anything less is virtually ignored and considered as "legacy" program languages. Yes, I know they usually still work but usually with each new version of Windows more quirks and incompatibilities arise. The biggest concern is they aren't considered up-to-date anymore. Looking 3 years into the future, how many program designs and proposals do you think would get approved and aplications sold if VFP were still a 32-bit program? So a 64-bit port is critical to our survival!
Yes, I know the Visual FoxPro team hasn't said yet what's in store for version 10.0, but I for one wouldn't mind at all if the only major change or addition was a 64-bit port. Rah, rah, sis, boom, bah... for 64-bit!
Awaiting anxiously, dbMark