Wish List Item: Backend Styling

Not wishing to clutter the 'upcoming features' post, I'll start a new thread:

I'm finding more and more often that I'd like better styling control over the backend. Here is an easy idea that would be welcome from my POV:

- classes assigned to field groups and individual fields:
Example for a textfield with pre- and post-text elements. This styling would let us control some aspects of a single field or a whole field-group. This could easily be connected to style class for a 'requied' field also.

<tr class="field_group field_aside [required]"> <!-- name of field group -->
<td class="field_label">Aside</td><!-- allows selection of all titles -->
<td class="field_content">
<span class="prefix">Optional:</span><!-- the prefix field -->

<textarea class="field" aria-hidden="true" name="aside" id="field_aside" rows="5" cols="40" </textarea>

<span class="field_desc">Used to highlight or feature items from this article such as pull quotes, adding supporting documents, or making extra comments.</span>
</td>
</tr>

This would let us easily create a backend style sheet which would allow us to apply styles to:
- whole field groups/table row (borders, colours, font style, margins, etc.),
- a single field group based on the name (highlight the required field's table row),
- all labels, prefixes or descriptions (make all prefixes dark, all descrptions indented, italics and monospaced),
- a single field (.field_aside .field_desc {color: red;}
- a required field (if a required token is set in the field schema) .required {background: yellow, url('alert_icon.gif') no-repeat;}



If you like this idea, I could mock up a list view version as well. It would probably follow similar rules but may need row and column indexing.

My $0.02... again. ;-)

J.