High,

just downloaded the DNN7 CTP2 - so far, it works like a charm.

My question (and I hope that someone will answer this soon): Are the UX guidelines (published here) still valid for DNN7? Are some of the style classes proposed and recommended there only not implemented in DNN (eg dnnFormRequired - with the red border on the left) or will this change completely again?

Best wishes
Michael

BTW: I have the impression that some link buttons appear disabled in the new skin - they are not, but it is a bit confusing at the first look.

At the moment it appears that there will have to be a number of changes in the UX guidelines. The dnnFormRequired class is one of the ones which concerns me, also. It is still defined in default.css but in DNN 7 must be applied to the DnnLabel control (or label element) rather than on the ASP.Net Textbox or other desired input control. When applied to the label element it will show up as a soft red * to the right of the label.

I actually like the red left border on the required input controls in DNN 6 as it is very noticible and unlike the * does not interfere with the right-justified alignment of the label. It was a problem, however, to apply it to some of the Telerik controls.

I have tried installing a number of my custom modules that had been upgraded to the DNN 6 form patterns not too long ago into DNN 7 CTP2. Most edit forms and setting pages look terrible - will have to make minor changes to the markup for issues such as that with the dnnFormRequired class and more extensive ones to module.css - mostly to remove positioning work-arounds for DNN 6 css issues.

I also agree that many of the link buttons, textboxes, comboboxes, etc. look disabled in the new skin. I also find that my worsening eyesite does not do well with all the light grays nor with the black sliders. At first I didn't even see the horizontal slider beneath the add new module list. I might as well dig one of my old 1980's vintage monochrome monitors out of storage.