Based on a one person user study, Adrian Bateman thinks that “this [WinFS] thing might catch on.“
So do I, and we have talked to a few more users. In fact, right now I'm sitting in the WinFS team meeting listening to a presentation on the taxonomy we are using to categorize different kinds of ISV apps and their users. What scenarios are most important to users and what apps do they use to enable those scenarios?
Feedback
11/10/2003 2:40 AM
# re: "This WinFS thing might catch on"
I have sent most of my working life as a programmer in different ISV. To get me to support WinFS in an app you will need to.
a) Provide me with a API that does not stop me shipping my application to people with Windows 2000 or XP. (I do not mind if some methods are no-opps on old OS)
b) Provide me with a WinForms (and/or Win32) FileSave / FileOpen/ FileFind dlg box that makes use of WinFS were it is there, but still lets a user save metadata with my files on old OS. E..g store the meta data as XML in a file with a name that is related to my file.
In other words making use of the WinFS api must make my application better for ALL users, not just the very few that will have WinFS in the next 10 years.
(We still have customers that are running on NT 4, so I think it will take 10 years before 99.9% of likely customers have WinFS installed on 100% of there PCs)
email: ringi at Bigfoot dot com
11/10/2003 6:59 AM
# re: "This WinFS thing might catch on"
On Longhorn the system provided file open/save dialog will be updated to use WinFS (in fact, it is sort of a mini-shell, with all the capabilities to find items as provided in the shell).
We are also looking at what we can do in the API to support down level systems. Your feedback in this area is extremely valuable.
6/1/2004 12:44 PM
# re: "This WinFS thing might catch on"
hgh
Post a Comment