by Michael S. Kaplan, published on 2005/04/22 11:30 -04:00, original URI: http://blogs.msdn.com/b/michkap/archive/2005/04/22/410797.aspx
Last night I got a piece of email from someone who had seen my talk for the .NET Developer's Association back in February and they had just downloaded Beta 2 of Whidbey.
He was very impressed with a lot of the features and even played with my Normalization as Obfuscation sample.
But custom cultures did not seem as exciting to him. How many developers are really going to use this feature? He could see the sysadmin script kiddie types wanting to tweak locales on Windows, but they would not really care about cultures in the .NET Framework. And they would not be writing extensive code like that anyway. All of the language experts for cultures that are not there at all would also prefer it happen in Windows, and none of them are developers. So who is the market for this feature, he wondered?
I had to tell him that I agree with a lot of what he was saying. I do not think that it is a mainstream feature for developers. It is pretty fringe.
But there is one really important customer of this feature -- Longhorn. As Cathy and I said months ago at IMUG and a year ago at GDDC (without really giving much in the way of specific since there were none then!), the custom cultures you create in Beta 2 and RTM of Whidbey will be custom locales in Longhorn.
This will not help the bar that exists for people who would want to use the feature but would not feel comfortable writing code that makes use of the CultureAndRegionInfoBuilder class. But obviously there a huge space here where developers anywhere can write tools that will allow the files to be created, KB articles can be written with ready made code to create them for the various "sysadmin tweaking" scenarios, and the chasms between developer and language expert, between developer and sysadmin are easily bridged.
Well, maybe not easily. There is a lot of information in a culture/locale. Trying to present it all in an intuitive and non-daunting way is a serious challenge for a developer. I have given it some though from time to time, though not too much since I am a really good UI developer. The only time I have done well is with extensive interviews with the customers who will be using the UI to collect the requirements in a highly itertative set of discussions, and I am not sure how a developer would be able to find a group of people like that who would be representative of the broad cross-section of people who would be interested in the end result of customized locales.
Does anyone out there see a design paradigm that would work well to capture hundreds of data items that people do not intuitively bunch together in most circumstances? I have to admit that an intuitive answer to the question eludes me; I think I would try to aim for somthing understandble rather than intuitive. And then provide a lot of documentation to allow people to grasp the "understandable" concepts....
How would you try to capture things?
# Jeff Parker on 22 Apr 2005 10:28 AM:
# Michael S. Kaplan on 22 Apr 2005 11:31 AM:
# Michael S. Kaplan on 22 Apr 2005 3:10 PM:
2006/05/18 Where are the other Tamils?
2006/01/04 Determining (and correcting) locale settings
go to newer or older post, or back to index or month or day