PandaWood's dashboard

With ben's consent, I've made a new project called, basically, BigVisibleCruise2 - it's at http://www.codeplex.com/BigVisibleCruise.

It has many of the features that have been submitted/rejected as patches here and quite a bit more. I've been actively developing it and will continue until all the features I want are complete ;-) I created this project simply because I have more changes to make than Ben can take, and I think they are useful enough that others will want to download it.

As an example of what I'm doing: I added functionality to get BVC to automatically monitor changes to the config file, so we can modify settings, such as "ProjectName RegEx, *while it's running* - and have the UI updated immediately. As it is now, BVC needs to be physically shut down and restarted to achieve this.

In BVC2, if you set the URL to start with "debug", BVC will use an XML file called DummyProjectStatus.xml in the bin folder, instead of hitting a real web service - important for playing around with skin changes and making screenshots etc.

I've also been actively cleaning code as I go, refactoring for Single Responsibility Principle - my best friend ;-) For example, I've MVP'd (ModelViewPresenter) the main window to move all the business logic out of the code-behind, and into a Presenter.

I just had a go at this, and got a GIT repository working and uploaded. However, using Git, on Windows, is not a friendly experience - at all. Until we get some decent tools (like Tortoise) I think I'll give it a miss. I couldn't get a 'push' to work anyway.

If you don't mind, I would like to take the version of BVC I have now, and make a GitHub project out of it.

The benefit of GitHub, and the disadvantage of the current system, is that I have many, many, changes I am making, and it's quite a burden to try and keep down with the base and commit patches. It's much easier, at this stage, to ignore the project and dance off with my own fork/version.

At least, with Git, I can do this, and make my "fork" easily available and mergeable (see http://whygitisbetterthanx.com/)

Here's a screenshot of the final patch I've submitted for adding gradients to the background.

I upgraded ccnet to 1.4.2 but I never see the "Message" attribute being set in the XML - so I never see build breakers.
I admit, I haven't read the doco yet - is there something you have to configure to get this to work?

I've just added gradients to the project box/rectangle - is this obviously better or should it be configurable?

We have a laptop (almost) dedicated to running BVC - the laptop sits on top of a cupboard in the dev room. The dev managers love it - more than us I think...Which is probably why we have several requests to show a photo of the person who broke the build flashing up beside the project name. A bit 'blamey' but probably just good fun.