Disabling emoticons should be a one line change. When is this going to happen? This is a coding forum, not a chat room.
e.g.http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=567391&SiteID=1
Where the line goes must be the critical path... :-)
I wasn't aware that emoticons were going to be completely disabled, is that what you're suggesting?
I doubt that will happen. Keep in mind that the software that is used for the MSDN Forums is also used for Windows Live OneCare Forums, TechNet Forums, Japanese MSDN Forums, Microsoft Codename Max Forums, Windows Academic Forums, ASP.NET Forums and I assume many others (XBox Forums, ASP.NET Forums, and IIS.NET Forums seem to get their own "special" software). Wholesale disabling of emotions, or a seemingly simple "one line change" has far-reaching consequences.
Brian Kramer wrote:
I'm not exactly suggesting that, but having it at all is preferable to having it. If headcount is an issue, then find one person to comment out a line or two of code to force it off. People have been complaining about it months ago.
I agree it's not "rocket science", but with the regression impact of even a simple change would be quite enormous.
If a single component is to be used in multiple contexts, then maybe a context code can be sent to the component so that it can format as appropriate. Whatever the solution, it can't be rocket science.
I agree. It would be nice to see some sort of roadmap for what's going on in the MSDN Forums.
At least I'd like to know what level of commitment MSDN has on these kinds of issues (i.e. show some transparency.)
"I agree it's not "rocket science", but with the regression impact of even a simple change would be quite enormous."
I guess, but I'm not so sympathetic. Tweaking UI code isn't as risky as, say, fixing a compiler bug. If there is agility lacking in maintaining a website, then that's a problem in of itself. Plus, much of the complaints stem from regressions caused by using a new editor--there are bugs that could have been easily spotted during internal testing.
Brian
