No more blogging this morning – my son Patrick woke up. The fact that I got him to take a nap at all is a miracle since I’m home alone with him. My wife Julie is starting a new job in the fall so she’s off learning the ropes. The job rocks in that she can bring Patrick every day, but she figured the training would go faster without him. I didn’t get to see him for 9 days while I was in New Orleans, so I’m happy to have the time with him. He was pretty upset over breakfast (I guess I didn’t make his oatmeal right), but otherwise he’s all giggles and smiles.

I just added 3 members to the DevHawk Wiki Workspace. However, one of them commented that they thought joining was the only way to get the source code. I just logged in w/ an alternate passport to test this: couldn’t check out or check in as a non-member, but I was able to get the latest version using the Windows Forms Control GDN source code interface. You do need to be a workspace member if you want to use the VS.NET integration.

I chatted w/ Scoble last night around 10:30pm. He wanted me to know he had blogged DevHawk Wiki as well as get my initial take on his secrets post. In response, I told him a secret. He’s got access to many more secrets than I do, so I figure he’s good at keeping them.

On secrets – I know there are a few times I have gone to write something on this blog just to delete it in the interest of keeping a secret. And not just MSFT secrets. I wrote a whole entry on a potential project that I don’t really have time to write. But in the end, I decided to keep it a secret in case I was ever able to build it. Not that it would make a huge amount of money – in MSFT terms it would be a component of a larger product. It’s just something I thought would be cool. (And this isn’t even the secret I told Scoble!). As Scoble points out, as an evangelist part of our job is to keep secrets. And to dole them out to what he calls the “influentials”. He’s talking about journalists, but for me, influentials are decision makers at my customers. Love or hate MSFT, everyone wants to know about what’s coming down the pipe. While I have lots of interesting things to say to customers, none more so than what follows: “You guys are under NDA, right?”

And here’s something that isn’t a secret: Scoble must get by on about 4 hours of sleep every night. He blogged 30 more times last night! That’s a total of 33 times in the 4 hours between 10pm and 2am. Wow.

Great to hear someone’s already using DevHawk Wiki. Robert Hurlbut (who’s working with Sam Gentile) set it up for his team’s internal use. Great to hear it’s going well Robert!

I figure there are two primary areas where I am interested in outside collaborative assistance on DevHawk Wiki. First, the WikiRenderer. I imagine as people start using DevHawk Wiki, they are going to want more formatting features. Second, SampleWiki is just that – a sample. A “real” wiki would need to add support for versioning at a minimum. User Authentication, search, multiple back ends (files, DB, etc), and reverse links are some of the other features I’d like to see.

I’m not particularly interested in enhancing SampleWiki or building a “RealWiki”. I built DevHawk Wiki primarily to have the WikiRenderer for another project I’m working on (more on that later). So I really mean it when I ask for collaborators.

I got my latest project posted – DevHawk Wiki. I was hoping to have this up yesterday, but GDN wouldn’t cooperate. It’s pretty minimal right now – it’s a v0.1 release. Collaborators welcome.

The cool part about DevHawk Wiki is that the wiki rendering code is separated out into a separate assembly. This means you could embed it in other apps (I’m thinking about a wiki-style comment system for this blog). One of the things I had to do to make this work is keep things like the wiki file repository independent of the wiki rendering itself. I used delegates to do this, then I read Don’s recent post on delegates and loose coupling. Here’s an example of what Don was talking about, in the wild.