Standards: Difference between revisions
Urs Hunkler (talk | contribs) m (→Lists) |
Urs Hunkler (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
== How to Style Moodle Standard Page Elements and and Page Parts == | == How to Style Moodle Standard Page Elements and and Page Parts == | ||
Similar functions or similar content should look and feel the same on all Moodle pages. The more consequent these principles are implemented the easer and less hindering the VLE will interfere the working/learning process. The Vision is that Moodle pages build on the same function patterns (PHP and JavaScript) and | Similar functions or similar content should look and feel the same on all Moodle pages. The more consequent these principles are implemented the easer and less hindering the VLE will interfere the working/learning process. The Vision is that Moodle pages build on the same function patterns (PHP and JavaScript) and content patterns (XHTML) and design patterns (CSS). For the contrary the consequences are that the special code for every Moodle module lets the Moodle files and CSS grow and that module, block and theme design gets more difficult and tedious. | ||
=== Lists === | === Lists === | ||
Lists are widely used all over Moodle. They appear in the sideblocks, they are used on the course pages. Many Moodle developers currently use the up-to-date combination of XHTML lists and CSS styling for navigation as in the SCORM or the CMS module. I regularly use them for navigation lists in HTML blocks. When all lists use the same XHTML and CSS it is easy to design different Moodle themes consistent and with few changes. Actually all lists are different. | Lists are widely used all over Moodle. They appear in the sideblocks, they are used on the course pages. Many Moodle developers currently use the up-to-date combination of XHTML lists and CSS styling for navigation as in the SCORM or the CMS module. I regularly use them for navigation lists in HTML blocks. When all lists use the same XHTML and CSS it is easy to design different Moodle themes consistent and with few changes. Actually all lists are different. | ||
I took the following example from the List-o-Matic Website [http://www.accessify.com/tools-and-wizards/list-o-matic/list-o-matic.asp] for easy reproduction. You find detailed descriptions about XHTML/CSS lists in the Listutorial | I took the following example from the List-o-Matic Website [http://www.accessify.com/tools-and-wizards/list-o-matic/list-o-matic.asp] for easy reproduction. You find detailed descriptions about XHTML/CSS lists in the Listutorial | ||
[http://css.maxdesign.com.au/listutorial/index.htm]. | [http://css.maxdesign.com.au/listutorial/index.htm]. | ||
Revision as of 13:47, 30 August 2005
How to Style Moodle Standard Page Elements and and Page Parts
Similar functions or similar content should look and feel the same on all Moodle pages. The more consequent these principles are implemented the easer and less hindering the VLE will interfere the working/learning process. The Vision is that Moodle pages build on the same function patterns (PHP and JavaScript) and content patterns (XHTML) and design patterns (CSS). For the contrary the consequences are that the special code for every Moodle module lets the Moodle files and CSS grow and that module, block and theme design gets more difficult and tedious.
Lists
Lists are widely used all over Moodle. They appear in the sideblocks, they are used on the course pages. Many Moodle developers currently use the up-to-date combination of XHTML lists and CSS styling for navigation as in the SCORM or the CMS module. I regularly use them for navigation lists in HTML blocks. When all lists use the same XHTML and CSS it is easy to design different Moodle themes consistent and with few changes. Actually all lists are different. I took the following example from the List-o-Matic Website [1] for easy reproduction. You find detailed descriptions about XHTML/CSS lists in the Listutorial [2].
Resources about Lists on the Web
[1]
List-o-Matic
[2] Listutorial
