Skip to main content

VFP Sedna Wishlist: A single way of doing dialogs

While Craig is espousing how awesome VFP will work with Sedna and Windows Vista - what IS missing and should likely be the #1 extension put into Sedna upon its release is a way to use the new Vistadialogs4COM under non-Vista platforms. (Updated: Doug brings up a good point in his comments that the purpose of this work was NOT to be a generic dialog handler, strictly for VFP - read the comments below)

As Craig noted, using the dialogs is very simple unless you are allergic to OOP - but it would have been really nice if the DLLs were immediately smart enough to say "hey, you're not running under Vista, so we're going to give you the older file dialogs instead."

I know that Vista is soon going to be everywhere - but NOT including some of this functionality now will limit the usefulness and implementation of this library for regular developers. In most  deployed applications, you are going to be balancing between Windows XP, Windows 2003, Windows Vista and even possibly Windows 98. Then again, in Canada, where they are floating the idea of taxing (additionally) new computers and hardware purchases for additional recycling revenue, I can see the argument for more companies keeping and simply upgrading their existing hardware. If you can do more work on the web today, what is the business argument for switching to Vista?

Maybe it's a case of saying "here's what you can do" and then get the entire community making it more useful. (just like Doug did with the updated New Property and Method dialog).

 If so, I welcome the approach but it kind of leaves me wanting a bit more.

Powered by ScribeFire.


Doug Hennig said…
Andrew, I'm not sure that's should be the focus of this control. It's job is to provide Vista dialogs to COM clients. IMO, it shouldn't be a generic dialog class. THAT would be easy enough to create by building a wrapper for the Vista classes and adding functionality that supports older operating systems.
Andrew MacNeill said…
I agree that it may not be the focus of the control - (it's all about scope!)

As you mention, a generic dialog class SHOULD be easy enough to create so that's why I mentioned maybe it should be one of the FIRST areas for improvement.

But there is one question that is suggested by your comment: its purpose is to provide Vista dialogs to COM clients - in other words, NOT just VFP but also perhaps, say, VB 6 or any client that can consume COM that isn't part of the .Net family.

Am I right in thinking that?
Anonymous said…
Doug is right on the money, and while I can't speak for Microsoft, I would say that Andrew's assumption regarding the desire to create COM visible classes (using VB.NET) that are found to be useful to anyone developing in a COM-aware language is also right on the money.

Given the limited resources provided for Sedna, proper scoping is very important. And, since the Sedna source code is slated to be released on CodePlex with a liberal EULA (most likely very similar to the xSource and FFC licenses), any of the Sedna projects can be easily enhanced or encapsulated, and hopefully the projects will also serve to provide concrete examples for enhancing VFP.

In addition to providing access to the new Vista dialogs, the Vistadialogs4COM project shows how to use .NET's inheritance, delegation, and COM-interop features to provide the developers working in unmanaged code access to the world of managed code. Throw in some other things, such as .NET runtime code generation and in-memory assembly compilation (i.e. CodeCOM, Reflection.Emit), FLLs (extending VFP's language base by accessing the VFP API using C/C++) and, IMHO, some fairly interesting possibilities begin to present themselves to VFP as well as other languages that are too valuable to ditch.

Popular posts from this blog

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub . A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article  : "...   people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack? Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub

Attending Southwest Fox 2019 could change your life - Find out how

Southwest Fox is coming up in October and as I do every year, I spoke with the organizers Rick , Doug and Tamar on the FoxShow. Deadlines for Southwest Fox: Super-saver price (before July 1): $695 Early-bird price (before August 1): $770 Regular price (August 1 and later): $820 This year, I took a different approach with separate shows for each organizer but the main message is still the same : July 1st is their Go/No-Go date. Conferences don't talk about this very often. I don't think developers really question if Apple will hold their WWDC in June or Microsoft will hold their Build conference - but that's because those conferences are vendor-led. Southwest Fox is a community-driven conference - it's not driven by a company with an agenda. Listen to the interviews and you can hear how important each of the organizers feel the live connection between speakers and among attendees.

eero icons - What the heck?

How to change icons used by eero.... Formerly titled: Eero router - Nicknames and icons UPDATE: Finally!!!! The most recent update to the eero now allows you to specify icons from their library. And it's a GOOD library - thank you. Finally! If you've extended your wireless network using eero , you have downloaded the app. I upgraded my network when I noticed a bunch of dead spots in what should have been a fairly reasonable coverage space (1700 sqft home). With two eero devices, our home is pretty well covered. Click on Connected devices and every device connected to your network is displayed. The eero app identifies the manufacturer and, with some devices, even the name of a given device. The eero app may also show an icon that represents its use. Some of the more obvious icons are those for phones, laptops and TVs. Unfortunately, the majority of devices get a fairly generic "wifi" icon. But you can change this. Give devices a nickname using ce