Martin Dougiamas tarafından yapılan gönderiler

Moodle in English -> Hardware and performance -> Moodle Bloat. -> Re: Moodle Bloat.

yazan Martin Dougiamas -
Core developers 'ın resmi Documentation writers 'ın resmi Moodle HQ 'ın resmi Plugin developers 'ın resmi Testers 'ın resmi
As someone said, the bigger files are only loaded once per session generally, because they are designed to cache.

We are talking in various corners about ways to streamline the CSS files in future. It's not easy, Moodle isn't simple, but there are things to improve for sure, such as more consistent design across modules.

In the meantime, you can try some of the things people have suggested here plus things like:

- use mod_gzip on the server to compress things (moodle.org does this for example)
- stick with the "standard" themes
- examine some other big web apps and you might be surprised how fat many of them actually are!
Core developers 'ın resmi Documentation writers 'ın resmi Moodle HQ 'ın resmi Plugin developers 'ın resmi Testers 'ın resmi

Hi Richard,

Sorry, I don't think there was ever such a list of projects on moodle.com.

Anyway, the best place to "hook up" on these things these days, whether you are a developer looking for paid work, or someone looking to pay a developer, is on the Moodle jobs board.

Also, specific small projects intended for core Moodle should be listed in the Moodle Tracker etc regardless of who is working on it, just so everyone knows what's going on.

More info can be found here: http://docs.moodle.org/en/Development:Overview

(Edited by Helen Foster to fix the Moodle jobs board link - original submission Sunday, 1 June 2008, 06:10 PM)

Core developers 'ın resmi Documentation writers 'ın resmi Moodle HQ 'ın resmi Plugin developers 'ın resmi Testers 'ın resmi
That's probably the best way in general (the XMLDB editor in Moodle can generate these statements for you). [Note the syntax has changed a little in Moodle 2.0 as part of the whole recent DML and DDL refactoring]

If you really just want to load an install.xml file in one shot without any checking for previous tables etc you can do it like this:


install_from_xmldb_file('/your/full/file/path/install.xml');