September 2006 - Posts
One of the dangers of software development is that people tend to
believe that because something is easy to say means that it is easy to
do. For example, all Windows does is provide a user interface to load
programs and handle devices. This sounds rather easy. Unfortuantely,
it is over simplistic. Let's look at some of the issues that must be
- Handle the differences in video. There are many video cards on the market. How do you handle the differences between them?
- What should a user interface look like?
- What kinds of devices should be supported? Hard drives, USB, Firewire, Printers, etc.
- Who is responsible for handling these devices?
- How do you handle networks?
- On and on.....................
Just because something is easy to say, doesn't mean that it is easy to do.
Original post: http://morewally.com/cs/blogs/wallym/archive/2006/09/26/373.aspx
On Saturday, October 28th, the third Alabama Code Camp will occur. My buddy Bruce Thomas is putting on the codecamp. Check out the web site at www.alabamacodecamp.com for more information. Why should you go?
- The list of speakers at the group is a who's who from the Southeast.
- If Joe Healy is involved, you know that he will treat the attendees right.
On a personal note, I went and did a talk in Montgomery back at the beginning of August. Their meeting was at lunchtime. 50 people showed up. The room was full and people standing/sitting in the aisles. Bottom line, beat the rush and sign up now.
It surely would be nice if there was some type of event or notification mechanism that an AJAX library could raise / fire / set that would cause a screen reader to notify a user that an update has occurred to part of the screen. Perhaps this could be accomplished through some type of DOM "event" or something similar. Ideally, the user would like to know specifically what was updated. I hope that everyone could get together on this and solve the problem for the screen reader / Section 508 users.
Original Post: http://morewally.com/cs/blogs/wallym/archive/2006/09/26/373.aspx
Are you frustrated by the development scenario of Vista? Yeah, you can run .NET 1.1 apps, but Visual Studio 2003 won't be fully supported (Debugging will likely not work). Do you want to develop all from one system and under Vista? I do. I just found out that VirtualPC 2007 Beta Nominations will open on http://connect.microsoft.com
on October 11, 2006. Make sure you mark a calendar event for that date. Hopefully, this will solve some of the development pain that we all feel.
Original post: http://morewally.com/cs/blogs/wallym/archive/2006/09/24/371.aspx
Another part of my test is in the Page_PreInit() method, I put in a call along the lines of
protected void Page_PreInit(object sender, EventArgs e)
if ( true == IsValidForUpdatePanel() )
ScriptManager1.EnablePartialRendering = true;
ScriptManager1.EnablePartialRendering = false;
public static bool IsValidForUpdatePanel()
bool IsValid = false;
IsValid = IsIE6OrLater() || IsFF15OrLater() || IsSafari();
IsValid = false;
private static bool IsIE6OrLater()
return ((HttpContext.Current.Request.Browser.IsBrowser("IE")) &&
(HttpContext.Current.Request.Browser.MajorVersion >= 6 ));
private static bool IsFF15OrLater()
return ((HttpContext.Current.Request.Browser.IsBrowser("Firefox")) &&
((HttpContext.Current.Request.Browser.MajorVersion == 1) &&
(HttpContext.Current.Request.Browser.MinorVersion == .5) ||
(HttpContext.Current.Request.Browser.MajorVersion >= 2)));
private static bool IsSafari() // <-- The Safari is currently not supported in the latest CTP.
Ok, this is cool. Battlestar Galactica has released some webisodes that span the timeframe between Seasons 2 and 3.
I have also recently gone out and bought Season 2.5 on DVD. I watched it over the weekend. Good stuff.
If you want to add a control to fire the UpdatePanel, you have to add the trigger. You add this through the ScriptManager control. The method is .RegisterAsyncPostBackControl(ControlName);
I put this call in the Page_PreInit() method. I put it there because of some other Atlas stuff was doing that needed an early place in the page lifecycle. .RegisterAsyncPostBackControl() will also work in the Page_Load() event.
Original post: http://morewally.com/cs/blogs/wallym/archive/2006/09/20/359.aspx
I've been running with Windows Vista RC1 for the past 10+ days or so. Everything has been fine. This is the first build of Vista that I have found that runs well. All previous builds were pretty bad. I have installed Office 2k7 Beta2 Technical Refresh. I hooked up Outlook to go to my Exchange Server through IMAP because thats all that I can get to work given ports that are blocked.. Now, the damned thing runs horribly. I'll go ahead and say that the package is just not ready for shipment in November. I think the package will have a number of problems. I just don't have a comfort level with Vista and Office 2k7 at this point. Here are the problems that I have run into at this time:
- Outlook 2007 does not seem to perform very well. Often times, it give me inaccuate information regarding the status of emails. It says things are in the sent folder, when they aren't according to my exchange server. While not specific to Outlook 2007, it saves sent emails in the local sent email folder, not the one on the server, like every other IMAP client I have ever dealt with.
- Windows Mail is horrible. It often locks up on me. I have mail in the outbox that never gets sent. It marks emails that I have kept around for years as spam. I've just given up on this app.
- Trying to play some wmv files, I have run into problems with the audio and video getting very out of sync.
- Outlook 2007 is continually complaining that the data file was closed improperly and Outlook must repair it. Well, I didn't kill the Outlook process, though it SHOULD be shot and put out of its misery, so what is the deal with this app. I merely have clicked on the close X button. No error messages, no "Do you want to kill this prcoess" type of messages, no nothing, just this error message on startup
I'm running on a system with an AMD64 3000+ with 1 gigabyte of RAM. I don't think the problem is that my machine is underpowered. I'm using the 32 bit version of Vista as I gave up on the x64 version a while back.
I feel that Vista and Office 2007 are being run out the door to meet some self imposed deadline. I think it needs some more time to resolve issues. I honestly don't think I'll be jumping into Vista and Office 2007 until the first service packs.
Originally posted from: http://morewally.com/cs/blogs/wallym/archive/2006/09/16/354.aspx
I downloaded build 5600 of Windows Longhorn/Vista Server last night. I had the x64 and 32 builds by this morning.
More Posts Next page »