I was accepted to speak at the next Code Camp, the weekend of Oct 28th, in Seattle! Hooray!! I thought for a little bit on (A) what would be a fun topic and (2) what do I have to say about said fun topic. I finally settled on talking about something I do on a daily basis: balancing the needs of the web designer, leveraging sufficient power of a great platform (read that as using the base class libraries and everything else given to me), along with the needs of the client and the overall budget.

Our designers at Pop Art are top shelf. They've come up with some fantastic ideas for sites. They're on the leading edge of what's possible with today's browsers and giving consideration to the downlevel browser folk.

Given that, they have some high demands on the HTML emitted by anything on the server. It absolutely, positively must be W3C compliant. It doesn't matter if its HTML 4.01 Transitional, or HTML 1.0 Strict; so long as it conforms to the given specification. Gone are the days of using menu server controls that emitted glorious reams of <table>, <tr> and <td> tags. Enough for you to knit a small blanket. Amen for the CSS Control Adapters.

The designers have a lot to say on usability too. There are just some things that developers will step right over like a country boy; where as the country boy's college roommate visiting for the weekend will stop, stare, point, hold their nose and give it a wide birth.

Enter DotNetNuke. Out-of-the-box, DNN is a developers playground. They know there's so much capability under the hood that they're (and I'm generalizing here) too busy envisioning what they're going to build next instead of rethinking the user interface that a client would need to maintain a site. That seems like small potatoes next to the glorious reams of code we can write.

So, I've settled on presenting the issues, challenges, arguments, counter-points and three-point-takedowns that we've had to address over the past 18 months with DNN. That would be a little too gloomy, so the remaining 67% of the discussion will contain some solutions that bridge the gap and keep the web site looking beautiful long after it launches. My presentation is in no way the rule; simply my experiences in dealing with this issue since I came to Pop Art in 2002. As with most things, I'm sure they are lots of ways to handle them, and I'm as open minded as the next guy; providing the next guy is sans jerk.

A basic introduction of DotNetNuke would be better served by a different session, but people who've never downloaded the bits from www.dotnetnuke.com will still get a reasonable insight into the problem sets and ways to deal with them.

My basic fear is probably the same as any other presenter who ever presented in all of presentation-land: getting slotted in the same time slot as ScottGu or anyone else in the rock star line up. What a problem to have!!   :)

I recently upgraded my laptop to 2GB of memory. I've been really pleased with my new ability to leave Internet Explorer, Outlook, SharpReader and SQL Server open when I want to use Visual Studio.Net and write some code.

As a negative side affect, I noticed some problems when I put my laptop into stand by or hibernation mode.

Stand by mode is where the laptop is still technically "on" and its drawing a tiny little charge out of the battery. All of my programs are still in memory but the machine is in a reduced state which preserves the battery until I'm ready to turn it on again. This mode the fastest way to pack up when I need to run for the bus as well as power back up again when I reach my destination.

Hiberation mode is similar to stand by except the machine is actually turned off. The laptop persists everything in memory to disk so I can even swap batteries if I like; a great trick to making long plane trips go by quickly. When I power up again, the laptop restores the contents of the memory and the CPU comes back to life.

It takes a little longer to go into and come out of hibernation since there's more stuff to do than when using stand by mode. Hence, my preference was to use stand by unless I knew I would be swapping batteries. The other day on a podcast I heard either Carl Franklin or Scott Hanselman mention that stand by mode can behave poorly because applications have the option of supporting it. Hibernation doesn't suffer from that since the contents of memory are dumped to the disk. Everything supports hibernation, but some apps may choose not to support stand by and therefore, when you start up again, an app may run aground.

I might have seen that on my laptop, but it hasn't been painful enough for me to care too much; until the 2GB memory upgrade.

In the best scenario, I would start the stand by or hibernate process and it would immediately come back and tell me this message:

Insufficient System Resources Exist to Complete the API

At first, I would smile and say to myself, "That's cause I got two gigs, baby!!" That wore off though. My harddrive is a paultry 40GB and I usually have somewhere between 8 and 0.5 GB free on any given day. So a few days ago, I deleted all of my Office and Battlestar Galactica episodes that I downloaded from iTunes and made sure I had enough room for the memory to dump to disk.

In the worst scenario, it would "take" for at least 2 minutes, enough for me to believe it worked, only to start up again inside my laptop bag. I would get to my destination and grab my laptop only to find it a little too warm. I'd frown. Sometimes, in the past, I would forget that it was on and chuck it in my bag only to find a hot laptop waiting for me later. The same frown occurs.

So this morning, I thought, what if there were some glorious place that existed where people would store and share their knowledge? I fired up my browser and did a Google query for "dell latitude cannot hibernate with 2GB ram". The first hit was this one:

http://translocator.ws/2005/11/06/hibernation-insufficient-system-resources

This page talks about my exact problem and an patch that is supposed to fix the problem. Only in his case, he has four computers that still exhibit the behavior after the patch was applied. There was a note on there that the latest patch of August 2006 was released. I suspected his problem was before this latest patch came out.

I downloaded the patch (WindowsXP-KB909095-x86-ENU.exe), installed it and lo-and-behold it worked! Well, I hibernated for at least two minutes. I'm excited to see if I get my stand by working again. I'll add a comment in a few days with the results.

This is the knowledge base article link and title for this issue:

http://support.microsoft.com/kb/909095

The computer occasionally does not hibernate and you receive an "Insufficient System Resources Exist to Complete the API" error message in Windows XP with Service Pack 2

 One of our Pop-Art-Gives-Back-To-The-Community clients wants to implement some simple online donation services on their website. So, I was flipping through a PDF file from PayPal using my Foxit Reader and I noticed this little phrase at the top of a page:

They're giving me complementary technical documenation! No orange juice or bagel, but the doc is categorized and complete.

I saw another funny part on the PayPal site. The link to the PDF file says it requires (my emphasis) Adobe Acrobat to read it. Ha! I must be flaunting the rules with my Foxit reader; breaking the law! breaking the law!

By the way, I've had great experiences with Foxit up until yesterday. One of our black turtleneck shirt wearing designers created a PDF version of a client proposal. When I opened it in Foxit, some large background images flashed for a second, then the text content appeared without much styling. Each page behaved this way. When I opened it in Adobe Acrobat, the full beautiful proposal displayed great with background and content. Huh. I'm not sure if the designer was leveraging some custom Adobe feature or if Foxit was the culprit; it was the first and only time I didn't get parity though.

Jason Mauer's blog let me know that Seattle Code Camp is coming up at the end of the month! Ack!

I'm thinking about heading up with my buddy Kelly. I told myself at the Portland Code camp, I said "Self," that's what I call myself, "you should present at the next code camp." Well, this is the next one, but its right around the corner!

I could do the DotNetNuke presentation, but seeing as how they just incorporated combined with their proximity to Seattle, there's a good probability that a DNN big shot will be there doing a far better show than I could. I was very impressed at the last Portland Code Camp at the quality of the "simple" talks. Things that you should already know, but are fun and refreshing to go over again. For example, the Subversion discussion was really well attended and you always end up learning some new trick or insight. I love that.

I'll put my thinking hat on and see what I come up with.

No matter how complex the Internet becomes, it refreshing to see that right and wrong are still easy to decipher. Here's the lesson that Six Apart has to pay for.

I just upgraded to the latest version of dasBlog. The Wife started grading AP Statistics papers with her sister (in town from Odessa Street of Paris, France) and I sat down on the couch to see how the new version works out. Ten minutes later, I've made the last file edit and the final FTP bits travel across the wire. Pretty simple stuff to upgrade!

I picked a new theme and found a photo to crop and added the oil painting effect. I thought I'd pick a familar sight; a photo of me surfing the web on my Treo. Just by messing around in these few brief minutes, I can see the blog engine has a few quirks that need some work. I'm going to try really hard to be a contributer in the next several weeks. I've been looking and the code though; its a little intimidating. Smells like an opportunity to learn!

The other day I fired up TortoiseSVN and it politely informed me that I might enjoy the latest release.

Hurrah!