MoodleDocs - User contributions [en]

CVS for Administrators

2007-10-08T19:50:45Z

Jonb: /* From a Unix computer */

The [http://moodle.cvs.sourceforge.net/moodle/moodle/ CVS archive] contains all the source code for Moodle. You can use a CVS program to extract versions ranging from the most stable release to the most cutting-edge development version. CVS can be an extremely convenient way of maintaining a Moodle server.

[[Image:Cvstree.png|CVS tree]]

Developers may have selective write access to the Moodle CVS archive using their Sourceforge username and password (see [[CVS for Developers]] for details about how to do this). However, most people only need read-only access, so they can just connect using '''anonymous CVS''' as described below. There can however currently be a delay of up to 1 hour between the time a developer commits changes to developer CVS and the time it becomes available on anonymous CVS.

==CVS Servers==

Until 25th April 2007, we only had one server available for anonymous CVS (moodle.cvs.sourceforge.net). Unfortunately anonymous CVS access on this server is now disabled.

Since then we have a growing list of anonymous CVS mirror servers around the world. Please choose the closest server to you from this list:

{| border="1" cellpadding="4" cellspacing="0"
|'''Country'''
|'''Server'''
|'''Provided by'''
|-
|EU
|'''[http://eu.cvs.moodle.org eu.cvs.moodle.org]'''
|Antonio Vicent and Eloy Lafuente (until more servers arrive - name will remain stable, don't worry)
|-
|ES
|'''es.cvs.moodle.org'''
|[http://www.mondragon.edu/ Mondragon Unibertsitatea] In case of trouble, contact [mailto:iarenuno@eteo.mondragon.edu iarenuno@eteo.mondragon.edu] or [mailto:iarenaza@escomposlinux.org iarenaza@escomposlinux.org]
|-
|UK
|'''uk.cvs.moodle.org'''
|Cumbria and Lancashire Education Online ([http://www.cleo.net.uk/ CLEO]) in collaboration with Lancaster University Network Services ([http://www.lancs.ac.uk/ LUNS])
|}

Replace the SERVER.cvs.moodle.org in the instructions below with the server you chose above!

For up-to-date alerts about planned or unplanned outages on any of these servers subscribe to the [https://lists.sourceforge.net/lists/listinfo/moodle-outage Moodle Outage mailing list].

(If you would like to contribute to the project by running a mirror, please see [[How to set up a CVS mirror]])

===Switching to a new server===

If you were ''already'' using CVS and want to switch to a different server, you'll probably need to make a small change so that the control files in your working copy will point to the new mirrors.

====Switching to a new server on Unix====

Use a shell command like this to change existing installations to point to the new mirror (UK mirror used in this example):

'''find . -type f -name Root -print0 | xargs -0 perl -pi -e 's/\@moodle\.cvs\.sourceforge\.net/\@uk\.cvs\.moodle\.org/''''

It can be run from /home, say, to fix multiple sites at once.

====Switching to a new server with TortoiseCVS====

If you were ''already'' using Tortoise CVS on Windows it's tricky, because Tortoise doesn't have any interface for changing the server. http://www.tortoisecvs.org/faq.html#changecvsroot explains it. But basically,

1) Install WinCVS and launch it.
2) Navigate to and select your Moodle folder.
3) Choose 'Macros'->CVS->Change Root from the menu.
4) Accept (or change) the default for the 'old' server.
5) Type the new server name. OK!

It takes a few seconds to go through all of the '''cvs''' folders and update the '''root''' files.

By the way, if you don't want to install WinCVS, another way of doing this is to uninstall your TortoiseCVS client on Windows, then do a regedit to clean up all the tortoisecvs related entries (might not be necessary), then reinstall TortoiseCVS client again (a good reason to upgrade to the most recent version of TortoiseCVS!). I have tested this and it cleared up the original setting of the original anonymous CVS server setting.

==Instructions==

===From a Unix computer===

To connect and login for the first time to the CVS server, you can use this command:

cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login

There is no password - when asked for one, just hit Enter.

To checkout (download) the entire Moodle code for the first time, use this command to get the latest STABLE version:

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -r MOODLE_18_STABLE moodle

Or the latest development version:

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co moodle

Or the modules in Contrib

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co contrib

Later, to update your local copy of Moodle to the current version in CVS you just need to go into your local Moodle directory and type:

cvs update -dP

To update your local copy of Moodle to a new version (e.g. from 1.7+ to 1.8), go into your local Moodle directory and type:

cvs update -dP -r MOODLE_18_STABLE

To update your local copy and to save the log of the process, use the following command instead the previous one:

cvs update -dP -r MOODLE_18_STABLE | tee upgrade.log

Then look at the upgrade.log, notably look for lines starting with "C" (conflict):

grep '^C' upgrade.log

Conflicts may appear in case you have manually modified your source files. You have to resolve conflicts before using the site. See [[CVS for Developers]] for more details.

===Changing the directory name===

By default, the CVS checkout creates a diectory on your webserver called 'moodle'. If you want your Moodle installation in a different directory, you can change the name of the directory that it will checkout the files to, by typing the follwing. This would download the MOODLE_18_STABLE branch into a directory called "mydirectory" (-d mydirectory).

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co '''-d mydirectory''' -r MOODLE_18_STABLE moodle

Or the latest development version to a directory called 'moodle-dev':

cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co '''-d moodle-dev''' moodle

You can also change the name of the directory after the files are downloaded, and before you go through the Moodle install process. If you change the name of the directory before install, it will not affect anything during the install or during a CVS update. If you change the name of the directory after an install, you will need to change the config.php to reflect the name change ([[Moodle_migration#Migrating_a_complete_Moodle_site|guidance here]]). It won't affect the CVS update though.

===From a Windows computer===

To get started with a fresh copy of Moodle, follow the following steps:[[Image:CVS moodle settings for tortoise CVS.jpg|thumb|Tortoise CVS Screen capture]]
[[Image:Ecran cvs.jpg|thumb|Tortoise CVS (real name) Screen capture]]
# Get TortoiseCVS from [http://www.tortoisecvs.org/ tortoisecvs.org] and install it, then reboot.
# Find or create a new folder somewhere where you want Moodle to be downloaded to.
# Right-mouse-click that folder and choose "CVS Checkout" from the menu. You should see a dialog box.
# Copy this text into the CVSROOT field: <code>:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle</code>
# Under the "Module" field, type "moodle" to get moodle. (Other options here include"contrib" to get the contrib directory of hacks and addons, or "mysql" to get the optional MySQL Admin module).
#* For the latest STABLE version, click on the "Revision" tab and then check the radio button labelled "Choose branch or tag". From the drop-down menu select MOODLE_18_STABLE.
#* If you don't see the very latest version in the long drop-down list under Branch or tag name, click the Update List button next to it and wait for the list to be updated.
#* For the latest UNSTABLE development version, the radio-button "Use HEAD branch" in the Revision tab should be checked.
# Press the button: "OK" and everything should be downloaded.

Later, to update your local copy of Moodle to the current version in CVS, just right-mouse-click the folder and choose "CVS Update".

Note that the enclosing moodle folder is self-contained - you can move it anywhere you like or even rename it.

'''NOTE.-''' Admins with a SourceForge account name can connect with their account name, see attached screen shot.

===From a Mac OS X computer===
You will find some information about CVS and Mac OS X in the documentation for the complete installation package Moodle4Mac. Please read [[Complete_Install_Packages_for_Mac_OS_X#How_To_Update_Your_Moodle4Mac | How To Update Your Moodle4Mac]]. It works fine with the new CVS servers.

==See also==

*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs] forum posting
*[[Development:Setting up Eclipse]] for step by step instructions for setting up the [http://www.eclipse.org/ Eclipse IDE] for Moodle development, which including how to do the necessary CVS operations.

[[Category:Administrator]]

[[fr:CVS pour administrateurs]]

CVS for Administrators

2007-04-28T09:08:54Z

Jonb: /* CVS Servers */

CVS for Administrators

2007-04-28T09:08:37Z

Jonb: /* CVS Servers */

CVS for Administrators

2007-04-28T09:08:18Z

Jonb: /* CVS Servers */

Development:Wikindx

2007-04-20T13:30:35Z

Jonb:

'''Notes on the possible integration of [http://wikindx.sourceforge.net/index2.html WIKINDX] with Moodle.'''

[http://wikindx.sourceforge.net/index2.html WIKINDX]is a free BiblioGraphic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.

Please also see the Moodle Discussion at http://moodle.org/mod/forum/discuss.php?d=23022

==Wikindx filter for Moodle==

Dan Stowell has created a "Wikindx filter" for Moodle which allows you to cross-link to a wikindx entry by typing (for example) wikindx:646. The filter is in contrib CVS, named "filter_wikindx" or can be downloaded at http://download.moodle.org/download.php/modules/filter_wikindx.zip

From MG:
Some design considerations for a moodle filter that enables a wikindx to be searched, a reference to be selected, page number(s) to be added and the in-text or footnote citation and full reference to be returned formatted to the user's requirements.

NB With everything else I have going on (PhD, Wikindx, life) I have no intention of setting up Moodle for testing this (no prior experience in Moodle let alone moodle filters) but, if someone is willing to a) write the moodle filter code and b) be prepared to run beta wikindx code to test the interface, then I would be more than happy to do whatever needs to be done in the wikindx code. The wikindx code will be easy: I can't speak for the moodle code (but, see below, imagine that quite a bit of it could be pulled from wikindx). I also have no idea if moodle filters alone can accomplish what I've suggested below or if the code needs greater integration in the moodle core code.

1/ The Moodle filter needs to provide 3 basic functions:
:a) an icon in the HTML text editor that opens a pop-up,
:b) the pop up should provide a simple search/select interface to wikindx resources,
:c) once the selected wikindx resource has been inserted into the text, the moodle HTML editor text is saved and the filter sends the reference (and style and page number(s)) to wikindx for formatting and insertion into the moodle text.

2/ Because what is supplied to the pop-up (see below) requires a connection to wikindx, the filter should have a config file for the wikindx database connection details. wikindx 3.4 now allows admins to lock out read-only users so this config file may also have the option to add a wikindx username::password pair (I would not favour this though).

3/ The search interface could be similar to the wikindx Quick Search interface less the ordering options (to save on space). [WIKINDX code (filling the pop-up)]

4/ The results of a search should be displayed with multiple resources next to radio buttons, a select box to choose the formatting style and text boxes to enter page number(s). Each radio button has a value that is the unique resource ID in the wikindx. [WIKINDX code]

5/ Once the appropriate resource has been selected and other details added, clicking on a 'process' button will add the appropriate filter mark-up which may be something like:
:wikindx:34:12[APA]
:wikindx:56:34-35[CHICAGO]

where the first number is the wikindx resource ID, the second number(s) is the page and [...] is the bibliographic style chosen. [WIKINDX code]

6/ On saving the moodle text, that markup is extracted and sent to the wikindx server (something like http://....index.php&externalResourceGrab&id=56&pages=34-35&style=CHICAGO) which then formats the requested resource and provides a string in return which would consist of a serialized/base64_encoded PHP multi-dimensional array which, when unpacked, would have something like the following (if APA for example):
:array(
::[style] = array(
:::[type] => "inText"
::),
::[citation] = array(
:::[56] => "(Martin et al. 1978, pp.34--35)"
::),
::[reference] = array(
:::[0] => "Martin, R. L., Thrift, N. J., & Bennett, R. J. (Eds.). (1978). ''Towards the dynamic analysis of spatial systems''. London: Pion."
::)
:);

for a footnote-type citation (e.g. Chicago), it might be:
:array(
::[style] = array(
:::[type] => "footnote",
:::[textMarkup] => "superscript",
:::[textStart] => "[",
:::[textEnd] => "] ",
:::[footnoteMarkup] => "normal",
:::[footnoteStart] => "",
:::[footnoteEnd] => ". "
::),
::[citation] = array(
:::[56] => "''Towards the Dynamic Analysis of Spatial Systems''. 1978. Edited by R. L. Martin, N. J. Thrift and R. J. Bennett. London: Pion. pp.34--35"
::),
::[reference] = array(
:::[0] => "''Towards the Dynamic Analysis of Spatial Systems''. 1978. Edited by R. L. Martin, N. J. Thrift and R. J. Bennett. London: Pion."
::)
:);

:NB 1/ The italics (and any underline, bold etc.) would be returned as HTML markup. [WIKINDX code]
:NB 2/ For footnote-type styles, [style][textMarkup] indicates whether the in-text reference ([1] for example should be 'superscript', 'subscript' or 'normal' (default)) -- for the footnote, such formatting could be HTML-encoded in [citation][56]. Ditto for the footnote.
:NB 3/ [style][textStart] and [style][textEnd] are characters that are printed before and after the in-text reference number. Ditto for the footnote. They may be blank.

7/ Moodle would take this array and, if [style][type] == 'footnote', insert something like '[1]' in the body of the text, [citation] as a footnote and, if required, append [reference] to a bibliography (perhaps this is just future-proofing in this case). However, if [style][type] == 'inText', [citation] would be inserted in the body of the text and [reference] appended.

8/ In the case of multiple citations, wikindx should be able to provide the second element of the array correctly ordered as per the style requirements. So you might have something like:

:array(
::[style] = array(
:::[type] => "inText"
::),
::[citation] = array(
:::[56] => "(Martin et al. 1978, pp.34--35)",
:::[34] => "(Aarseth et al. 2003)"
::),
::[reference] = array(
:::[0] => "Aarseth, E., Smedstad, S. M., & Sunnanå, L. (2003, November 4—6). ''A multi-dimensional typology of games''. Paper presented at Level Up, Utrecht Universiteit.",
:::[1] => "Martin, R. L., Thrift, N. J., & Bennett, R. J. (Eds.). (1978). ''Towards the dynamic analysis of spatial systems''. London: Pion."
::)
:);

In this way separate orders are maintained for the citation and the appended bibliography. Additionally, having [citation][56] and [citation][34] allows for a quick search and replace, once the array has been returned, on the moodle text using something like "/\Wwikindx:$citationIndex.*\s/Ui"
[WIKINDX code]

Perhaps the above is not do-able as a simple moodle filter?

It should be noted that the footnote type display of citations above is a simplified version of what the full WIKINDX/OSBib code offers where, in addition to deciding on endnote/footnote types, there is also the possibility for in-text footnote references to be repeated/reused if they refer to the same reference, for in-text citations to be manipulated or even dropped entirely on a whole set of conditions (title/author name in same sentence, that reference already referred to in the text body etc. etc. etc.) just to name a few of the extra processing on offer. All of this is, of course, in the case of multiple citations within the same body of text. To get this functionality, the whole body of text would need to be sent to wikindx for processing -- this may be a step too far in this case.

::Perhaps sending the complete body of text would be easiest. I can simply set the wikindx code to ignore markup outside the wikindx::xxxx tag. --[[User:Mark Grimshaw|Mark Grimshaw]] 13:31, 3 September 2006 (CDT)

==Outline thoughts on integration...==

1. Do we need to allowing a user already logged into a Moodle site to be seamlessly logged in to a wikindx? Or maybe just use the same login details between the two (like the way that Moodle.org and MoodleDocs works). If necessary, something could be added to wikindx to enable this. In most cases though, with the right config settings, wikindx will allow any read only request without requiring login.

2. Another issue is how to integrate the paper writing function of Wikindx into Moodle. What about use of the HTML editor? Could it be integrated some way with the Netpublish module? Imagine students or professors being able to use it to write academic papers and then publish those on the Moodle site. Currently wikindx publishes papers solely to RTF. It should be simple to publish to HTML since that's what the raw document is anyway (a matter of adding HTML header/footer, formatting citations and appending bibliographies -- most of this code is already in wikindx but not (yet) made available to the word processor). Compared to other HTML editors, the only additional options wikindx offers in its version are buttons to import citations, metadata and insert footnotes. All the rest (barring stats, timestamps, save etc.) are font/text formatting.

3. For the filter above, how do you decide what bibliographic style to present in (APA, Chicago, IEEE etc.)? Presumably, this is something that could be set in the filter config file. (Although I haven't seen the filter in operation, I'm assuming it picks up a properly formatted reference for insert. Either short (Grimshaw, 2006) or long (Grimshaw, Mark N. 2006, WIKINDX [OSS].) for example. Is the only method of citation available parenthetical? Is it possible to use endnotes (or footnotes) as well? Yes, endnote/footnote styles are available as well.

:''Note from DS: No, at present the Wikindx filter simply displays the text "wikindx:646" (for example). It's a very simple start and I hope that people with more knowledge of Wikindx will be able to modify it to extract the properly-formatted reference direct from Wikindx. If wikindx had a system whereby a certain URL call would supply the reference text in whatever style was configured for wikindx, this would be a good way to display the citation nicely within Moodle. Does such a call exist? I don't think so. Something like mywikindx.com/index.php?'''action=resourceGrabCitation'''&id=501 would be required.''

:''Note from JB: As the wikindx admin can set the default bibliographic style in the config, the filter will just present that style. The filter is simple but oh so useful! So when I type '''wikindx:1''' into my moodle installation, it creates an automatic link to http://www.baillie.org.uk/wikindx//index.php?action=resourceView&id=1

:''Note from MG: action=resourceGrabCitation can be added and the default citation formatting applied. A possible gotcha in that there may be a problem with footnote/endnote style citation is that not only would you need the footnote marker (e.g. [1]) but you would also need the full reference to be appended to the text as a footnote (I'm assuming this is required rather than just using [1] as a hyperlink to the wikindx resource -- presumably you would want to use the same strict referencing that students are required to use). Hence, in this case, the returned values would consist of two values -- one the citation to be hyperlinked and the other the full reference to be appended.''

:''Note from MG: In wikindx, inserting a citation into metadata or the word processor involves clicking on an icon which opens a popup. In this, there is a select box listing short entries of all available resources and some text fields for users to enter cited page numbers. Perhaps something similar could be used in the moodle wikindx filter to avoid the hassle of having to look up the wikindx resource id before entering it into moodle. This pop-up could also list the available citation/bibliographic styles on the wikindx allowing the user to select the style with which the citation should be formatted prior to insertion into moodle.''

4. Mark, your remarks in 2 have gotten me thinking. Although not everyone likes the Moodle HTML area editor that much, it still is the standard way of creating text in Moodle and perhaps a way of integrating Wikindx would be to add buttons for Wikindx to it, just like the kind described above in Wikindx's native editor. I needed to integrate a hieroglyph editor into my site and Janne Mikkonen helped me to add it through a button in the html editor that pops up a window, in which the student type the hieroglyphs they need, and then click a button to have them inserted back into the editor-similar to the way the insert image popup works. I would imagine something similar could be done with Wikindx. The advantage of this is that it would make Wikindx accessible anywhere within Moodle, rather than just as a separate module. You might also want a standalone module option whereby students could collaborate on creating bibliographies together.

:''Note from MG: Adding the appropriate buttons would be my suggestion. In wikindx, citations are added by the popup automatically adding something like''
:''[cite]146:22-23[/cite]''
:''where 146 is the resource ID in the database and 22-23 are the page nos. This can be added via a cite button or will be appended to an inserted quotation/paraphrase via the wikindx 'insert metadata' button. Footnotes (i.e. parenthetical thoughts as opposed to citation footnotes - WIKINDX does handle those footnotes/endnotes as well) are inserted via a button which encloses the inserted footnote in:''
:''[footnote]....[/footnote]''

:''Exporting to RTF, the cite tags are substituted with the formatted citation marker (in-text or footnote/endnote), bibliographic information is extracted and appended to a bibliography and footnote tags are converted to RTF footnotes. Of course, all HTML code (font/text formatting, tables, lists, images etc.) are converted to their appropriate RTF code too.''

5. Re the citation/bibliographic formatting, the PHP code for this has been extracted from wikindx and made available to other OSS apps at http://bibliophile.sourceforge.net (I think Aigaion and Bibliograph use it or are about to) so it may be easy enough for Moodle to use this too. In fact doubly easy if moodle interfaces with a wikindx because the quickest way to set up the formatting engine is to provide data to it in exactly the same PHP associative array that wikindx natively expects.

6. What capabilities are there in Wikindx at this time for different capabilities in using bibliographies? Can bibliographies be shared by a predefined group/all users? Can some people be given the ability to add to a bibliography while others can only use the bibilography? Can bibliography entries be required to have approval by some person before they are displayed to all? These would be nice features to have.

:''MG: WIKINDX recognizes two types of bibliography; the master bibliography (MB) and user bibliographies (UB). The MB holds the resources while UBs merely have references to resources from the MB. Currently both the MB and UBs are readable by all users. A UB is owned by a user and only he/she can add/delete references to resources. All write enabled users can add to the MB. Because I'm aiming towards collaborative authoring in the word processor (SUWP), a long-standing feature to be implemented is to add user groups (i.e. research teams). Then, the owner of a UB can add other users with write access to the UB and only those users can browse the UB. Additionally, a user can make comments and musings private, shared with a group or public. Of course, a SUWP article can be shared among a group. This hasn't been implemented yet -- I need to find someone familiar with wiki technology to help implement the collaborative authoring first.''

[[Category:Developer]]

Homepage design

2006-08-10T19:39:21Z

Jonb:

{{Scrapbook}}

The [http://moodle.org moodle.org] theme is not included in the standard Moodle download, however theme designers are welcome to take ideas from its homepage design.

The centre sections are created using H1 and P tags (defined in your css file). The code should be placed in the single html block that is formed when you switch the setting for "Include a topic section" to 'yes' in your Admin Site Setting (yourmoodle/admin/site.php)

<pre>
<div class="frontblock">
<h1 class="frontblock fronthead p1">Welcome to Moodle!</h1>
<p class="fronttext p1">
text...
</p>
</div>

<div class="frontblock">
<h1 class="frontblock fronthead p2">Moodle Community</h1>
<p class="fronttext p2">
text...
</p>
</div>

<div class="frontblock">
<h1 class="frontblock fronthead p3"><span class="nolink">Moodle Development</span></h1>
<p class="fronttext p3">
text...
</p>
</div>

<div class="frontblock">
<h1 class="frontblock fronthead p4"><span class="nolink">Moodle Downloads</span></h1>
<p class="fronttext p4">
text...
</p>
</div>
</pre>

The H1 and P tags are then styled to match the blocks.

<pre>
.fronthead {
font-size:1.3em;
letter-spacing:0.04em;
}

.fronttext {
margin-top:5px;
margin-left:20px;
margin-right:10px;
margin-bottom:20px;
}

div.frontblock {
margin-top: 12px;
margin-bottom: 25px;
border: #DDD solid 1px;
-moz-border-radius-bottomleft: 20px;
-moz-border-radius-bottomright: 20px;
font-size: 0.95em;
}

h1.frontblock {
border: #DDD solid 1px;
background-image: url(gradient.jpg);
background-position: top;
background-repeat: repeat-x;
padding: 1px 10px;
display: inline;
position: relative;
top: -0.5em;
left: 8px;
font-weight: normal;
}

p.fronttext.p1 {
min-height: 90px;
}
p.fronttext.p2 {
min-height: 90px;
}
p.fronttext.p3 {
min-height: 125px;
}
p.fronttext.p4 {
min-height: 105px;
}</pre>

==External links==
* [http://www.w3.org/TR/REC-html40/interact/forms.html#h-17.10 W3C 17.10 Adding structure to forms] - The recommended use of fieldset and legend elements is for adding structure to forms.

[[Category:Administrator]]
[[Category:Developer]]
[[Category:Themes]]

Homepage design

2006-08-10T19:37:55Z

Jonb:

{{Scrapbook}}

The [http://moodle.org moodle.org] theme is not included in the standard Moodle download, however theme designers are welcome to take ideas from its homepage design.

The centre sections are created using H1 and P tags (defined in your css file). The code should be placed in the single html block that is formed when you switch the setting for "Include a topic section" to 'yes' in your Admin Site Setting (yourmoodle/admin/site.php)

<pre>
<div class="frontblock">
<h1 class="frontblock fronthead p1">Welcome to Moodle!</h1>
<p class="fronttext p1">
text...
</p>
</div>

<div class="frontblock">
<h1 class="frontblock fronthead p2">Moodle Community</h1>
<p class="fronttext p2">
text...
</p>
</div>

<div class="frontblock">
<h1 class="frontblock fronthead p3"><span class="nolink">Moodle Development</span></h1>
<p class="fronttext p3">
text...
</p>
</div>

<div class="frontblock">
<h1 class="frontblock fronthead p4"><span class="nolink">Moodle Downloads</span></h1>
<p class="fronttext p4">
text...
</p>
</div>
</pre>

The H1 and P tags are then styled to match the blocks.

<pre>
.fronthead {
font-size:1.3em;
letter-spacing:0.04em;
}

.fronttext {
margin-top:5px;
margin-left:20px;
margin-right:10px;
margin-bottom:20px;
}

div.frontblock {
margin-top: 12px;
margin-bottom: 25px;
border: #DDD solid 1px;
-moz-border-radius-bottomleft: 20px;
-moz-border-radius-bottomright: 20px;
font-size: 0.95em;
}

h1.frontblock {
border: #DDD solid 1px;
background-image: url(gradient.jpg);
background-position: top;
background-repeat: repeat-x;
padding: 1px 10px;
display: inline;
position: relative;
top: -0.5em;
left: 8px;
font-weight: normal;
}

p.fronttext.p1 {
min-height: 90px;
}
p.fronttext.p2 {
min-height: 90px;
}
p.fronttext.p3 {
min-height: 125px;
}
p.fronttext.p4 {
min-height: 105px;
}
}</pre>

==External links==
* [http://www.w3.org/TR/REC-html40/interact/forms.html#h-17.10 W3C 17.10 Adding structure to forms] - The recommended use of fieldset and legend elements is for adding structure to forms.

[[Category:Administrator]]
[[Category:Developer]]
[[Category:Themes]]

Development:Wikindx

2006-08-09T11:09:38Z

Jonb: /* Outline thoughts on integration... */

Development:Developer notes

2006-08-08T15:19:53Z

Jonb:

<p class="note"> '''Note for contributors:''' This area is for developers to work on various bits of code and documentation as necessary. Once material has matured it should be linked to from the main [[Developer documentation]] page.
Initial text has been taken from [http://moodle.org/course/view.php?id=5 Using Moodle] Developer Wiki. If you find any text missing, please email docs AT moodle DOT org.</p>

*[[Forum development|Forum functional upgrade]]
*[[Other lang issues|Language issues]]
*[[MoodleDocs development]]
*[[Datalib Notes]]
*[[Usability]]
*[[Blogs and forums|Blogs, forums and the nature of discussion]]
*[[Document Management API]]
*[[Filters schema]]
*[[Filterall support]]
*[[Application/session variables]]
*[[Wiki development|Wiki module development]]
*[[Conditional activities]]
*[[Roles]]
*[[Improved Payment Plugin]]
*[[Moodle forms library]]
*[[Martin form notes]]
*[[wikindx|Possible integration of WIKINDX with Moodle]]

[[Category:Developer]]

Development:Developer notes

2006-08-08T15:18:47Z

Jonb:

Development:Wikindx

2006-08-08T15:07:22Z

Jonb: Notes on the possible integration of WIKINDX with Moodle