Google Chrome Comic is really a comic strip about the new browser call Chrome.

For now http://www.google.com/chrome is the supposed home for this site. It gives a file not found. So, they still have more releasing to do!

Based on webkit as well as other open source projects. At the end of the comic Google seems to be taking a jab at Microsoft. They certainly could have created a closed and proprietary new browser. While never mentioning Microsoft by name, what other browser is proprietary? None that I can think off.

If they can make money off of open source projects, Microsoft should find out how. Also, they should port Developers Studio over to the Mac.

Chrome will be coming soon!

http://develop-one.net/blog/2008/08/27/HugADeveloper.aspx is a sad video, since it is so true.

http://www.codeproject.com/KB/macros/SimpleSwitchFramework.aspx is an example of making a custom switch for devenv. I really need to get to know msbuild.

http://flourish.org/cinclude2dot/ is a web site that hosts a perl script to create a dependency chart for C++ code.

You will need wget on your system! See http://www.asitis.org/installing-wget-for-mac-os-x for the Mac. If you have Windows, well, you will need to do something else.

If you want to get all the Perforce files in one step, try this:
#!/bin/bash
cd perforce
mkdir Win32
cd Win32
wget http://www.perforce.com/downloads/perforce/r08.1/bin.ntx86/p4vinst.exe
wget http://www.perforce.com/downloads/perforce/r08.1/bin.ntx86/perforce.exe
wget http://www.perforce.com/downloads/perforce/r08.1/bin.ntx86/p4webinst.exe
wget http://www.perforce.com/downloads/perforce/r08.1/bin.ntx86/p4dtg.exe
wget http://www.perforce.com/downloads/perforce/r08.1/bin.ntx86/p4winst.exe
wget http://www.perforce.com/downloads/perforce/r07.3/bin.ntx86/p4gt.exe
wget http://www.perforce.com/downloads/perforce/r07.3/bin.ntx86/p4ofc.exe
wget http://www.perforce.com/downloads/perforce/r07.3/bin.ntx86/p4rpt.exe
wget http://www.perforce.com/downloads/perforce/r08.1/bin.ntx86/p4ftpd.exe
cd ..
mkdir MacOSX-Intel

Having an agreement between developers and the build team will keep everyone's expectations in check.

Below should be the minimum of any document.

You need at least these items:
What output is expected?

What setup is needed?
Configuration:
Pre-requisites:

What input will be used?
VCS: Branch? Modules?

SET /A LINES=0 && FOR /F "usebackq" %L IN (`dir /s/ad/b`) DO @SET /A LINES=!LINES!+1

Will show you a poor excuse for the "wc -l" function.

Over my lunch I have installed macpython 2.5 and the GoogleApplicationLauncher. We will see what this thing does one day.

http://accessdataonline.com, phecht_drpl2
http://hechtmail.com, phecht_drpl3
http://phecht.com, phecht_drpl1

Introduction to OpenUP discusses the SDP "Open UP". Yet, it is not just another process doc. It is based on the Eclipse Platform's Eclipse Process Framework (EPF). This allows teams to define work flow using Eclipse.

I need to sharpen up on Team Foundation Server, but if I had the time and choice. I would evaluate EPF.