Lang.F Thought

[dwkrueger]

I keep thinking about your issue with providing the language translation and putting all of the Static strings through the method Lan.F. I keep thinking what about overriding the object.ToString() method. But this would be nice becuase the ToString() method is so handy and intellisense brings it up often. But I think you would get into all sorts of problems ie referencing column names and the column name get interpeted. Then I thought what if we add a method to the object class or the string class that provides the translation lookup.

So now instead of having to type Lan.F (string) or Lan.g(string) you can just type "hello world".F or "hello World".g . Okay so it is only 5 keystrokes better but it just seems that there might be a better way.

I have never overridden such a low level object before it might be intersting. I'm not sure we can even do this without creating a new object that inherits from the other object -string (yuck).

Just a thought.

Dan

[jordansparks]

I'm pretty sure it's easier in .Net 3.5 because we can use an extension method to extend String with g. But we would have to make sure Mono supports such a new feature. And there is a disadvantage in that g is not as intuitive as Lan.g. Lan.g is a quickly recognizable English word part. I say we leave it alone.

[dwkrueger]

I also think you Lan.g is too embedded to really fiddle with now but it was just a rogue thought.