Tag: LAE-V1

Liberal Arts Edition v1.0 Released

Moodle Liberal Arts Edtion v1.0 is available for download. The project’s home page includes the full Liberal Arts Edition v1.0 package, as well as its components broken out for individual download. It also includes links to a number of recommended extensions that a number of CLAMP schools use, but need further development before they are folded into the LAE.

Included in the initial LAE release are:

  • TinyMCE 2.x: A WYSIWYG editor that replaces the outdated HTMLArea editor that ships with Moodle. TinyMCE offers a streamlined interface, DragMath support, and better cutting and pasting from Microsoft Word.
  • SimplePie RSS: A replacement for the deprecated Magpie RSS parser that included with Moodle. SimplePie RSS supports a greater variety of feeds than Magpie.
  • Quickmail: An simple block that allows faculty to quickly send an email to students in a class. This replicates functionality founding other LMS systems.
  • Filtered Course Block: A block that allows administrators to display a list of courses based on the current and future terms.

Visit the Moodle Liberal Arts Edition v1.0 page to download the full package or its individual components.

Update 11/4/09: There is a security release available for this version of the LAE.

Liberal Arts Edition Update for 7/31

At Hack/Doc Fest we set a release date of July 31, 2009 for Moodle: Liberal Arts Edition v1.0, a packaged version of Moodle which incorporates our most-used modules, bug fixes, and home-grown and add-ons. Go to the Liberal Arts Edition v1.0 for a complete inventory.

The release date has been delayed until August 7, 2009 in order to give us more time to test code and put the finishing touches on our Subversion repository. Most of the LAE is completed, and we plan to start releasing stand-alone code next week. A test version of the final LAE build will be available on Wednesday, and the finished version will be available on Friday.

Those who have access to Redmine can download the current development version of the code through Subversion (and we welcome the additional testers). Instructions for doing so can be found in the Development project.