TechShorts

Blizzard Entertainment - World of Warcraft I have been waiting for over three years for WOW to come out. Is it worth the wait? Am I going to rush and play it? Should I? After all these years are online dungeons even relevant? UPDATE:   My wife bought me the game for Christmas, but she said I can't open it until Christmas!  But we are going to Flint, MI for Christmas so I won't be able to play it until New Years Eve, when we get back.  Oh the humanity of it all!

Scott Peterson is found guilty.  Finally, maybe this will become a non-issue now.  I'm sick of hearing about this case, Who Cares!  There are far worse attrocities going on in the world, who cares about this cheap ass punk? Arafat is dead.  Finally!  He did nothing but cause problems.  Maybe now the Palestinians can get some solid leadership. The election is a solid win. What ever are the reporters going to harp on now?  I'm sure they will find something, the bastards.

The December 2004 issue of MSDN contains an article on developing CF apps. Part of the article advocates the disposing of forms as soon as you are done using them in order to conserve memory. I disagree with this. I have found that caching forms improves the performance of a CF application. It takes a long time to load a form in CF so why should I make the user wait every time he has to reopen the same form? If the speed of creating forms was not an issue then I would be OK with disposing of them when done. There is a Form Stack code block floating around the web that I have been using successfully to cache forms. This works up to a point but it has limitations as well. I am working on a hashtable cache for forms and will extend it to include panels. I think that performance would be even more improved if instead of caching entire forms we cache the panels.