Changeset 121
- Timestamp:
- 07/16/05 17:19:10 (3 years ago)
- Files:
-
- django/trunk/docs/admin_css.txt (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/admin_css.txt
r103 r121 16 16 17 17 The ``.module`` class is a basic building block for grouping content in the 18 admin. It's generally applied to ``div``s or ``fieldset``s. It wraps the content18 admin. It's generally applied to a ``div`` or a ``fieldset``. It wraps the content 19 19 group in a box and applies certain styles to the elements within. An ``h2`` 20 20 within a ``div.module`` will align to the top of the ``div`` as a header for the … … 69 69 width, without using ``width="100%"`` which makes IE 5's box model cry.) 70 70 71 ``'Note:``'Within a ``.flex`` page, the ``.xfull`` class will ``usually`` set71 **Note:** Within a ``.flex`` page, the ``.xfull`` class will ``usually`` set 72 72 to 100%, but there are exceptions and still some untested cases. 73 73 … … 104 104 This is a custom class for blocks of inline help text explaining the 105 105 function of form elements. It makes text smaller and gray, and when applied 106 to ``p`` s withing ``.form-row`` elements (see Form Styles below), it will106 to ``p`` elements withing ``.form-row`` elements (see Form Styles below), it will 107 107 offset the text to align with the form field. Use this for help text, 108 instead of ``small quiet``. It works on ``span``s, but try to put the class109 on the``p`` whenever you can.108 instead of ``small quiet``. It works on other elements, but try to put the class 109 on a ``p`` whenever you can. 110 110 .align-left 111 It aligns the text left. Only works on block elements , I think.111 It aligns the text left. Only works on block elements containing inline elements. 112 112 .align-right 113 113 Are you paying attention? 114 114 .nowrap 115 Keeps text from wrapping. Comes in handy for table headers you want to stay115 Keeps text and inline objects from wrapping. Comes in handy for table headers you want to stay 116 116 on one line. 117 117 … … 138 138 Example from a changelist page:: 139 139 140 <ul class="object-tools"><li><a href="/stories/add/" class="addlink">Add story</a></li></ul> 140 <ul class="object-tools"> 141 <li><a href="/stories/add/" class="addlink">Add story</a></li> 142 </ul> 141 143 142 144 and from a form page:: … … 153 155 --------- 154 156 155 Admin forms are broken up into groups by ``fieldset`` s. Each form fieldset156 should have a class ``.module``. Each fieldset should have a header ``h2`` 157 within the fieldset at the top (except the first group in the form, and in some158 cases where thegroup of fields doesn't have a logical label).157 Admin forms are broken up into groups by ``fieldset`` elements. Each form fieldset 158 should have a class ``.module``. Each fieldset should have a header ``h2`` within the 159 fieldset at the top (except the first group in the form, and in some cases where the 160 group of fields doesn't have a logical label). 159 161 160 162 Each fieldset can also take extra classes in addition to ``.module`` to apply … … 178 180 Each form ``label`` and field should be enclosed in a header ``h4``. Any 179 181 explanation or help text should follow this ``h4`` in a ``p`` with class 180 ``.help``. Form ``label``s should always precede the field, except in the case182 ``.help``. Form labels should always precede the field, except in the case 181 183 of checkboxes and radio buttons, where the ``input`` should come first.
