Wednesday, February 22, 2006

What does the future hold for VFP?

This is perhaps one of the most asked questions lately. Most of the time when I'm asked this question it is in regards to SednaX, but today I'd like to talk about the contract work I recently started on Sedna. The Microsoft Visual FoxPro Team is allowing me to talk about things that would ordinarily be kept behind closed doors. In fact, when I asked them what I was allowed to talk about, their response was pretty surprising. Basically they feel that the more that we discuss, preview, and show before the eventual release of Sedna, the better (they obviously weren't just blowing smoke when they began touting the concept of transparency - I must admit that before this I had my doubts).

Windows Vista

The bulk of my work is being done on what some would call a Vista toolkit, but really it's just the Visual FoxPro Team and I working on some really cool and useful stuff for Visual FoxPro using new features and APIs that are being unveiled by Microsoft as they move towards Windows Vista. As Microsoft is back porting a lot of this new stuff, some of these proposed Sedna components would work on Windows XP and maybe even Windows 2000 as well. In the coming months you can expect to see lots of things both here on my blog and also in the CTPs that will be released for Sedna. Most are things that have never been done, or were never possible before, in Visual FoxPro. Not excited now? You will be... OH, you will be! :)

Let's take a look at a few things that I've worked on that are being considered for possible inclusion in Sedna...

Windows Presentation Foundation (WPF) - XAML (codename was Avalon)

Below is a screen shot of XAML controls running inside a Visual FoxPro form. When the buttons are clicked they actually fire Visual FoxPro methods. While this example is just showing some simple drop-shadowed buttons, pretty much anything that WPF is capable of doing with XAML could be done. So if you wanted something more complex, like a 3D model that would spin around, you could have it. Think of a database application for products where the user could rotate an image of the product a full 360 degrees.

 

XML Paper Specification (XPS)

Sometimes referred to as the Office 12 document format, XPS is going to be huge in the coming years in my opinion. Given the open nature of the XPS format (basically a bunch of XML documents inside a zip file), there will be a lot of 3rd party products that will be coming out supporting XPS. So how about the ability to create XPS documents from Visual FoxPro reports? Here's a screen shot of one of the solution sample reports in XPS format. It is being shown in the XPS viewer that Microsoft has created for IE 7, but Microsoft will also be providing a standalone viewer as well. In XPS format, the report's text is fully searchable and the document can even be digitally signed. Also, the rendered quality of an XPS document is super crisp and clear.

 

Task Dialogs

Say goodbye to the simple and somewhat tired looking Windows message box and hello to Task Dialogs! Task dialogs are message boxes on steroids, and just one of the new common controls provided by Microsoft in Windows Vista. What the screen shot below doesn't show is some of the other features that come with task dialogs, such as enhanced button types, progressbars, additional icons, callback functions, additional control areas... the list goes on and on. In addition to being very useful, task dialogs can help give a Visual FoxPro application one of those little touches that makes it look and feel more professional.

 

Speech API (SAPI)

Sorry, no screen shot for this one, but SAPI has really been improved in Windows Vista. Imagine users using Visual FoxPro applications to do dictation (saved directly into a memo file as data), or run queries... "Bring up customer, last name Smith", "Show me the February sales report", "Upload progress report to headquarters". Sounds a bit futuristic perhaps, but given the new Speech engine in Windows Vista, all of this and more is possible. I haven't worked out what all the uses might be for this in Visual FoxPro applications, but talking into a microphone and seeing the sentences appear in an editbox on a Visual FoxPro form is still pretty neat. And, when thought of in conjunction with the growing popularity of internet telephony (VoIP), I have to think there is some use for speech recognition in the Visual FoxPro applications of the future.

More to come

That's all for this blog entry, but certainly not all that is being worked on. I'll be back with more later. I just thought that some of you would enjoy seeing these, and maybe it would generate some excitement and useful discussion here or out on the Visual FoxPro forums. As for SednaX... more is on the way there too. I promise.

Wednesday, February 22, 2006 9:04:24 AM (Central Standard Time, UTC-06:00)  #    Comments [10]
Wednesday, February 22, 2006 3:14:39 PM (Central Standard Time, UTC-06:00)
Great news Craig! As I am currently working on a WPF project, I am curious on how the xaml+Foxpro is done, so can't wait to the release of that Sedna CTP.
Thanks!
Wednesday, February 22, 2006 4:37:58 PM (Central Standard Time, UTC-06:00)
Craig... This is fantastic news!!!

I can't wait to use these future capabilities (XPS,WPF) and indeed, the new TASK Dialogs - through Visual FoxPro and the upcoming SednaX release.

It's an exciting time for Visual FoxPro developers!

Keep up the great work, both here at the SPS Blog and with the VFP Team!!

Thursday, February 23, 2006 12:20:09 AM (Central Standard Time, UTC-06:00)
This is all cool stuff...
What about all the stuff on the VFP wishlist? Is any of it even being considered?
Foxis Thebest
Thursday, February 23, 2006 10:41:53 AM (Central Standard Time, UTC-06:00)
When MS recently released the Sedna preview docs it was all a bit 'meh'. This, however, is the business! VFP has always been weak when it comes to GUI so the XAML capabilities are most welcome! Brilliant stuff, as usual Craig.
Steve Harris
Friday, February 24, 2006 9:33:45 AM (Central Standard Time, UTC-06:00)
Foxis,

A large number of the items that are on the wishlist would require the Microsoft Fox Team to modify the core of Visual FoxPro 9.0. They've already pretty much said that they really don't want to touch the core for Sedna. That having been said, there are some items on that list that can be implemented without having to touch the core. I'm not privy to everything everyone is working on in Sedna or all the discussions they are having. The work I am doing directly relates to new APIs and Windows Vista in general. Perhaps some of the wishlist items that don't require changes to Visual FoxPro itself could become projects in SednaX. I noticed that OOP menus is on the list, and Doug Hennig is already managing a project for that in SednaX. Probably not the answer you were looking for, but it's the best I can offer.

Steve,

Yeah, I felt the same way when I read through the docs, but it's early in the game yet and this whole thing with transparency and CTPs is gonna be really cool as we progress towards Sedna. I'll be back soon with more stuff I'm working on that is being considered for inclusion in Sedna. I'm gonna try to bring the BUSINESS as much as I can! Also, I know they have some other really talented programmers working on this... so more business and less 'meh' should be on the way.
Thursday, March 09, 2006 7:43:43 AM (Central Standard Time, UTC-06:00)
Thanks Craig !

The Spanish version of this article is available at (La versión en Español de este artículo está disponible en:)
http://www.portalfox.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=119


Regards / Saludos,

Ana
www.amby.net
www.PortalFox.com
Thursday, March 09, 2006 3:26:18 PM (Central Standard Time, UTC-06:00)
Thank you Ana. You always do a such a good job on the translations.
Sunday, May 28, 2006 5:09:09 PM (Central Daylight Time, UTC-05:00)
I've never had a problem with VFP's technology. (I was reading some of the things they're
doing for a project called LINQ for .NET 3.0 - their comment was "oh, this is really great...
it looks like what FoxPro had 15 years ago" !!!) The fact that it's taken them until v3.0
in order to provide what (to a VFP person) looks like pretty much standard functionality for
business applications tells me something about the .NET developer's mindset - they are not
business/data processing people.

It was great for FoxPro when Microsoft bought it back in the early 90's because it always
got most of the new technology plugged in one way or another.

The problem with VFP is in perception/marketing. Microsoft doesn't "sell" it anymore. Not
to new customers, as far as I can tell. They think that .NET is the end-all-be-all for
programming languages.

Whether it's appropriate, for many typical business uses, to have a language that seems to
require a doctoral dissertation in order to comprehend, isn't a their considerations. There
are some bad things about .NEyT - it's excellent/outstanding as far as having a compiler
understand the program - but it's far less clear what they're trying to do as far as making
it clear to the developers who have to program in it.

COBOL was a primitive sort of thing. VFP is far closer to .NET than COBOL. But you can
actually take a COBOL program and more or less follow the business logic. Not an
inconsequential consideration.

The Army, Marines and Rangers all share a lot of common requirements. You'd think that
they'd all be able to use the same equipment. But they don't. There are enough perceived
differences in how they operate that they require equipment specialized for the task.

Now, .NEyT might be a wonderful language for designing computer games, writing compilers,
and all sorts of other things. But when it comes to business/data processing it's simply
too complicated.

A lot of people understand that there are certain types of job where VFP offers advantages
over anything else. Technical advantages. BUT NONE OF VFP's CAPABILITIES MEAN A THING
TO ANYONE AS LONG AS MICROSOFT KEEPS ON TREATING VFP LIKE THE THREE-HEADED UNCLE THAT THEY
KEEP LOCKED IN THE ATTIC. We're all on the path to early and unnecessary extinction unless
Microsoft has a plan as to what sort of jobs they'll recommend VFP for instead of the glory
boys in .NET. VFP needs to have at least a market niche - at present I don't see it.

Please excuse my rant. Somebody explain to me why I'm wrong.

thanks.
David W. Dee
Tuesday, May 30, 2006 2:06:27 PM (Central Daylight Time, UTC-05:00)
Case in point:

Even as simple a concept as what is "fast" or "efficient" for a business application is
different than what the .NET guys seem to think. Given the power of any typical workstation
today, I expect that I can run four copies of Word alongside whatever VFP business application
I might imagine, and still have CPU to burn to watch a movie or DVD in another window.

All I care about re: FAST is how quickly I can pull data from whatever database. It's
database I/O, tied at some level to the physical movement of disk heads in the disk drive,
that's the limiting factor. And scalability. Can I run 3 or 10 or 1000 or 10,000 sessions
accessing that data before I run into a problem.

If you're writing a graphics-intensive computer game, you have an entirely different
conception.

That's fine - no problem. Unless they try to foist their concept of "fast" on me and
the work I'm trying to do.
David W. Dee
Sunday, July 01, 2007 2:07:08 AM (Central Daylight Time, UTC-05:00)
i am a die hard fan of VFP. I have used VB and VFP both. When it was time for me to decide a primary programming language, i chose VFP. I have written many projects in VFP using native VFP database. My customers dont care what database i use or what front end i use, what they really care is [ RELIABILITY & PERFORMANCE ].

I was recently reading about VFP on VFP's homepage and it was depressing for me to know that MS is going to support VFP till 2015. They want all the VFP guys to hang on to VB.NET or C#.NET. There are many links and tutorials offered for VFP developers to switch to .NET

I think MS is trying to run away from a very fantastic programming language. It is shocking to know that MS commitment to ACCESS is greater than VFP. It is depressing for the entire VFP community but i am happy to tell u that some of the great applications in the market are written in VFP. Many govt offices in AUSTRALIA, Thailand, India use VFP applications.


Sanjay
Name
E-mail
(will show your gravatar icon)
Home page

Comment (Some html is allowed: a@href@title, b, blockquote@cite, em, i, strike, strong, sub, super, u)  

Enter the code shown (prevents robots):


 

Archive

<August 2008>
SunMonTueWedThuFriSat
272829303112
3456789
10111213141516
17181920212223
24252627282930
31123456