Team Server "Albus" build 1075 is available

Nice improvements!

The web site usability is much improved, mostly by putting valuable information into previously blank spaces. The site flow is pretty good as well. The front page is still too empty, but that's probably an artifact of me having only being one project installed, at present. Aesthetics are improving, but it's still rather spare and drab due to color selection and lack of chrome.

Deferred commit rules, but not quite as much as had thought it would. I figured that if I submitted a project for remote run, I could then commit the changed files as they were at the time of the remote run. Instead, deferred commit picks up any changes I've made to those files since the remote run was requested. Fixing this would require some local history hackery, but seems like it would be much safer and truer to the desired semantics. Also, since each file can be in only one change-set, it's trickier than it might be to manage later defered commits if you skip one. I'm not sure that deferred commits should be tied to change sets, for that reason.

--Dave Griffith

Dave, thanks for your attention and comments.

Regarding web UI part - I think, I should have explained the situation before ... but better late then never :)

To be honest, there's no such thing in the world as public EAP of a web application. Google is just showing off with their Gmail "beta"... I reckon if we were going to release a web service we would never do a public EAP of a web app which interface has a working prototype quality.

But TeamServer is not a web service or "pure" web-application. Its web UI is just a part of the whole system. Hence the need of early EAP.

Web UI is evolving, gaining new features along with structural improvements. The design (fancy graphics, colors, typography, etc.) will be completed after we are done with the "skeleton" - navigation, pages layouts, content etc. With CSS it's not that difficult.

I understand that web UI is considered final when it's unveiled. :)) Please, consider TeamServer to be an exception from this rule. The UI part is constantly changed - the next EAP will (hopefully!) bring the new Build Log page and new Project view (current home page), plus a bunch of smaller usability issues like pop-windows design and behaviour.

Again - thanks for the feedback and attention. Be sure, we care about everything you tell us.


--
sasha maximova
User Experience designer,

JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"

Sasha,

I absolutely understand, and am treating the Team Server functionality just like I do IDEA EAP functionality. As an EAP member, I have a responsibility to bring up anything I think still needs improvement, and an equal responsibility to understand that EAP functionality is in flux, and may be half-finished or even broken. I certainly understand that cosmetics come last (or second-to-last, before documentation). Sorry if this means I comment on thing your were going to fix anyway, but the alternative (keeping quiet and hoping) is worse for all concerned. And always remember, feature requests are the purest applause that people in our business get.

--Dave Griffith

"Dave Griffith" <dave.griffith@cnn.com> wrote in message
news:25414709.1146261431695.JavaMail.itn@is.intellij.net...

Nice improvements!

>

Deferred commit rules, but not quite as much as had thought it would. I
figured that if I submitted a project for remote run, I could then commit
the changed files as they were at the time of the remote run.
Instead, deferred commit picks up any changes I've made to those files
since the remote run was requested.

Did you request commit manually after notification about successful build?
Actually commit action after remote run should be disabled now, in the next
eap version commmitted files will not contain changes made after remote
commit invocation (but they will contain the changes it you'll try to commit
the files manually)

Got it. I was using the changelist labelled as "Deferred Commit: ]]>" in the Changes toolwindow. If that doesn't do a true deferred commit, but instead commits the files along with any changes made since the remote run, then the changelist stuff is just confusingly labelled.

--Dave Griffith