and the following runtime dependencies:
I know 1 (one) : angular.js, and by name only, never used it.
So this means that I have a LOT of catching up to do,
I can't speak for the other devs, because at the time of writing, it seems I'm the only active one.
(besides of the other contributors that is)
This does not mean that I discard this topic, far from it !
I always wanted to get the dashboard to HTML5 one way, and this gives it the perfect opportunity.
Any pointers where I and other people wanting to help / discuss should look at first?
Just so I have a bit of hands on on the matter.
Further down the line I think it would be fun to have a go at a ground up rewrite of the webdashboard server using some of the super-new, super-shinyASP.NET vNext stuff that's just on the horizon. I suspect a lot of the existing webdashboard code is doing things that are already implemented in ASP.NET (a hangover from the original Java CruiseControl port perhaps?) and so we might be able to produce a much lighter, easier to maintain solution. That's a big job for much later though.
Let me know if people have thoughts on any of that.Cheers,Rich
On Friday, September 12, 2014 8:41:33 AM UTC+1, Williams wrote:
HiThat mockup looks really great, amazing work !What kind of info / data do you need to continue with the dashboard change?I'm no designer either :-) but I really like the new look.Concerning the config, that's hosted on a private account in GitHub because of settings of other projects.but if you want to set up a build server that runs the CCNet code, it's not hard :This one looks like this :
All you have to do is call the 'all' target of the included nant build file
<target name="all" depends="clean, init, build, runTests, runCodeMetrics, package" description="" />with kind regards
Hi Guys,While having a look at the mono build I had a go at setting up a couple of ccnet servers hosted in the so-called "cloud" running my fork: