This isn't a bad approach, but I really don't think folks should be installing yet another background process, lurking and stealing CPU cycles for the 99.99% of the time it is not needed.

The similarly-named (but original) "DashboardStarter" - find it here: http://www.versiontracker.com/dyn/moreinfo/macosx/27608 - seems to be a much better approach: It is a one-trick pony, which merely activates then dismisses Dashboard. You set it as a LoginItem, and it does exactly what is needed, when it is needed - and then quits itself.

This implementation, on the other hand, remains active, and simply waits for the Dock to be restarted to reinitialize Dashboard again. Since a vast majority of users will only start the Dock upon login, this is a huge waste of processing. In addition, if you do restart the Dock within an interactive user session (say, to test dock.plist changes, etc.), then you need to wait as it tries to kick off Dashboard again - which at this point is not necessary.

Avoid this implementation, and try DashboardStarter (note the LACK of a space in the name) instead.