Posts made by Urs Hunkler

Moodle in English -> General developer forum -> Course Page Structure

by Urs Hunkler -
Picture of Core developers

Hi,

in the structure of the course page I discovered inconsistent naming:

TABLE                            topicsoutline
     TBODY
         TR         section_0
              TD                 topicsoutlineside
              TD                 topicsoutlinecontent
              TD                 topicsoutlineside

         TR
         TR

              TD                 topicsoutlineside
              TD     section_1   topicsoutlinecontent
              TD                 topicsoutlineside

The first TR is named ID "section_0", the other section IDs apply to the "topicsoutlinecontent" TD. The sections cover both sides and the content. I propose to name the TR tags with the ID "section-n" with n = 0 to numer of courses (underscores can be expected critical in some browsers).

Average of ratings: -

Moodle in English -> Themes -> standard orange -> Re: standard orange

by Urs Hunkler -
Picture of Core developers

Jon and Martin,

if you want to enter this wide field I propose to consider the following. For all parts of a Moodle page with a somehow similar structure and task standard names can be used:

.header
.content
.leftside
.rightside
.footer

Based on that names many chunks can be named and addressed in CSS with "Contextual Selectors" like:

_ "Forumpost"

forumpost

the CSS could look like:

.forumpost .picture { }
.forumpost .topic { }
.forumpost .leftside { }
.forumpost .content { }
.forumpost .footer { } /* distance 
to the next post could be omited and done 
by .forumpost {margin-bottom:1em;} */

_ course "Topicsoutline"

topicsoutline

the CSS could look like:

.topicsoutline .content { }
.topicsoutline .leftside { }
.topicsoutline .rightside { }

and the informations in a list:
.topicsoutline .content .list { }

and the single info in every row:
.topicsoutline .content .list .r0/.r1 { }

_ "Sideblock"

sideblock

the CSS could look like:

.sideblock .header { }
.sideblock .content { }
.sideblock .footer { }

and the informations in a list:
.sideblock .content .list { }
or shorter
.sideblock .list { }

and the single info in every row:
.sideblock .content .list .r0/.r1 { }
or shorter
.sideblock .r0/r1 { }

What do you think?

Picture of Core developers

I'll chime in this discussion with a question.

What is easier, to add alt tags or to explain the very sophisticated reasons to everybody running the test and getting warnings? So I think, using descriptive title tags and short alt tags would help everybody and avoid those warnings.

I noticed, that firefox doesn'd show the alt description but only the title description - is that right?

Picture of Core developers

Hello Marc,

with the doctype change from "HTML 4.01 transitional" to "XHTML 1.0 Transitional" those scrollbar properties defined in the "body" tag don't work any more.

If you add those "special only for IE on windows" properties to the "html" tag it works again. I've tried this code on the latest 1.5Dev with IE 6 on Windows.

html {
   scrollbar-face-color: #739FC4;
   scrollbar-track-color: #ffffff;
   scrollbar-arrow-color: #B9DFFE;
   scrollbar-shadow-color: #92F9FD;
   scrollbar-3dlight-color: #ADD8E6;
   scrollbar-darkshadow-color: #000000;
   buttonface: #FF0000;
}

The "background-color" you can change within the "body" tag and the font-family property within styles_fonts.

I hope that helps
Urs