https://docs.moodle.org/501/en/api.php?action=feedcontributions&feedformat=atom&user=Martin 2026-04-10T08:29:54Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/501/en/index.php?title=License&diff=6721 2006-03-02T06:50:22Z

<p>Martin: /* Copyright License for Moodle */</p> <hr /> <div>{{About Moodle}}<br /> ==Copyright License for Moodle==<br /> <br /> The ''name'' '''Moodle™''' is a registered trademark of Moodle Pty Ltd.<br /> If you are intending to use the name to promote commercial Moodle services,<br /> then you must seek permission from the Trust via the [http://moodle.com/helpdesk/ moodle.com helpdesk], in accordance with normal trademark restrictions. There are no restrictions<br /> on how you use the name in other contexts.<br /> <br /> The ''software'' '''Moodle''' is Copyright © 1999 onwards, [http://dougiamas.com/ Martin Dougiamas].<br /> <br /> This program is free software; you can redistribute it and/or modify<br /> it under the terms of the GNU General Public License as published by<br /> the Free Software Foundation; either version 2 of the License, or<br /> (at your option) any later version.<br /> <br /> This program is distributed in the hope that it will be useful,<br /> but WITHOUT ANY WARRANTY; without even the implied warranty of<br /> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br /> GNU General Public License below for more details.<br /> <br /> ----<br /> <br /> <br /> <br /> &lt;center&gt;&lt;b&gt;GNU GENERAL PUBLIC LICENCE&lt;/b&gt;&lt;/center&gt;<br /> &lt;center&gt;Version 2, June 1991&lt;/center&gt;<br /> <br /> &lt;blockquote&gt;Copyright (C) 1989, 1991 Free Software Foundation, Inc.<br /> 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<br /> Everyone is permitted to copy and distribute verbatim copies<br /> of this license document, but changing it is not allowed.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;The licenses for most software are designed to take away your<br /> freedom to share and change it. By contrast, the GNU General Public<br /> License is intended to guarantee your freedom to share and change free<br /> software--to make sure the software is free for all its users. This<br /> General Public License applies to most of the Free Software<br /> Foundation's software and to any other program whose authors commit to<br /> using it. (Some other Free Software Foundation software is covered by<br /> the GNU Library General Public License instead.) You can apply it to<br /> your programs, too.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;When we speak of free software, we are referring to freedom, not<br /> price. Our General Public Licenses are designed to make sure that you<br /> have the freedom to distribute copies of free software (and charge for<br /> this service if you wish), that you receive source code or can get it<br /> if you want it, that you can change the software or use pieces of it<br /> in new free programs; and that you know you can do these things.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;To protect your rights, we need to make restrictions that forbid<br /> anyone to deny you these rights or to ask you to surrender the rights.<br /> These restrictions translate to certain responsibilities for you if you<br /> distribute copies of the software, or if you modify it.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;For example, if you distribute copies of such a program, whether<br /> gratis or for a fee, you must give the recipients all the rights that<br /> you have. You must make sure that they, too, receive or can get the<br /> source code. And you must show them these terms so they know their<br /> rights.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;We protect your rights with two steps: (1) copyright the software, and<br /> (2) offer you this license which gives you legal permission to copy,<br /> distribute and/or modify the software.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Also, for each author's protection and ours, we want to make certain<br /> that everyone understands that there is no warranty for this free<br /> software. If the software is modified by someone else and passed on, we<br /> want its recipients to know that what they have is not the original, so<br /> that any problems introduced by others will not reflect on the original<br /> authors' reputations.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Finally, any free program is threatened constantly by software<br /> patents. We wish to avoid the danger that redistributors of a free<br /> program will individually obtain patent licenses, in effect making the<br /> program proprietary. To prevent this, we have made it clear that any<br /> patent must be licensed for everyone's free use or not licensed at all.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;The precise terms and conditions for copying, distribution and<br /> modification follow.&lt;/blockquote&gt;<br /> <br /> &lt;center&gt;GNU GENERAL PUBLIC LICENSE&lt;/center&gt;<br /> &lt;center&gt;TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION&lt;/center&gt;<br /> <br /> &lt;blockquote&gt;0. This License applies to any program or other work which contains<br /> a notice placed by the copyright holder saying it may be distributed<br /> under the terms of this General Public License. The &quot;Program&quot;, below,<br /> refers to any such program or work, and a &quot;work based on the Program&quot;<br /> means either the Program or any derivative work under copyright law:<br /> that is to say, a work containing the Program or a portion of it,<br /> either verbatim or with modifications and/or translated into another<br /> language. (Hereinafter, translation is included without limitation in<br /> the term &quot;modification&quot;.) Each licensee is addressed as &quot;you&quot;.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Activities other than copying, distribution and modification are not<br /> covered by this License; they are outside its scope. The act of<br /> running the Program is not restricted, and the output from the Program<br /> is covered only if its contents constitute a work based on the<br /> Program (independent of having been made by running the Program).<br /> Whether that is true depends on what the Program does.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;1. You may copy and distribute verbatim copies of the Program's<br /> source code as you receive it, in any medium, provided that you<br /> conspicuously and appropriately publish on each copy an appropriate<br /> copyright notice and disclaimer of warranty; keep intact all the<br /> notices that refer to this License and to the absence of any warranty;<br /> and give any other recipients of the Program a copy of this License<br /> along with the Program.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;You may charge a fee for the physical act of transferring a copy, and<br /> you may at your option offer warranty protection in exchange for a fee.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;2. You may modify your copy or copies of the Program or any portion<br /> of it, thus forming a work based on the Program, and copy and<br /> distribute such modifications or work under the terms of Section 1<br /> above, provided that you also meet all of these conditions:&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;a) You must cause the modified files to carry prominent notices<br /> stating that you changed the files and the date of any change.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;b) You must cause any work that you distribute or publish, that in<br /> whole or in part contains or is derived from the Program or any<br /> part thereof, to be licensed as a whole at no charge to all third<br /> parties under the terms of this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;c) If the modified program normally reads commands interactively<br /> when run, you must cause it, when started running for such<br /> interactive use in the most ordinary way, to print or display an<br /> announcement including an appropriate copyright notice and a<br /> notice that there is no warranty (or else, saying that you provide<br /> a warranty) and that users may redistribute the program under<br /> these conditions, and telling the user how to view a copy of this<br /> License. (Exception: if the Program itself is interactive but<br /> does not normally print such an announcement, your work based on<br /> the Program is not required to print an announcement.)&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;These requirements apply to the modified work as a whole. If<br /> identifiable sections of that work are not derived from the Program,<br /> and can be reasonably considered independent and separate works in<br /> themselves, then this License, and its terms, do not apply to those<br /> sections when you distribute them as separate works. But when you<br /> distribute the same sections as part of a whole which is a work based<br /> on the Program, the distribution of the whole must be on the terms of<br /> this License, whose permissions for other licensees extend to the<br /> entire whole, and thus to each and every part regardless of who wrote it.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Thus, it is not the intent of this section to claim rights or contest<br /> your rights to work written entirely by you; rather, the intent is to<br /> exercise the right to control the distribution of derivative or<br /> collective works based on the Program.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;In addition, mere aggregation of another work not based on the Program<br /> with the Program (or with a work based on the Program) on a volume of<br /> a storage or distribution medium does not bring the other work under<br /> the scope of this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;3. You may copy and distribute the Program (or a work based on it,<br /> under Section 2) in object code or executable form under the terms of<br /> Sections 1 and 2 above provided that you also do one of the following:&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;a) Accompany it with the complete corresponding machine-readable<br /> source code, which must be distributed under the terms of Sections<br /> 1 and 2 above on a medium customarily used for software interchange; or,&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;b) Accompany it with a written offer, valid for at least three<br /> years, to give any third party, for a charge no more than your<br /> cost of physically performing source distribution, a complete<br /> machine-readable copy of the corresponding source code, to be<br /> distributed under the terms of Sections 1 and 2 above on a medium<br /> customarily used for software interchange; or,&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;c) Accompany it with the information you received as to the offer<br /> to distribute corresponding source code. (This alternative is<br /> allowed only for noncommercial distribution and only if you<br /> received the program in object code or executable form with such<br /> an offer, in accord with Subsection b above.)&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;The source code for a work means the preferred form of the work for<br /> making modifications to it. For an executable work, complete source<br /> code means all the source code for all modules it contains, plus any<br /> associated interface definition files, plus the scripts used to<br /> control compilation and installation of the executable. However, as a<br /> special exception, the source code distributed need not include<br /> anything that is normally distributed (in either source or binary<br /> form) with the major components (compiler, kernel, and so on) of the<br /> operating system on which the executable runs, unless that component<br /> itself accompanies the executable.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;If distribution of executable or object code is made by offering<br /> access to copy from a designated place, then offering equivalent<br /> access to copy the source code from the same place counts as<br /> distribution of the source code, even though third parties are not<br /> compelled to copy the source along with the object code.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;4. You may not copy, modify, sublicense, or distribute the Program<br /> except as expressly provided under this License. Any attempt<br /> otherwise to copy, modify, sublicense or distribute the Program is<br /> void, and will automatically terminate your rights under this License.<br /> However, parties who have received copies, or rights, from you under<br /> this License will not have their licenses terminated so long as such<br /> parties remain in full compliance.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;5. You are not required to accept this License, since you have not<br /> signed it. However, nothing else grants you permission to modify or<br /> distribute the Program or its derivative works. These actions are<br /> prohibited by law if you do not accept this License. Therefore, by<br /> modifying or distributing the Program (or any work based on the<br /> Program), you indicate your acceptance of this License to do so, and<br /> all its terms and conditions for copying, distributing or modifying<br /> the Program or works based on it.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;6. Each time you redistribute the Program (or any work based on the<br /> Program), the recipient automatically receives a license from the<br /> original licensor to copy, distribute or modify the Program subject to<br /> these terms and conditions. You may not impose any further<br /> restrictions on the recipients' exercise of the rights granted herein.<br /> You are not responsible for enforcing compliance by third parties to<br /> this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;7. If, as a consequence of a court judgment or allegation of patent<br /> infringement or for any other reason (not limited to patent issues),<br /> conditions are imposed on you (whether by court order, agreement or<br /> otherwise) that contradict the conditions of this License, they do not<br /> excuse you from the conditions of this License. If you cannot<br /> distribute so as to satisfy simultaneously your obligations under this<br /> License and any other pertinent obligations, then as a consequence you<br /> may not distribute the Program at all. For example, if a patent<br /> license would not permit royalty-free redistribution of the Program by<br /> all those who receive copies directly or indirectly through you, then<br /> the only way you could satisfy both it and this License would be to<br /> refrain entirely from distribution of the Program.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;If any portion of this section is held invalid or unenforceable under<br /> any particular circumstance, the balance of the section is intended to<br /> apply and the section as a whole is intended to apply in other<br /> circumstances.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;It is not the purpose of this section to induce you to infringe any<br /> patents or other property right claims or to contest validity of any<br /> such claims; this section has the sole purpose of protecting the<br /> integrity of the free software distribution system, which is<br /> implemented by public license practices. Many people have made<br /> generous contributions to the wide range of software distributed<br /> through that system in reliance on consistent application of that<br /> system; it is up to the author/donor to decide if he or she is willing<br /> to distribute software through any other system and a licensee cannot<br /> impose that choice.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;This section is intended to make thoroughly clear what is believed to<br /> be a consequence of the rest of this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;8. If the distribution and/or use of the Program is restricted in<br /> certain countries either by patents or by copyrighted interfaces, the<br /> original copyright holder who places the Program under this License<br /> may add an explicit geographical distribution limitation excluding<br /> those countries, so that distribution is permitted only in or among<br /> countries not thus excluded. In such case, this License incorporates<br /> the limitation as if written in the body of this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;9. The Free Software Foundation may publish revised and/or new versions<br /> of the General Public License from time to time. Such new versions will<br /> be similar in spirit to the present version, but may differ in detail to<br /> address new problems or concerns.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Each version is given a distinguishing version number. If the Program<br /> specifies a version number of this License which applies to it and &quot;any<br /> later version&quot;, you have the option of following the terms and conditions<br /> either of that version or of any later version published by the Free<br /> Software Foundation. If the Program does not specify a version number of<br /> this License, you may choose any version ever published by the Free Software<br /> Foundation.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;10. If you wish to incorporate parts of the Program into other free<br /> programs whose distribution conditions are different, write to the author<br /> to ask for permission. For software which is copyrighted by the Free<br /> Software Foundation, write to the Free Software Foundation; we sometimes<br /> make exceptions for this. Our decision will be guided by the two goals<br /> of preserving the free status of all derivatives of our free software and<br /> of promoting the sharing and reuse of software generally.&lt;/blockquote&gt;<br /> <br /> &lt;center&gt;NO WARRANTY&lt;/center&gt;<br /> <br /> &lt;blockquote&gt;11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY<br /> FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN<br /> OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES<br /> PROVIDE THE PROGRAM &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED<br /> OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF<br /> MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS<br /> TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE<br /> PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,<br /> REPAIR OR CORRECTION.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING<br /> WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR<br /> REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,<br /> INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING<br /> OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED<br /> TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY<br /> YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER<br /> PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE<br /> POSSIBILITY OF SUCH DAMAGES.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;END OF TERMS AND CONDITIONS&lt;/blockquote&gt;<br /> <br /> [[Category:Administrator]]<br /> <br /> [[es:Licencia]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Developer_documentation&diff=6621 2006-02-28T03:29:54Z

<p>Martin: </p> <hr /> <div>==How you can contribute==<br /> <br /> The M in Moodle stands for 'Modular'. There are many different types of components that you can contribute that can be plugged into Moodle to provide additional funtionality. Even if you are not a programmer there are things you can change or help with.<br /> *[[Activity modules]]<br /> *[[Blocks Howto|Blocks]]<br /> *[[Themes]]<br /> *[[Translation|Translations]]<br /> *[[Text filters]]<br /> *[[Resource types]]<br /> *[[Assignment types]]<br /> *[[Question types]]<br /> *[[Question import/export formats]]<br /> *[[Quiz reports]]<br /> *[[Database Schemas|Database schemas]]<br /> *[[Course formats]]<br /> You can also help a lot by<br /> *[[Tests|Testing]]<br /> *[[Bug tracker|Participating in the bug tracker]]<br /> <br /> ==Guides for developers==<br /> *[[Moodle architecture]]<br /> *[[Coding|Coding guidelines]]<br /> *[[Interface guidelines]]<br /> *[[CVS (developer)|Moodle CVS for developers]]<br /> <br /> ==Plans for the future==<br /> Ideas for and details of planned future features of Moodle are initially discussed on the forums in the [http://moodle.org/course/view.php?id=5 Using Moodle] course at moodle.org. That developer discussions are intermixed with user discussions in the same forums may seem strange at first but is one of the reasons for the success of Moodle. It is important that both end-users and developers discuss the future features together.<br /> <br /> Once ideas begin to crystalize on the forums they can be summarized in this wiki, either as part of the [[Roadmap]] or in the form of [[Developer notes]]. These pages then form the basis for further discussion in the forums.<br /> *[[Roadmap]]<br /> *[[Developer notes]]<br /> *[[Developer conference|Developer conferences]]<br /> <br /> ==Documentation for core components==<br /> This section is for documentation of specific components of the existing core Moodle code. Discussion of components that are under discussion or in development can be found in the [[Developer notes]] or on the [[Roadmap]].<br /> <br /> *[[UTF-8 migration|Migration to UTF-8]]<br /> *[[Quiz developer docs|Quiz module]]<br /> *[[SCORM schema|SCORM module 1.5 schema]]<br /> *[[Authentication API]]<br /> *[[Stats package]]<br /> *[[Email processing]]<br /> *[[Cookieless Sessions]]<br /> <br /> ==Documentation for contributed code==<br /> Many Moodle users contribute code for the benefit of other Moodle users. This can take the form of new activity modules, blocks, themes, resource plug-ins, assignment plug-ins, question type plug-ins, question import/export formats, quiz report plug-ins, course formats, ... This code is initially posted on the forums in the [http://moodle.org/course/view.php?id=5 Using Moodle] course and then often go into the [http://cvs.sourceforge.net/viewcvs.py/moodle/contrib/ contrib area] of the Moodle [[CVS]] repository. Developer documentation for these components should be listed here.<br /> <br /> == Developer resources and tools ==<br /> <br /> *[http://moodle.org/bugs/ Moodle bug tracker] - bug reports, feature requests and other tracked issues<br /> *[http://cvs.sourceforge.net/viewcvs.py/moodle/moodle/ CVS code]<br /> *[http://moodle.org/xref/nav.html?index.html Cross reference] - phpxref output for browsing Moodle source code<br /> *[http://moodle.org/mod/resource/view.php?id=1267 Core API]<br /> *[http://moodle.sourceforge.net/dhawes-phpdoc/ Moodle PHP doc reference]<br /> *[[Unmerged files|1.4 and 1.5 un-merged files]]<br /> <br /> ==See also==<br /> *[http://security.moodle.org/ Moodle Security Centre]<br /> *[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services<br /> <br /> [[Category:Developer]]<br /> [[es:Documentación para Desarrolladores]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Tests&diff=6620 2006-02-28T03:29:13Z

<p>Martin: </p> <hr /> <div>* [[Tests/Assignment]]<br /> * [[Tests/Chat]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Developer_documentation&diff=6619 2006-02-28T03:24:41Z

<p>Martin: /* How you can contribute */</p> <hr /> <div>==How you can contribute==<br /> <br /> The M in Moodle stands for 'Modular'. There are many different types of components that you can contribute that can be plugged into Moodle to provide additional funtionality. Even if you are not a programmer there are things you can change or help with.<br /> *[[Activity modules]]<br /> *[[Blocks Howto|Blocks]]<br /> *[[Themes]]<br /> *[[Translation|Translations]]<br /> *[[Text filters]]<br /> *[[Resource types]]<br /> *[[Assignment types]]<br /> *[[Question types]]<br /> *[[Question import/export formats]]<br /> *[[Quiz reports]]<br /> *[[Database Schemas|Database schemas]]<br /> *[[Course formats]]<br /> You can also help a lot by<br /> *[[Testing]]<br /> *[[Bug tracker|Participating in the bug tracker]]<br /> <br /> ==Guides for developers==<br /> *[[Moodle architecture]]<br /> *[[Coding|Coding guidelines]]<br /> *[[Interface guidelines]]<br /> *[[CVS (developer)|Moodle CVS for developers]]<br /> <br /> ==Plans for the future==<br /> Ideas for and details of planned future features of Moodle are initially discussed on the forums in the [http://moodle.org/course/view.php?id=5 Using Moodle] course at moodle.org. That developer discussions are intermixed with user discussions in the same forums may seem strange at first but is one of the reasons for the success of Moodle. It is important that both end-users and developers discuss the future features together.<br /> <br /> Once ideas begin to crystalize on the forums they can be summarized in this wiki, either as part of the [[Roadmap]] or in the form of [[Developer notes]]. These pages then form the basis for further discussion in the forums.<br /> *[[Roadmap]]<br /> *[[Developer notes]]<br /> *[[Developer conference|Developer conferences]]<br /> <br /> ==Documentation for core components==<br /> This section is for documentation of specific components of the existing core Moodle code. Discussion of components that are under discussion or in development can be found in the [[Developer notes]] or on the [[Roadmap]].<br /> <br /> *[[UTF-8 migration|Migration to UTF-8]]<br /> *[[Quiz developer docs|Quiz module]]<br /> *[[SCORM schema|SCORM module 1.5 schema]]<br /> *[[Authentication API]]<br /> *[[Stats package]]<br /> *[[Email processing]]<br /> *[[Cookieless Sessions]]<br /> <br /> ==Documentation for contributed code==<br /> Many Moodle users contribute code for the benefit of other Moodle users. This can take the form of new activity modules, blocks, themes, resource plug-ins, assignment plug-ins, question type plug-ins, question import/export formats, quiz report plug-ins, course formats, ... This code is initially posted on the forums in the [http://moodle.org/course/view.php?id=5 Using Moodle] course and then often go into the [http://cvs.sourceforge.net/viewcvs.py/moodle/contrib/ contrib area] of the Moodle [[CVS]] repository. Developer documentation for these components should be listed here.<br /> <br /> == Developer resources and tools ==<br /> <br /> *[http://moodle.org/bugs/ Moodle bug tracker] - bug reports, feature requests and other tracked issues<br /> *[http://cvs.sourceforge.net/viewcvs.py/moodle/moodle/ CVS code]<br /> *[http://moodle.org/xref/nav.html?index.html Cross reference] - phpxref output for browsing Moodle source code<br /> *[http://moodle.org/mod/resource/view.php?id=1267 Core API]<br /> *[http://moodle.sourceforge.net/dhawes-phpdoc/ Moodle PHP doc reference]<br /> *[[Unmerged files|1.4 and 1.5 un-merged files]]<br /> <br /> ==See also==<br /> *[http://security.moodle.org/ Moodle Security Centre]<br /> *[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services<br /> <br /> [[Category:Developer]]<br /> [[es:Documentación para Desarrolladores]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=MediaWiki:Sidebar&diff=5285 2006-02-13T16:46:38Z

<p>Martin: </p> <hr /> <div>* Navigation<br /> ** mainpage|mainpage<br /> ** recentchanges-url|recentchanges<br /> ** helppage|help<br /> <br /> * Documentation<br /> ** About Moodle|About Moodle<br /> ** Teacher documentation|Teacher<br /> ** Administrator documentation|Administrator<br /> ** Developer documentation|Developer<br /> ** Martin Testing</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Blocks&diff=5141 2006-02-11T04:24:21Z

<p>Martin: First version, pasted from original html page, needs cleaning up still</p> <hr /> <div>(Needs cleaning up - I only did the first page or so.)<br /> <br /> Original Author: Jon Papaioannou (pj@uom.gr)<br /> <br /> A Step-by-step Guide To Creating Blocks<br /> <br /> 1. Summary<br /> <br /> The present document serves as a guide to developers who want to create their own blocks for use in Moodle. It applies to the 1.5 development version of Moodle (and any newer) only, as the blocks subsystem was rewritten and expanded for the 1.5 release. However, you can also find it useful if you want to modify blocks written for Moodle 1.3 and 1.4 to work with the latest versions (look at Appendix B).<br /> <br /> The guide is written as an interactive course which aims to develop a configurable, multi-purpose block that displays arbitrary HTML. It's targeted mainly at people with little experience with Moodle or programming in general and aims to show how easy it is to create new blocks for Moodle. A certain small amount of PHP programming knowledge is still required, though. Experienced developers and those who just want a reference text should refer to Appendix A because the main guide has a rather low concentration of pure information in the text.<br /> <br /> 2. Basic Concepts<br /> <br /> Through this guide, we will be following the creation of an &quot;HTML&quot; block from scratch in order to demonstrate most of the block features at our disposal. Our block will be named &quot;SimpleHTML&quot;. This does not constrain us regarding the name of the actual directory on the server where the files for our block will be stored, but for consistency we will follow the practice of using the lowercased form &quot;simplehtml&quot; in any case where such a name is required. Whenever we refer to a file or directory name which contains &quot;simplehtml&quot;, it's important to remember that only the &quot;simplehtml&quot; part is up to us to change; the rest is standardized and essential for Moodle to work correctly.<br /> <br /> Whenever a file's path is mentioned in this guide, it will always start with a slash. This refers to the Moodle home directory; all files and directories will be referred to with respect to that directory.<br /> <br /> 3. Ready, Set, Go!<br /> <br /> To define a &quot;block&quot; in Moodle, in the most basic case we need to provide just one source code file. We start by creating the directory /blocks/simplehtml/ and creating a file named /blocks/simplehtml/block_simplehtml.php which will hold our code. We then begin coding the block:<br /> <br /> class block_simplehtml extends block_base {<br /> function init() {<br /> $this-&gt;title = get_string('simplehtml', 'block_simplehtml');<br /> $this-&gt;version = 2004111200;<br /> }<br /> }<br /> <br /> The first line is our block class definition; it must be named exactly in the manner shown. Again, only the &quot;simplehtml&quot; part can (and indeed must) change; everything else is standardized.<br /> <br /> Our class is then given a small method: init. This is essential for all blocks, and its purpose is to set the two class member variables listed inside it. But what do these values actually mean? Here's a more detailed description.<br /> <br /> $this-&gt;title is the title displayed in the header of our block. We can set it to whatever we like; in this case it's set to read the actual title from a language file we are presumably distributing together with the block. I 'll skip ahead a bit here and say that if you want your block to display no title at all, then you should set this to any descriptive value you want (but not make it an empty string). We will later see how to disable the title's display.<br /> <br /> $this-&gt;version is the version of our block. This actually would only make a difference if your block wanted to keep its own data in special tables in the database (i.e. for very complex blocks). In that case the version number is used exactly as it's used in activities; an upgrade script uses it to incrementally upgrade an &quot;old&quot; version of the block's data to the latest. We will outline this process further ahead, since blocks tend to be relatively simple and not hold their own private data. In our example, this is certainly the case so we just set $this-&gt;version to YYYYMMDD00 and forget about it.<br /> <br /> UPDATING: Prior to version 1.5, the basic structure of each block class was slightly different. Refer to Appendix B for more information on the changes that old blocks have to make to conform to the new standard.<br /> <br /> <br /> 4. I Just Hear Static<br /> <br /> In order to get our block to actually display something on screen, we need to add one more method to our class (before the final closing brace in our file). The new code is:<br /> <br /> function get_content() {<br /> if ($this-&gt;content !== NULL) {<br /> return $this-&gt;content;<br /> }<br /> <br /> $this-&gt;content = new stdClass;<br /> $this-&gt;content-&gt;text = 'The content of our SimpleHTML block!';<br /> $this-&gt;content-&gt;footer = 'Footer here...';<br /> <br /> return $this-&gt;content;<br /> }<br /> <br /> <br /> It can't get any simpler than that, can it? Let's dissect this method to see what's going on...<br /> <br /> First of all, there is a check that returns the current value of $this-&gt;content if it's not NULL; otherwise we proceed with &quot;computing&quot; it. Since the computation is potentially a time-consuming operation and it will be called several times for each block (Moodle works that way internally), we take a precaution and include this time-saver.<br /> <br /> Supposing the content had not been computed before (it was NULL), we then define it from scratch. The code speaks for itself there, so there isn't much to say. Just keep in mind that we can use HTML both in the text and in the footer, if we want to.<br /> <br /> At this point our block should be capable of being automatically installed in Moodle and added to courses; visit your administration page to install it and after seeing it in action come back to continue our tutorial.<br /> <br /> <br /> 5. Configure That Out<br /> <br /> The current version of our block doesn't really do much; it just displays a fixed message, which is not very useful. What we 'd really like to do is allow the teachers to customize what goes into the block. This, in block-speak, is called &quot;instance configuration&quot;. So let's give our block some instance configuration...<br /> <br /> First of all, we need to tell Moodle that we want it to provide instance-specific configuration amenities to our block. That's as simple as adding one more method to our block class:<br /> <br /> function instance_allow_config() {<br /> return true;<br /> }<br /> <br /> This small change is enough to make Moodle display an &quot;Edit...&quot; icon in our block's header when we turn editing mode on in any course. However, if you try to click on that icon you will be presented with a notice that complains about the block's configuration not being implemented correctly. Try it, it's harmless.<br /> <br /> Moodle's complaints do make sense. We told it that we want to have configuration, but we didn't say what kind of configuration we want, or how it should be displayed. To do that, we need to create one more file: /blocks/simplehtml/config_instance.html (which has to be named exactly like that). For the moment, copy paste the following into it and save:<br /> <br /> &lt;table cellpadding=&quot;9&quot; cellspacing=&quot;0&quot;&gt;<br /> &lt;tr valign=&quot;top&quot;&gt;<br /> &lt;td align=&quot;right&quot;&gt;<br /> &lt;?php print_string('configcontent', 'block_simplehtml'); ?&gt;:<br /> &lt;/td&gt;<br /> &lt;td&gt;<br /> &lt;?php print_textarea(true, 10, 50, 0, 0, 'text', $this-&gt;config-&gt;text); ?&gt;<br /> &lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td colspan=&quot;2&quot; align=&quot;center&quot;&gt;<br /> &lt;input type=&quot;submit&quot; value=&quot;&lt;?php print_string('savechanges') ?&gt;&quot; /&gt;<br /> &lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> &lt;?php use_html_editor(); ?&gt;<br /> <br /> It isn't difficult to see that the above code just provides us with a wysiwyg-editor-enabled textarea to write our block's desired content in and a submit button to save. But... what's $this-&gt;config-&gt;text? Well...<br /> <br /> Moodle goes a long way to make things easier for block developers. Did you notice that the textarea is actually named &quot;text&quot;? When the submit button is pressed, Moodle saves each and every field it can find in our config_instance.html file as instance configuration data. We can then access that data as $this-&gt;config-&gt;variablename, where variablename is the actual name we used for our field; in this case, &quot;text&quot;. So in essence, the above form just pre-populates the textarea with the current content of the block (as indeed it should) and then allows us to change it.<br /> <br /> You also might be surprised by the presence of a submit button and the absence of any &lt;form&gt; element at the same time. But the truth is, we don't need to worry about that at all; Moodle goes a really long way to make things easier for developers! We just print the configuration options we want, in any format we want; include a submit button, and Moodle will handle all the rest itself. The instance configuration variables are automatically at our disposal to access from any of the class methods except init.<br /> <br /> In the event where the default behavior is not satisfactory, we can still override it. However, this requires advanced modifications to our block class and will not be covered here; refer to Appendix A for more details.<br /> <br /> Having now the ability to refer to this instance configuration data through $this-&gt;config, the final twist is to tell our block to actually display what is saved in is configuration data. To do that, find this snippet in /blocks/simplehtml/block_simplehtml.php:<br /> <br /> $this-&gt;content = new stdClass;<br /> $this-&gt;content-&gt;text = 'The content of our SimpleHTML block!';<br /> $this-&gt;content-&gt;footer = 'Footer here...';<br /> <br /> and change it to:<br /> <br /> $this-&gt;content = new stdClass;<br /> $this-&gt;content-&gt;text = $this-&gt;config-&gt;text;<br /> $this-&gt;content-&gt;footer = 'Footer here...';<br /> <br /> Oh, and since the footer isn't really exciting at this point, we remove it from our block because it doesn't contribute anything. We could just as easily have decided to make the footer configurable in the above way, too. So for our latest code, the snippet becomes:<br /> <br /> $this-&gt;content = new stdClass;<br /> $this-&gt;content-&gt;text = $this-&gt;config-&gt;text;<br /> $this-&gt;content-&gt;footer = '';<br /> <br /> After this discussion, our block is ready for prime time! Indeed, if you now visit any course with a SimpleHTML block, you will see that modifying its contents is now a snap.<br /> 6.<br /> The Specialists<br /> <br /> Implementing instance configuration for the block's contents was good enough to whet our apetite, but who wants to stop there? Why not customize the block's title, too?<br /> <br /> Why not, indeed. Well, our first attempt to achieve this is natural enough: let's add another field to /blocks/simplehtml/config_instance.html. Here goes:<br /> <br /> &lt;tr valign=&quot;top&quot;&gt;<br /> &lt;td align=&quot;right&quot;&gt;&lt;p&gt;&lt;?php print_string('configtitle', 'block_simplehtml'); ?&gt;:&lt;/td&gt;<br /> &lt;td&gt;&lt;input type=&quot;text&quot; name=&quot;title&quot; size=&quot;30&quot; value=&quot;&lt;?php echo $this-&gt;config-&gt;title; ?&gt;&quot; /&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> <br /> We save the edited file, go to a course, edit the title of the block and... nothing happens! The instance configuration is saved correctly, all right (editing it once more proves that) but it's not being displayed. All we get is just the simple &quot;SimpleHTML&quot; title.<br /> <br /> That's not too wierd, if we think back a bit. Do you remember that init method, where we set $this-&gt;title? We didn't actually change its value from then, and $this-&gt;title is definitely not the same as $this-&gt;config-&gt;title (to Moodle, at least). What we need is a way to update $this-&gt;title with the value in the instance configuration. But as we said a bit earlier, we can use $this-&gt;config in all methods except init! So what can we do?<br /> <br /> Let's pull out another ace from our sleeve, and add this small method to our block class:<br /> <br /> function specialization() {<br /> $this-&gt;title = $this-&gt;config-&gt;title;<br /> }<br /> <br /> Aha, here's what we wanted to do all along! But what's going on with the specialization method?<br /> <br /> This &quot;magic&quot; method has actually a very nice property: it's guaranteed to be automatically called by Moodle as soon as our instance configuration is loaded and available (that is, immediately after init is called). That means before the block's content is computed for the first time, and indeed before anything else is done with the block. Thus, providing a specialization method is the natural choice for any configuration data that needs to be acted upon &quot;as soon as possible&quot;, as in this case.<br /> 7.<br /> Now You See Me, Now You Don't<br /> <br /> Now would be a good time to mention another nifty technique that can be used in blocks, and which comes in handy quite often. Specifically, it may be the case that our block will have something interesting to display some of the time; but in some other cases, it won't have anything useful to say. (An example here would be the &quot;Recent Activity&quot; block, in the case where no recent activity in fact exists. However in that case the block chooses to explicitly inform you of the lack of said activity, which is arguably useful). It would be nice, then, to be able to have our block &quot;disappear&quot; if it's not needed to display it.<br /> <br /> This is indeed possible, and the way to do it is to make sure that after the get_content method is called, the block is completely void of content. Specifically, &quot;void of content&quot; means that both $this-&gt;content-&gt;text and $this-&gt;content-&gt;footer are each equal to the empty string (''). Moodle performs this check by calling the block's is_empty() method, and if the block is indeed empty then it is not displayed at all.<br /> <br /> Note that the exact value of the block's title and the presence or absence of a hide_header method do not affect this behavior. A block is considered empty if it has no content, irrespective of anything else.<br /> 8.<br /> We Are Legion<br /> <br /> Right now our block is fully configurable, both in title and content. It's so versatile, in fact, that we could make pretty much anything out of it. It would be really nice to be able to add multiple blocks of this type to a single course. And, as you might have guessed, doing that is as simple as adding another small method to our block class:<br /> <br /> function instance_allow_multiple() {<br /> return true;<br /> }<br /> <br /> This tells Moodle that it should allow any number of instances of the SimpleHTML block in any course. After saving the changes to our file, Moodle immediately allows us to add multiple copies of the block without further ado!<br /> <br /> There are a couple more of interesting points to note here. First of all, even if a block itself allows multiple instances in the same page, the administrator still has the option of disallowing such behavior. This setting can be set separately for each block from the Administration / Configuration / Blocks page.<br /> <br /> And finally, a nice detail is that as soon as we defined an instance_allow_multiple method, the method instance_allow_config that was already defined became obsolete. Moodle assumes that if a block allows multiple instances of itself, those instances will want to be configured (what is the point of same multiple instances in the same page if they are identical?) and thus automatically provides an &quot;Edit&quot; icon. So, we can also remove the whole instance_allow_config method now without harm. We had only needed it when multiple instances of the block were not allowed.<br /> 9.<br /> The Effects of Globalization<br /> <br /> Configuring each block instance with its own personal data is cool enough, but sometimes administrators need some way to &quot;touch&quot; all instances of a specific block at the same time. In the case of our SimpleHTML block, a few settings that would make sense to apply to all instances aren't that hard to come up with. For example, we might want to limit the contents of each block to only so many characters, or we might have a setting that filters HTML out of the block's contents, only allowing pure text in. Granted, such a feature wouldn't win us any awards for naming our block &quot;SimpleHTML&quot; but some tormented administrator somewhere might actually find it useful.<br /> <br /> This kind of configuration is called &quot;global configuration&quot; and applies only to a specific block type (all instances of that block type are affected, however). Implementing such configuration for our block is quite similar to implementing the instance configuration. We will now see how to implement the second example, having a setting that only allows text and not HTML in the block's contents.<br /> <br /> First of all, we need to tell Moodle that we want our block to provide global configuration by, what a surprise, adding a small method to our block class:<br /> <br /> function has_config() {<br /> return true;<br /> }<br /> <br /> Then, we need to create a HTML file that actually prints out the configuration screen. In our case, we 'll just print out a checkbox saying &quot;Do not allow HTML in the content&quot; and a &quot;submit&quot; button. Let's create the file /blocks/simplehtml/config_global.html which again must be named just so, and copy paste the following into it:<br /> <br /> &lt;div style=&quot;text-align: center;&quot;&gt;<br /> &lt;input type=&quot;hidden&quot; name=&quot;block_simplehtml_strict&quot; value=&quot;0&quot; /&gt;<br /> &lt;input type=&quot;checkbox&quot; name=&quot;block_simplehtml_strict&quot; value=&quot;1&quot; <br /> &lt;?php if(!empty($CFG-&gt;block_simplehtml_strict)) echo 'checked=&quot;checked&quot;'; ?&gt; /&gt;<br /> &lt;?php print_string('donotallowhtml', 'block_simplehtml'); ?&gt;<br /> &lt;p&gt;&lt;input type=&quot;submit&quot; value=&quot;&lt;?php print_string('savechanges'); ?&gt;&quot; /&gt;&lt;/p&gt;<br /> &lt;/div&gt;<br /> <br /> True to our block's name, this looks simple enough. What it does is that it displays a checkbox named &quot;block_simplehtml_strict&quot; and if the Moodle configuration variable with the same name (i.e., $CFG-&gt;block_simplehtml_strict) is set and not empty (that means it's not equal to an empty string, to zero, or to boolean false) it displays the box as pre-checked (reflecting the current status). Why does it check the configuration setting with the same name? Because the default implementation of the global configuration saving code takes all the variables we have in our form and saves them as Moodle configuration options with the same name. Thus, it's good practice to use a descriptive name and also one that won't possibly conflict with the name of another setting. &quot;block_simplehtml_strict&quot; clearly satisfies both requirements.<br /> <br /> The astute reader may have noticed that we actually have two input fields named &quot;block_simplehtml_strict&quot; in our configuration file. One is hidden and its value is always 0; the other is the checkbox and its value is 1. What gives? Why have them both there?<br /> <br /> Actually, this is a small trick we use to make our job as simple as possible. HTML forms work this way: if a checkbox in a form is not checked, its name does not appear at all in the variables passed to PHP when the form is submitted. That effectively means that, when we uncheck the box and click submit, the variable is not passed to PHP at all. Thus, PHP does not know to update its value to &quot;0&quot;, and our &quot;strict&quot; setting cannot be turned off at all once we turn it on for the first time. Not the behavior we want, surely.<br /> <br /> However, when PHP handles received variables from a form, the variables are processed in the order in which they appear in the form. If a variable comes up having the same name with an already-processed variable, the new value overwrites the old one. Taking advantage of this, our logic runs as follows: the variable &quot;block_simplehtml_strict&quot; is first unconditionally set to &quot;0&quot;. Then, if the box is checked, it is set to &quot;1&quot;, overwriting the previous value as discussed. The net result is that our configuration setting behaves as it should.<br /> <br /> To round our bag of tricks up, notice that the use of if(!empty($CFG-&gt;block_simplehtml_strict)) in the test for &quot;should the box be checked by default?&quot; is quite deliberate. The first time this script runs, the variable $CFG-&gt;block_simplehtml_strict will not exist at all. After it's set for the first time, its value can be either &quot;0&quot; or &quot;1&quot;. Given that both &quot;not set&quot; and the string &quot;0&quot; evaluate as empty while the sting &quot;1&quot; does not, we manage to avoid any warnings from PHP regarding the variable not being set at all, and have a nice human-readable representation for its two possible values (&quot;0&quot; and &quot;1&quot;).<br /> <br /> Now that we have managed to cram a respectable amount of tricks into a few lines of HTML, we might as well discuss the alternative in case that tricks are not enough for a specific configuration setup we have in mind. Saving the data is done in the method config_save, the default implementation of which is as follows:<br /> <br /> function config_save($data) {<br /> // Default behavior: save all variables as $CFG properties<br /> foreach ($data as $name =&gt; $value) {<br /> set_config($name, $value);<br /> }<br /> return true;<br /> }<br /> <br /> As can be clearly seen, Moodle passes this method an associative array $data which contains all the variables coming in from our configuration screen. If we wanted to do the job without the &quot;hidden variable with the same name&quot; trick we used above, one way to do it would be by overriding this method with the following:<br /> <br /> function config_save($data) {<br /> if(isset($data['block_simplehtml_strict'])) {<br /> set_config('block_simplehtml_strict', '1');<br /> }<br /> else {<br /> set_config('block_simplehtml_strict', '0');<br /> }<br /> return true;<br /> }<br /> <br /> Quite straightfoward: if the variable &quot;block_simplehtml_strict&quot; is passed to us, then it can only mean that the user has checked it, so set the configuration variable with the same name to &quot;1&quot;. Otherwise, set it to &quot;0&quot;. Of course, this version would need to be updated if we add more configuration options because it doesn't respond to them as the default implementation does. Still, it's useful to know how we can override the default implementation if it does not fit our needs (for example, we might not want to save the variable as part of the Moodle configuration but do something else with it).<br /> <br /> So, we are now at the point where we know if the block should allow HTML tags in its content or not. How do we get the block to actually respect that setting?<br /> <br /> We could decide to do one of two things: either have the block &quot;clean&quot; HTML out from the input before saving it in the instance configuration and then display it as-is (the &quot;eager&quot; approach); or have it save the data &quot;as is&quot; and then clean it up each time just before displaying it (the &quot;lazy&quot; approach). The eager approach involves doing work once when saving the configuration; the lazy approach means doing work each time the block is displayed and thus it promises to be worse performance-wise. We shall hence go with the eager approach.<br /> <br /> Much as we did just before with overriding config_save, what is needed here is overriding the method instance_config_save which handles the instance configuration. The default implementation is as follows:<br /> <br /> function instance_config_save($data) {<br /> $data = stripslashes_recursive($data);<br /> $this-&gt;config = $data;<br /> return set_field('block_instance', 'configdata', base64_encode(serialize($data)), <br /> 'id', $this-&gt;instance-&gt;id);<br /> }<br /> <br /> This may look intimidating at first (what's all this stripslashes_recursive() and base64_encode() and serialize() stuff?) but do not despair; we won't have to touch any of it. We will only add some extra validation code in the beginning and then instruct Moodle to additionally call this default implementation to do the actual storing of the data. Specifically, we will add a method to our class which goes like this:<br /> <br /> function instance_config_save($data) {<br /> // Clean the data if we have to<br /> global $CFG;<br /> if(!empty($CFG-&gt;block_simplehtml_strict)) {<br /> $data['text'] = strip_tags($data['text']);<br /> }<br /> <br /> // And now forward to the default implementation defined in the parent class<br /> return parent::instance_config_save($data);<br /> }<br /> <br /> At last! Now the administrator has absolute power of life and death over what type of content is allowed in our &quot;SimpleHTML&quot; block! Absolute? Well... not exactly. In fact, if we think about it for a while, it will become apparent that if at some point in time HTML is allowed and some blocks have saved their content with HTML included, and afterwards the administrator changes the setting to &quot;off&quot;, this will only prevent subsequent content changes from including HTML. Blocks which already had HTML in their content would continue to display it!<br /> <br /> Following that train of thought, the next stop is realizing that we wouldn't have this problem if we had chosen the lazy approach a while back, because in that case we would &quot;sanitize&quot; each block's content just before it was displayed. The only thing we can do with the eager approach is strip all the tags from the content of all SimpleHTML instances as soon as the admin setting is changed to &quot;HTML off&quot;; but even then, turning the setting back to &quot;HTML on&quot; won't bring back the tags we stripped away. On the other hand, the lazy approach might be slower, but it's more versatile; we can choose whether to strip or keep the HTML before displaying the content, and we won't lose it at all if the admin toggles the setting off and on again. Isn't the life of a developer simple and wonderful?<br /> <br /> We will let this part of the tutorial come to a close with the obligatory excercise for the reader: in order to have the SimpleHTML block work &quot;correctly&quot;, find out how to strengthen the eager approach to strip out all tags from the existing configuration of all instances of our block, or go back and implement the lazy approach instead. (Hint: do that in the get_content method)<br /> <br /> UPDATING: Prior to version 1.5, the file config_global.html was named simply config.html. Also, the methods config_save and config_print were named handle_config and print_config respectively. Upgrading a block to work with Moodle 1.5 involves updating these aspects; refer to Appendix B for more information.<br /> 10.<br /> Eye Candy<br /> <br /> Our block is just about complete functionally, so now let's take a look at some of the tricks we can use to make its behavior customized in a few more useful ways.<br /> <br /> First of all, there are a couple of ways we can adjust the visual aspects of our block. For starters, it might be useful to create a block that doesn't display a header (title) at all. You can see this effect in action in the Course Description block that comes with Moodle. This behavior is achieved by, you guessed it, adding one more method to our block class:<br /> <br /> function hide_header() {<br /> return true;<br /> }<br /> <br /> One more note here: we cannot just set an empty title inside the block's init method; it's necessary for each block to have a unique, non-empty title after init is called so that Moodle can use those titles to differentiate between all of the installed blocks.<br /> <br /> Another adjustment we might want to do is instruct our block to take up a certain amount of width on screen. Moodle handles this as a two-part process: first, it queries each block about its preferred width and takes the maximum number as the desired value. Then, the page that's being displayed can choose to use this value or, more probably, bring it within some specific range of values if it isn't already. That means that the width setting is a best-effort settlement; your block can request a certain width and Moodle will try to provide it, but there's no guarantee whatsoever about the end result. As a concrete example, all standard Moodle course formats will deliver any requested width between 180 and 210 pixels, inclusive.<br /> <br /> To instruct Moodle about our block's preferred width, we add one more method to the block class:<br /> <br /> function preferred_width() {<br /> // The preferred value is in pixels<br /> return 200;<br /> }<br /> <br /> This will make our block (and all the other blocks displayed at the same side of the page) a bit wider than standard.<br /> <br /> Finally, we can also affect some properties of the actual HTML that will be used to print our block. Each block is fully contained within a &lt;table&gt; element, inside which all the HTML for that block is printed. We can instruct Moodle to add HTML attributes with specific values to that container. This would be done to either a) directly affect the end result (if we say, assign bgcolor=&quot;black&quot;), or b) give us freedom to customize the end result using CSS (this is in fact done by default as we 'll see below).<br /> <br /> The default behavior of this feature in our case will assign to our block's container the class HTML attribute with the value &quot;sideblock block_simplehtml&quot; (the prefix &quot;block_&quot; followed by the name of our block, lowercased). We can then use that class to make CSS selectors in our theme to alter this block's visual style (for example, &quot;.sideblock.block_simplehtml { border: 1px black solid}&quot;).<br /> <br /> To change the default behavior, we will need to define a method which returns an associative array of attribute names and values. For example, the version<br /> <br /> function html_attributes() {<br /> return array(<br /> 'class' =&gt; 'sideblock block_'. $this-&gt;name(),<br /> 'onmouseover' =&gt; 'alert(&quot;Mouseover on our block!&quot;);'<br /> );<br /> }<br /> <br /> will result in a mouseover event being added to our block using JavaScript, just as if we had written the onmouseover=&quot;alert(...)&quot; part ourselves in HTML. Note that we actually duplicate the part which sets the class attribute (we want to keep that, and since we override the default behavior it's our responsibility to emulate it if required). And the final elegant touch is that we don't set the class to the hard-coded value &quot;block_simplehtml&quot; but instead use the name method to make it dynamically match our block's name.<br /> 11.<br /> Authorized Personnel Only<br /> <br /> It's not difficult to imagine a block which is very useful in some circumstances but it simply cannot be made meaningful in others. An example of this would be the &quot;Social Activities&quot; block which is indeed useful in a course with the social format, but doesn't do anything useful in a course with the weeks format. There should be some way of allowing the use of such blocks only where they are indeed meaningful, and not letting them confuse users if they are not.<br /> <br /> Moodle allows us to declare which course formats each block is allowed to be displayed in, and enforces these restrictions as set by the block developers at all times. The information is given to Moodle as a standard associative array, with each key corresponding to a page format and defining a boolean value (true/false) that declares whether the block should be allowed to appear in that page format.<br /> <br /> Notice the deliberate use of the term page instead of course in the above paragraph. This is because in Moodle 1.5 and onwards, blocks can be displayed in any page that supports them. The best example of such pages are the course pages, but we are not restricted to them. For instance, the quiz view page (the first one we see when we click on the name of the quiz) also supports blocks.<br /> <br /> The format names we can use for the pages derive from the name of the script which is actually used to display that page. For example, when we are looking at a course, the script is /course/view.php (this is evident from the browser's address line). Thus, the format name of that page is course-view. It follows easily that the format name for a quiz view page is mod-quiz-view. This rule of thumb does have a few exceptions, however:<br /> * The format name for the front page of Moodle is site-index.<br /> * The format name for courses is actually not just course-view; it is course-view-weeks, course-view-topics, etc.<br /> * Even though there is no such page, the format name all can be used as a catch-all option.<br /> <br /> We can include as many format names as we want in our definition of the applicable formats. Each format can be allowed or disallowed, and there are also three more rules that help resolve the question &quot;is this block allowed into this page or not?&quot;:<br /> * Prefixes of a format name will match that format name; for example, mod will match all the activity modules. course-view will match any course, regardless of the course format. And finally, site will also match the front page (remember that its full format name is site-index).<br /> * The more specialized a format name that matches our page is, the higher precedence it has when deciding if the block will be allowed. For example, mod, mod-quiz and mod-quiz-view all match the quiz view page. But if all three are present, mod-quiz-view will take precedence over the other two because it is a better match.<br /> * The character * can be used in place of any word. For example, mod and mod-* are equivalent. At the time of this document's writing, there is no actual reason to utilize this &quot;wildcard matching&quot; feature, but it exists for future usage.<br /> * The order that the format names appear does not make any difference.<br /> <br /> All of the above are enough to make the situation sound complex, so let's look at some specific examples. First of all, to have our block appear only in the site front page, we would use:<br /> <br /> function applicable_formats() {<br /> return array('site' =&gt; true);<br /> }<br /> <br /> Since all is missing, the block is disallowed from appearing in any course format; but then site is set to true, so it's explicitly allowed to appear in the site front page (remember that site matches site-index because it's a prefix).<br /> <br /> For another example, if we wanted to allow the block to appear in all course formats except social, and also to not be allowed anywhere but in courses, we would use:<br /> <br /> function applicable_formats() {<br /> return array('course-view' =&gt; true, 'course-view-social' =&gt; false);<br /> }<br /> <br /> This time, we first allow the block to appear in all courses and then we explicitly disallow the social format.<br /> <br /> For our final, most complicated example, suppose that a block can be displayed in the site front page, in courses (but not social courses) and also when we are viewing any activity module, except quiz. This would be:<br /> <br /> function applicable_formats() {<br /> return array('site-index' =&gt; true,<br /> 'course-view' =&gt; true, 'course-view-social' =&gt; false,<br /> 'mod' =&gt; true, 'mod-quiz' =&gt; false);<br /> }<br /> <br /> It is not difficult to realize that the above accomplishes the objective if we remember that there is a &quot;best match&quot; policy to determine the end result.<br /> <br /> UPDATING: Prior to version 1.5, blocks were only allowed in courses (and in Moodle 1.4, in the site front page). Also, the keywords used to describe the valid course formats at the time were slightly different and had to be changed in order to allow for a more open architecture. Refer to Appendix B for more information on the changes that old blocks have to make to conform to the new standard.<br /> 12.<br /> Lists and Icons<br /> <br /> In this final part of the guide we will briefly discuss an additional capability of Moodle's block system, namely the ability to very easily create blocks that display a list of choices to the user. This list is displayed with one item per line, and an optional image (icon) next to the item. An example of such a list block is the standard Moodle &quot;admin&quot; block, which illustrates all the points discussed in this section.<br /> <br /> As we have seen so far, blocks of use two properties of $this-&gt;content: &quot;text&quot; and &quot;footer&quot;. The text is displayed as-is as the block content, and the footer is displayed below the content in a smaller font size. List blocks use $this-&gt;content-&gt;footer in the exact same way, but they ignore $this-&gt;content-&gt;text.<br /> <br /> Instead, Moodle expects such blocks to set two other properties when the get_content method is called: $this-&gt;content-&gt;items and $this-&gt;content-&gt;icons. $this-&gt;content-&gt;items should be a numerically indexed array containing elements that represent the HTML for each item in the list that is going to be displayed. Usually these items will be HTML anchor tags which provide links to some page. $this-&gt;content-&gt;icons should also be a numerically indexed array, with exactly as many items as $this-&gt;content-&gt;items has. Each of these items should be a fully qualified HTML &lt;img&gt; tag, with &quot;src&quot;, &quot;height&quot;, &quot;width&quot; and &quot;alt&quot; attributes. Obviously, it makes sense to keep the images small and of a uniform size.<br /> <br /> In order to tell Moodle that we want to have a list block instead of the standard text block, we need to make a small change to our block class declaration. Instead of extending class block_base, our block will extend class block_list. For example:<br /> <br /> class block_my_menu extends block_list {<br /> // The init() method does not need to change at all<br /> }<br /> <br /> In addition to making this change, we must of course also modify the get_content method to construct the $this-&gt;content variable as discussed above:<br /> <br /> function get_content() {<br /> if ($this-&gt;content !== NULL) {<br /> return $this-&gt;content;<br /> }<br /> <br /> $this-&gt;content = new stdClass;<br /> $this-&gt;content-&gt;items = array();<br /> $this-&gt;content-&gt;icons = array();<br /> $this-&gt;content-&gt;footer = 'Footer here...';<br /> <br /> $this-&gt;content-&gt;items[] = '&lt;a href=&quot;some_file.php&quot;&gt;Menu Option 1&lt;/a&gt;';<br /> $this-&gt;content-&gt;icons[] = '&lt;img src=&quot;images/icons/1.gif&quot; width=&quot;16&quot; height=&quot;16&quot; alt=&quot;&quot; /&gt;';<br /> <br /> // Add more list items here<br /> <br /> return $this-&gt;content;<br /> }<br /> <br /> To summarize, if we want to create a list block instead of a text block, we just need to change the block class declaration and the get_content method. Adding the mandatory init method as discussed earlier will then give us our first list block in no time!<br /> <br /> Appendix A: Reference<br /> <br /> This Appendix will discuss the base class block_base from which all other block classes derive, and present each and every method that can be overridden by block developers in detail. Methods that should not be overridden are explicitly referred to as such. After reading this Appendix, you will have a clear understanding of every method which you should or could override to implement functionality for your block.<br /> <br /> The methods are divided into three categories: those you may use and override in your block, those that you may not override but might want to use, and those internal methods that should neither be used nor overridden. In each category, methods are presented in alphabetical order.<br /> <br /> *<br /> Methods you can freely use and override:<br /> o<br /> applicable_formats<br /> <br /> function applicable_formats() {<br /> // Default case: the block can be used in courses and site index, but not in activities<br /> return array('all' =&gt; true, 'mod' =&gt; false);<br /> }<br /> <br /> This method allows you to control which pages your block can be added to. Page formats are formulated from the full path of the script that is used to display that page. You should return an array with the keys being page format names and the values being booleans (true or false). Your block is only allowed to appear in those formats where the value is true.<br /> <br /> Example format names are: course-view, site-index (this is an exception, referring front page of the Moodle site), course-format-weeks (referring to a specific course format), mod-quiz (referring to the quiz module) and all (this will be used for those formats you have not explicitly allowed or disallowed).<br /> <br /> The full matching rules are:<br /> + Prefixes of a format name will match that format name; for example, mod will match all the activity modules. course-view will match any course, regardless of the course format. And finally, site will also match the front page (remember that its full format name is site-index).<br /> + The more specialized a format name that matches our page is, the higher precedence it has when deciding if the block will be allowed. For example, mod, mod-quiz and mod-quiz-view all match the quiz view page. But if all three are present, mod-quiz-view will take precedence over the other two because it is a better match.<br /> + The character * can be used in place of any word. For example, mod and mod-* are equivalent. At the time of this document's writing, there is no actual reason to utilize this &quot;wildcard matching&quot; feature, but it exists for future usage.<br /> + The order that the format names appear does not make any difference.<br /> <br /> o<br /> config_print<br /> <br /> function config_print() {<br /> // Default behavior: print the config_global.html file<br /> // You don't need to override this if you're satisfied with the above<br /> if (!$this-&gt;has_config()) {<br /> return false;<br /> }<br /> global $CFG, $THEME;<br /> print_simple_box_start('center', '', $THEME-&gt;cellheading);<br /> include($CFG-&gt;dirroot.'/blocks/'. $this-&gt;name() .'/config_global.html');<br /> print_simple_box_end();<br /> return true;<br /> }<br /> <br /> This method allows you to choose how to display the global configuration screen for your block. This is the screen that the administrator is presented with when he chooses &quot;Settings...&quot; for a specific block. Override it if you need something much more complex than the default implementation allows you to do. However, keep these points in mind:<br /> 1. If you save your configuration options in $CFG, you will probably need to use global $CFG; before including any HTML configuration screens.<br /> 2. The HTML &lt;input&gt; elements that you include in your method's output will be automatically enclosed in a &lt;form&gt; element. You do not need to worry about where and how that form is submitted; however, you must provide a way to submit it (i.e., an &lt;input type=&quot;submit&quot; /&gt;.<br /> <br /> You should return a boolean value denoting the success or failure of your method's actions.<br /> o<br /> config_save<br /> <br /> function config_save($data) {<br /> // Default behavior: save all variables as $CFG properties<br /> // You don't need to override this if you 're satisfied with the above<br /> foreach ($data as $name =&gt; $value) {<br /> set_config($name, $value);<br /> }<br /> return true;<br /> }<br /> <br /> This method allows you to override the storage mechanism for your global configuration data. The received argument is an associative array, with the keys being setting names and the values being setting values. The default implementation saves everything as Moodle $CFG variables.<br /> <br /> Note that $data does not hold all of the submitted POST data because Moodle adds some hidden fields to the form in order to be able to process it. However, before calling this method it strips the hidden fields from the received data and so when this method is called only the &quot;real&quot; configuration data remain.<br /> <br /> You should return a boolean value denoting the success or failure of your method's actions.<br /> o<br /> get_content<br /> <br /> function get_content() {<br /> // This should be implemented by the derived class.<br /> return NULL;<br /> }<br /> <br /> This method should, when called, populate the $this-&gt;content variable of your block. Populating the variable means:<br /> <br /> EITHER<br /> defining $this-&gt;content-&gt;text and $this-&gt;content-&gt;footer if your block derives from block_base. Both of these should be strings, and can contain arbitrary HTML.<br /> <br /> OR<br /> defining $this-&gt;content-&gt;items, $this-&gt;content-&gt;icons and $this-&gt;content-&gt;footer if your block derives from block_list. The first two should be numerically indexed arrays having the exact same number of elements. $this-&gt;content-&gt;items is an array of strings that can contain arbitrary HTML while $this-&gt;content-&gt;icons also contains should strings, but those must be fully-qualified HTML &lt;img&gt; tags and nothing else. $this-&gt;content-&gt;footer is a string, as above.<br /> <br /> If you set all of these variables to their default &quot;empty&quot; values (empty arrays for the arrays and empty strings for the strings), the block will not be displayed at all except to editing users. This is a good way of having your block hide itself to unclutter the screen if there is no reason to have it displayed.<br /> <br /> Before starting to populate $this-&gt;content, you should also include a simple caching check. If $this-&gt;content is exactly equal to NULL then proceed as normally, while if it is not, return the existing value instead of calculating it once more. If you fail to do this, Moodle will suffer a performance hit.<br /> <br /> In any case, your method should return the fully constructed $this-&gt;content variable.<br /> o<br /> has_config<br /> <br /> function has_config() {<br /> return false;<br /> }<br /> <br /> This method should return a boolean value that denotes whether your block wants to present a configuration interface to site admins or not. The configuration that this interface offers will impact all instances of the block equally.<br /> <br /> To actually implement the configuration interface, you will either need to rely on the default config_print method or override it. The full guide contains more information on this.<br /> o<br /> hide_header<br /> <br /> function hide_header() {<br /> //Default, false--&gt; the header is shown<br /> return false;<br /> }<br /> <br /> This method should return a boolean value that denotes whether your block wants to hide its header (or title). Thus, if you override it to return true, your block will not display a title unless the current user is in editing mode.<br /> o<br /> html_attributes<br /> <br /> function html_attributes() {<br /> // Default case: an id with the instance and a class with our name in it<br /> return array('id' =&gt; 'inst'.$this-&gt;instance-&gt;id, 'class' =&gt; 'block_'. $this-&gt;name());<br /> }<br /> <br /> This method should return an associative array of HTML attributes that will be given to your block's container element when Moodle constructs the output HTML. No sanitization will be performed in these elements at all.<br /> <br /> If you intend to override this method, you should return the default attributes as well as those you add yourself. The recommended way to do this is:<br /> <br /> function html_attributes() {<br /> $attrs = parent::html_attributes();<br /> // Add your own attributes here, e.g.<br /> // $attrs['width'] = '50%';<br /> return $attrs;<br /> }<br /> <br /> o<br /> init<br /> <br /> function init() {<br /> $this-&gt;title = get_string('simplehtml', 'block_simplehtml');<br /> $this-&gt;version = 2004111200;<br /> }<br /> <br /> This method must be implemented for all blocks. It has to assign meaningful values to the object variables $this-&gt;title and $this-&gt;version (which is used by Moodle for performing automatic updates when available).<br /> <br /> No return value is expected from this method.<br /> o<br /> instance_allow_config<br /> <br /> function instance_allow_config() {<br /> return false;<br /> }<br /> <br /> This method should return a boolean value. True indicates that your block wants to have per-instance configuration, while false means it does not. If you do want to implement instance configuration, you will need to take some additional steps apart from overriding this method; refer to the full guide for more information.<br /> <br /> This method's return value is irrelevant if instance_allow_multiple returns true; it is assumed that if you want multiple instances then each instance needs its own configuration.<br /> o<br /> instance_allow_multiple<br /> <br /> function instance_allow_multiple() {<br /> // Are you going to allow multiple instances of each block?<br /> // If yes, then it is assumed that the block WILL USE per-instance configuration<br /> return false;<br /> }<br /> <br /> This method should return a boolean value, indicating whether you want to allow multiple instances of this block in the same page or not. If you do allow multiple instances, it is assumed that you will also be providing per-instance configuration for the block. Thus, you will need to take some additional steps apart from overriding this method; refer to the full guide for more information.<br /> o<br /> instance_config_print<br /> <br /> function instance_config_print() {<br /> // Default behavior: print the config_instance.html file<br /> // You don't need to override this if you're satisfied with the above<br /> if (!$this-&gt;instance_allow_multiple() &amp;&amp; !$this-&gt;instance_allow_config()) {<br /> return false;<br /> }<br /> global $CFG, $THEME;<br /> <br /> if (is_file($CFG-&gt;dirroot .'/blocks/'. $this-&gt;name() .'/config_instance.html')) {<br /> print_simple_box_start('center', '', $THEME-&gt;cellheading);<br /> include($CFG-&gt;dirroot .'/blocks/'. $this-&gt;name() .'/config_instance.html');<br /> print_simple_box_end();<br /> } else {<br /> notice(get_string('blockconfigbad'),<br /> str_replace('blockaction=', 'dummy=', qualified_me()));<br /> }<br /> <br /> return true;<br /> }<br /> <br /> This method allows you to choose how to display the instance configuration screen for your block. Override it if you need something much more complex than the default implementation allows you to do. Keep in mind that whatever you do output from config_print, it will be enclosed in a HTML form automatically. You only need to provide a way to submit that form.<br /> <br /> You should return a boolean value denoting the success or failure of your method's actions.<br /> o<br /> instance_config_save<br /> <br /> function instance_config_save($data) {<br /> $data = stripslashes_recursive($data);<br /> $this-&gt;config = $data;<br /> return set_field('block_instance', 'configdata', base64_encode(serialize($data)), <br /> 'id', $this-&gt;instance-&gt;id);<br /> }<br /> <br /> This method allows you to override the storage mechanism for your instance configuration data. The received argument is an associative array, with the keys being setting names and the values being setting values.<br /> <br /> The configuration must be stored in the &quot;configdata&quot; field of your instance record in the database so that Moodle can auto-load it when your block is constructed. However, you may still want to override this method if you need to take some additional action apart from saving the data. In that case, you really should do what data processing you want and then call parent::instance_config_save($data) with your new $data array. This will keep your block from becoming broken if the default implementation of instance_config_save changes in the future.<br /> <br /> Note that $data does not hold all of the submitted POST data because Moodle adds some hidden fields to the form in order to be able to process it. However, before calling this method it strips the hidden fields from the received data and so when this method is called only the &quot;real&quot; configuration data remain.<br /> <br /> If you want to update the stored copy of the configuration data at run time (for example to persist some changes you made programmatically), you should not use this method. The correct procedure for that purpose is to call instance_config_commit.<br /> <br /> You should return a boolean value denoting the success or failure of your method's actions.<br /> o<br /> preferred_width<br /> <br /> function preferred_width() {<br /> // Default case: the block wants to be 180 pixels wide<br /> return 180;<br /> }<br /> <br /> This method should return an integer value, which is the number of pixels of width your block wants to take up when displayed. Moodle will try to honor your request, but this is actually up to the implementation of the format of the page your block is being displayed in and therefore no guarantee is given. You might get exactly what you want or any other width the format decides to give you, although obviously an effort to accomodate your block will be made.<br /> <br /> Most display logic at this point allocates the maximum width requested by the blocks that are going to be displayed, bounding it both downwards and upwards to avoid having a bad-behaving block break the format.<br /> o<br /> refresh_content<br /> <br /> function refresh_content() {<br /> // Nothing special here, depends on content()<br /> $this-&gt;content = NULL;<br /> return $this-&gt;get_content();<br /> }<br /> <br /> This method should cause your block to recalculate its content immediately. If you follow the guidelines for get_content, which say to respect the current content value unless it is NULL, then the default implementation will do the job just fine.<br /> <br /> You should return the new value of $this-&gt;content after refreshing it.<br /> o<br /> specialization<br /> <br /> function specialization() {<br /> // Just to make sure that this method exists.<br /> }<br /> <br /> This method is automatically called by the framework immediately after your instance data (which includes the page type and id and all instance configuration data) is loaded from the database. If there is some action that you need to take as soon as this data becomes available and which cannot be taken earlier, you should override this method.<br /> <br /> The instance data will be available in the variables $this-&gt;instance and $this-&gt;config.<br /> <br /> This method should not return anything at all.<br /> *<br /> Methods which you should not override but may want to use:<br /> o<br /> instance_config_commit<br /> <br /> function instance_config_commit() {<br /> return set_field('block_instance',<br /> 'configdata', base64_encode(serialize($this-&gt;config)),<br /> 'id', $this-&gt;instance-&gt;id);<br /> }<br /> <br /> This method saves the current contents of $this-&gt;config to the database. If you need to make a change to the configuration settings of a block instance at run time (and not through the usual avenue of letting the user change it), just make the changes you want to $this-&gt;config and then call this method.<br /> o<br /> get_content_type<br /> <br /> function get_content_type() {<br /> return $this-&gt;content_type;<br /> }<br /> <br /> This method returns the value of $this-&gt;content_type, and is the preferred way of accessing that variable. It is guaranteed to always work, now and forever. Directly accessing the variable is not recommended; future library changes may break compatibility with code that does so.<br /> o<br /> get_title<br /> <br /> function get_title() {<br /> return $this-&gt;title;<br /> }<br /> <br /> This method returns the value of $this-&gt;title, and is the preferred way of accessing that variable. It is guaranteed to always work, now and forever. Directly accessing the variable is not recommended; future library changes may break compatibility with code that does so.<br /> o<br /> get_version<br /> <br /> function get_version() {<br /> return $this-&gt;version;<br /> }<br /> <br /> This method returns the value of $this-&gt;version, and is the preferred way of accessing that variable. It is guaranteed to always work, now and forever. Directly accessing the variable is not recommended; future library changes may break compatibility with code that does so.<br /> o<br /> is_empty<br /> <br /> For blocks that extend class block_base:<br /> <br /> function is_empty() {<br /> $this-&gt;get_content();<br /> return(empty($this-&gt;content-&gt;text) &amp;&amp; empty($this-&gt;content-&gt;footer));<br /> }<br /> <br /> For blocks that extend class block_list:<br /> <br /> function is_empty() {<br /> $this-&gt;get_content();<br /> return (empty($this-&gt;content-&gt;items) &amp;&amp; empty($this-&gt;content-&gt;footer));<br /> }<br /> <br /> This method returns the a boolean true/false value, depending on whether the block has any content at all to display. Blocks without content are not displayed by the framework.<br /> o<br /> name<br /> <br /> function name() {<br /> static $myname;<br /> if ($myname === NULL) {<br /> $myname = strtolower(get_class($this));<br /> $myname = substr($myname, strpos($myname, '_') + 1);<br /> }<br /> return $myname;<br /> }<br /> <br /> This method returns the internal name of your block inside Moodle, without the block_ prefix. Obtaining the name of a block object is sometimes useful because it can be used to write code that is agnostic to the actual block's name (and thus more generic and reusable). For an example of this technique, see the config_print method.<br /> *<br /> Methods which you should not override and not use at all:<br /> o<br /> _self_test<br /> <br /> This is a private method; no description is given.<br /> o<br /> _add_edit_controls<br /> <br /> This is a private method; no description is given.<br /> o<br /> _load_instance<br /> <br /> This is a private method; no description is given.<br /> o<br /> _print_block<br /> <br /> This is a private method; no description is given.<br /> o<br /> _print_shadow<br /> <br /> This is a private method; no description is given.<br /> <br /> The class block_base also has a few standard member variables which its methods manipulate. These variables, the purpose of each and the type of data they are expected to hold is explained in the next section of this Appendix.<br /> Class variables:<br /> <br /> *<br /> $this-&gt;config<br /> <br /> This variable holds all the specialized instance configuration data that have been provided for this specific block instance (object). It is an object of type stdClass, with member variables directly corresponding to the HTML &lt;input&gt; elements in the block's config_instance.html file.<br /> <br /> The variable is initialized just after the block object is constructed, immediately before specialization is called for the object. It is possible that the block has no instance configuration, in which case the variable will be NULL.<br /> <br /> It is obvious that there is a direct relationship between this variable and the configdata field in the mdl_block_instance table. However, it is strongly advised that you refrain from accessing the configdata field yourself. If you absolutely must update its value at any time, it is recommended that you call the method instance_config_commit to do the actual work.<br /> *<br /> $this-&gt;content_type<br /> <br /> This variable instructs Moodle on what type of content it should assume the block has, and is used to differentiate text blocks from list blocks. It is essential that it has a meaningful value, as Moodle depends on this for correctly displaying the block on screen. Consequently, this variable is closely tied with the variable $this-&gt;content. The variable is expected to have a valid value after the framework calls the init method for each block.<br /> <br /> The only valid values for this variable are the two named constants BLOCK_TYPE_TEXT and BLOCK_TYPE_LIST.<br /> *<br /> $this-&gt;content<br /> <br /> This variable holds all the actual content that is displayed inside each block. Valid values for it are either NULL or an object of class stdClass, which must have specific member variables set as explained below. Normally, it begins life with a value of NULL and it becomes fully constructed (i.e., an object) when get_content is called.<br /> <br /> After it is fully constructed, this object is expected to have certain properties, depending on the value of $this-&gt;content_type. Specifically:<br /> o If $this-&gt;content_type is BLOCK_TYPE_TEXT, then $this-&gt;content is expected to have the following member variables:<br /> +<br /> text<br /> This is a string of arbitrary length and content. It is displayed inside the main area of the block, and can contain HTML.<br /> +<br /> footer<br /> This is a string of arbitrary length and contents. It is displayed below the text, using a smaller font size. It can also contain HTML.<br /> o If $this-&gt;content_type is BLOCK_TYPE_LIST, then $this-&gt;content is expected to have the following member variables:<br /> +<br /> items<br /> This is a numerically indexed array of strings which holds the title for each item in the list that will be displayed in the block's area. Since usually such lists function like menus, the title for each item is normally a fully qualified HTML &lt;a&gt; tag.<br /> +<br /> icons<br /> This is a numerically indexed array of strings which represent the images displayed before each item of the list. It therefore follows that it should have the exact number of elements as the items member variable. Each item in this array should be a fully qualified HTML &lt;img&gt; tag.<br /> +<br /> footer<br /> This is a string of arbitrary length and contents. It is displayed below the text, using a smaller font size. It can also contain HTML.<br /> <br /> *<br /> $this-&gt;instance<br /> <br /> This member variable holds all the specific information that differentiates one block instance (i.e., the PHP object that embodies it) from another. It is an object of type stdClass retrieved by calling get_record on the table mdl_block_instance. Its member variables, then, directly correspond to the fields of that table. It is initialized immediately after the block object itself is constructed.<br /> *<br /> $this-&gt;title<br /> <br /> This variable is a string that contains the human-readable name of the block. It is used to refer to blocks of that type throughout Moodle, for example in the administrator's block configuration screen and in the editing teacher's add block menu. It is also the title that is printed when the block is displayed on screen, although blocks can specifically change this title to something else if they wish (see below). The variable is expected to have a valid value after the framework calls the init method for each object.<br /> <br /> In the case of blocks which may want to configure their title dynamically through instance configuration, it is still essential to provide a valid title inside init. This title may then be overridden when the specialization method is called by the framework:<br /> <br /> function specialization() {<br /> // At this point, $this-&gt;instance and $this-&gt;config are available<br /> // for use. We can now change the title to whatever we want.<br /> $this-&gt;title = $this-&gt;config-&gt;variable_holding_the_title;<br /> }<br /> <br /> *<br /> $this-&gt;version<br /> <br /> This variable should hold each block's version number in the form YYYYMMDDXX, as per the convention throughout Moodle. The version number is used by Moodle to detect when a block has been upgraded and it consequently needs to run the block's upgrade code to bring the &quot;old&quot; version of the block's data up to date. The variable is expected to have a valid value after the framework calls the init method for each block.<br /> <br /> Most blocks do not keep complex data of their own in the database the way that modules do, so in most cases nothing actually happens during a block version upgrade. However, the version number is displayed in the administration interface for blocks. It is good practice therefore to change your block's version number when it gains new functionality or receives important bug fixes, to enable site administrators to easily identify the exact version of the block they are working with.<br /> <br /> Appearing throughout the code related to the Blocks API, there is a number of predefined constants that are utilized to avoid the use of &quot;magic numbers&quot; in the code. These constants are:<br /> Named constants:<br /> <br /> *<br /> BLOCK_TYPE_LIST<br /> <br /> This is one of the two valid values for the $this-&gt;content_type member variable of every block. Its value specifies the exact requirements that Moodle will then have for $this-&gt;content.<br /> *<br /> BLOCK_TYPE_TEXT<br /> <br /> This is one of the two valid values for the $this-&gt;content_type member variable of every block. Its value specifies the exact requirements that Moodle will then have for $this-&gt;content.<br /> <br /> Appendix B: Differences in the Blocks API for Moodle versions prior to 1.5<br /> <br /> This Appendix will discuss what changes in the Blocks API were introduced by Moodle 1.5 and what steps developers need to take to update their blocks to be fully compatible with Moodle 1.5. Unfortunately, with these changes backward compatibility is broken; this means that blocks from Moodle 1.4 will never work with 1.5 and vice versa.<br /> <br /> 1.<br /> Class naming conventions changed<br /> <br /> In Moodle 1.4, all block classes were required to have a name like CourseBlock_something and the base class from which the derived was MoodleBlock. This has changed in Moodle 1.5, to bring the naming conventions in line with other object-oriented aspects of Moodle (for example there are classes enrolment_base, resource_base etc). The new block classes should instead be named like block_something and derive from block_base. This means that in order to make a block compatible with Moodle 1.5, you need to change the class definition<br /> <br /> class CourseBlock_online_users extends MoodleBlock { ... }<br /> <br /> to<br /> <br /> class block_online_users extends block_base { ... }<br /> <br /> An exception to the above is the special case where the block is intended to display a list of items instead of arbitrary text; in this case the block class must derive from class block_list instead, like this:<br /> <br /> class block_admin extends block_list { ... }<br /> <br /> 2.<br /> Constructor versus init()<br /> <br /> In Moodle 1.4, in each block class it was mandatory to define a constructor which accepted a course data record as an argument (the example is from the actual Online Users block):<br /> <br /> function CourseBlock_online_users ($course) {<br /> $this-&gt;title = get_string('blockname','block_online_users');<br /> $this-&gt;content_type = BLOCK_TYPE_TEXT;<br /> $this-&gt;course = $course;<br /> $this-&gt;version = 2004052700;<br /> }<br /> <br /> In contrast, Moodle 1.5 does away with the constructor and instead requires you to define an init() method that takes no arguments:<br /> <br /> function init() {<br /> $this-&gt;title = get_string('blockname','block_online_users');<br /> $this-&gt;version = 2004111600;<br /> }<br /> <br /> Of course, this leaves you without access to the $course object, which you might actually need. Since that's probably going to be needed inside get_content, the way to retrieve it is by using this code:<br /> <br /> $course = get_record('course', 'id', $this-&gt;instance-&gt;pageid);<br /> <br /> If you are going to need access to $course from inside other methods in addition to get_content, you might fetch the $course object inside the specialization method and save it as a class variable for later use, in order to avoid executing the same query multiple times:<br /> <br /> function specialization() {<br /> $this-&gt;course = get_record('course', 'id', $this-&gt;instance-&gt;pageid);<br /> }<br /> <br /> 3.<br /> Blocks with configuration<br /> <br /> In Moodle 1.4, blocks could only have what are now (in Moodle 1.5) called &quot;global configuration&quot; options, to differentiate from the new &quot;instance configuration&quot; options. If your block has support for configuration, you will need to take these steps:<br /> 1. Rename your config.html file to config_global.html.<br /> 2. Edit the newly renamed file and completely remove the &lt;form&gt; tag (Moodle now wraps your configuration in a form automatically).<br /> 3. If you are using any HTML &lt;input&gt; tags other than those that directly affect your configuration (for example, &quot;sesskey&quot;), REMOVE those too (Moodle will add them automatically as required).<br /> 4. If you have overridden print_config, rename your method to config_print.<br /> 5. If you have overridden handle_config, rename your method to config_save.<br /> 4.<br /> Blocks with customized applicable formats<br /> <br /> The correct way to specify the formats you want to allow or disallow your block to exist has been reworked for Moodle 1.5 to take account of the fact that blocks are no longer restricted to just courses. To have a block retain its intended behavior, you must change these format names (array keys in the return value of applicable_formats) if they are used in your block:<br /> * social should become course-view-social<br /> * topics should become course-view-topics<br /> * weeks should become course-view-weeks<br /> <br /> You should also keep in mind that there is now the possibility of blocks being displayed in other pages too, like the introductory page that users see when they enter an activity module. You might therefore need to make the specification for applicable formats more restrictive to keep your block out of pages it is not supposed to be shown in. Also, there are subtle changes to the way that the final decision to allow or disallow a block is made. For the technical details refer to the definition of applicable_formats, and for a more extended example read the section dedicated to this subject.<br /> <br /> That's everything; your block will now be ready for use in Moodle 1.5!<br /> <br /> The End</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Developer_documentation&diff=5140 2006-02-11T04:20:38Z

<p>Martin: /* Documentation for specific modules */</p> <hr /> <div>*[[Roadmap]]<br /> <br /> *[[Developer notes]]<br /> *[[Developer conference|Developer conferences]]<br /> *[[Coding|Coding guidelines]]<br /> *[[CVS|Moodle CVS for developers]]<br /> *[[Moodle architecture]]<br /> <br /> ===Documentation for specific modules===<br /> <br /> *[[Quiz developer docs|Quiz module]]<br /> *[[SCORM schema|SCORM module 1.5 schema]]<br /> *[[Blocks Howto|Blocks]]<br /> <br /> ===How you can contribute===<br /> <br /> Even if you are not a programmer there are things you can change or help with.<br /> *[[Activity modules]]<br /> *[[Themes]]<br /> *[[Translation]]<br /> *[[Database Schemas|Database schemas]]<br /> *[[Course formats]]<br /> *[[Bug tracker|Participating in the bug tracker]]<br /> <br /> == See also ==<br /> <br /> *[http://moodle.org/blocks/HOWTO.html A step-by-step guide to creating blocks]<br /> *[http://moodle.org/bugs/ Moodle bug tracker] - bug reports, feature requests and other tracked issues<br /> *[http://cvs.sourceforge.net/viewcvs.py/moodle/moodle/ CVS code]<br /> *[http://moodle.org/xref/nav.html?index.html Cross reference] - phpxref output for browsing Moodle source code<br /> *[http://moodle.org/mod/resource/view.php?id=1267 Core API]<br /> *[http://moodle.sourceforge.net/dhawes-phpdoc/ Moodle PHP doc reference]<br /> *[http://security.moodle.org/ Moodle Security Centre]<br /> *[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services<br /> *[[Presentations]]<br /> *[[Moodle manuals]]<br /> *[[Using Moodle book]]<br /> <br /> [[Category:Core]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Developer_documentation&diff=5139 2006-02-11T04:19:24Z

<p>Martin: /* Documentation for specific modules */</p> <hr /> <div>*[[Roadmap]]<br /> <br /> *[[Developer notes]]<br /> *[[Developer conference|Developer conferences]]<br /> *[[Coding|Coding guidelines]]<br /> *[[CVS|Moodle CVS for developers]]<br /> *[[Moodle architecture]]<br /> <br /> ===Documentation for specific modules===<br /> <br /> *[[Quiz developer docs|Quiz module]]<br /> *[[SCORM schema|SCORM module 1.5 schema]]<br /> *[[Blocks|Blocks Howto]]<br /> <br /> ===How you can contribute===<br /> <br /> Even if you are not a programmer there are things you can change or help with.<br /> *[[Activity modules]]<br /> *[[Themes]]<br /> *[[Translation]]<br /> *[[Database Schemas|Database schemas]]<br /> *[[Course formats]]<br /> *[[Bug tracker|Participating in the bug tracker]]<br /> <br /> == See also ==<br /> <br /> *[http://moodle.org/blocks/HOWTO.html A step-by-step guide to creating blocks]<br /> *[http://moodle.org/bugs/ Moodle bug tracker] - bug reports, feature requests and other tracked issues<br /> *[http://cvs.sourceforge.net/viewcvs.py/moodle/moodle/ CVS code]<br /> *[http://moodle.org/xref/nav.html?index.html Cross reference] - phpxref output for browsing Moodle source code<br /> *[http://moodle.org/mod/resource/view.php?id=1267 Core API]<br /> *[http://moodle.sourceforge.net/dhawes-phpdoc/ Moodle PHP doc reference]<br /> *[http://security.moodle.org/ Moodle Security Centre]<br /> *[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services<br /> *[[Presentations]]<br /> *[[Moodle manuals]]<br /> *[[Using Moodle book]]<br /> <br /> [[Category:Core]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Developer_documentation&diff=5138 2006-02-11T04:18:46Z

<p>Martin: /* Documentation for specific modules */</p> <hr /> <div>*[[Roadmap]]<br /> <br /> *[[Developer notes]]<br /> *[[Developer conference|Developer conferences]]<br /> *[[Coding|Coding guidelines]]<br /> *[[CVS|Moodle CVS for developers]]<br /> *[[Moodle architecture]]<br /> <br /> ===Documentation for specific modules===<br /> <br /> *[[Quiz developer docs|Quiz module]]<br /> *[[SCORM schema|SCORM module 1.5 schema]]<br /> *[[Blocks]]<br /> <br /> ===How you can contribute===<br /> <br /> Even if you are not a programmer there are things you can change or help with.<br /> *[[Activity modules]]<br /> *[[Themes]]<br /> *[[Translation]]<br /> *[[Database Schemas|Database schemas]]<br /> *[[Course formats]]<br /> *[[Bug tracker|Participating in the bug tracker]]<br /> <br /> == See also ==<br /> <br /> *[http://moodle.org/blocks/HOWTO.html A step-by-step guide to creating blocks]<br /> *[http://moodle.org/bugs/ Moodle bug tracker] - bug reports, feature requests and other tracked issues<br /> *[http://cvs.sourceforge.net/viewcvs.py/moodle/moodle/ CVS code]<br /> *[http://moodle.org/xref/nav.html?index.html Cross reference] - phpxref output for browsing Moodle source code<br /> *[http://moodle.org/mod/resource/view.php?id=1267 Core API]<br /> *[http://moodle.sourceforge.net/dhawes-phpdoc/ Moodle PHP doc reference]<br /> *[http://security.moodle.org/ Moodle Security Centre]<br /> *[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services<br /> *[[Presentations]]<br /> *[[Moodle manuals]]<br /> *[[Using Moodle book]]<br /> <br /> [[Category:Core]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Student_Information_API&diff=5133 2006-02-10T22:03:40Z

<p>Martin: </p> <hr /> <div>Some standards<br /> <br /> PESC <br /> <br /> SIF<br /> <br /> IMS Enterprise<br /> <br /> Things to pass out<br /> <br /> * Grades<br /> * Outcomes<br /> * Calendar events</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Student_Information_API&diff=5132 2006-02-10T22:01:53Z

<p>Martin: </p> <hr /> <div>Some standards<br /> <br /> PESC <br /> <br /> SIF<br /> <br /> IMS Enterprise</div>

Martin https://docs.moodle.org/501/en/index.php?title=MediaWiki:Talk&diff=4806 2006-02-06T08:32:49Z

<p>Martin: Trying this out</p> <hr /> <div>Page Comments</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Community_hub&diff=4791 2006-02-06T06:33:54Z

<p>Martin: </p> <hr /> <div>[[Image:Community.png]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Community_hub&diff=4790 2006-02-06T06:33:28Z

<p>Martin: </p> <hr /> <div>[[Image:Community.jpg]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=File:Community.png&diff=4789 2006-02-06T06:33:00Z

<p>Martin: </p> <hr /> <div></div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4526 2006-02-03T14:00:46Z

<p>Martin: /* Version 1.6 - Beta expected late February 2006 */</p> <hr /> <div>This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.<br /> <br /> == Version 1.6 - Beta expected late February 2006 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> * [[Granularised Backup]] - Catalyst and Eloy Lafuente<br /> ::<br /> * [[Chameleon]] - <br /> ::<br /> <br /> == Version 2.0 - Expected end of 2006 ==<br /> <br /> * [[IMS Learning Design]] - moodle.com<br /> :: Support for importing/exporting LD, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses<br /> * [[Conditional activities]] - moodle.com<br /> ::allowing dependencies and forced paths through the content. It also provides support for <br /> * [[Roles]] - moodle.com<br /> ::this new system will allow the creation of custom roles at site, course and activity level<br /> * [[Metadata]] - moodle.com<br /> ::build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula<br /> * [[Accessibility]] - moodle.com <br /> ::Full compliance with all major accessibility standards<br /> * [[Web Services API]]<br /> ::Providing remote control and access of Moodle services by other systems, as well as sharing of information between Moodle sites with trust relationships.<br /> * [[Repository API]] - moodle.com<br /> ::Abstract all file operations to an API that allows plugins for different external repositories.<br /> * [[Student Information API]]<br /> ::API for integrating external systems for managing student career<br /> * [[Community Hub]] - moodle.com <br /> ::Leverage above improvements into a system to network Moodles together.<br /> <br /> == Version 2.1 ==<br /> <br /> * [[Groups]] <br /> ::groups can also be defined at the site level, and activities can be assigned to course groups<br /> * [[Portfolio API]]<br /> ::Interface Moodle activities and repositories to help produce portfolios for internal assessment AND external publication<br /> <br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Developer_documentation&diff=4520 2006-02-03T11:10:42Z

<p>Martin: </p> <hr /> <div>*[[Roadmap]]<br /> <br /> *[[Developer notes]]<br /> *[[Coding|Coding guidelines]]<br /> *[[CVS|Moodle CVS for developers]]<br /> *[[Moodle architecture]]<br /> <br /> ===Documentation for specific modules===<br /> <br /> *[[Quiz developer docs|Quiz module]]<br /> *[[SCORM schema|SCORM module 1.5 schema]]<br /> <br /> ===How you can contribute===<br /> <br /> Even if you are not a programmer there are things you can change or help with.<br /> *[[Activity modules]]<br /> *[[Themes]]<br /> *[[Translation]]<br /> *[[Database Schemas|Database schemas]]<br /> *[[Course formats]]<br /> *[[Bug tracker|Participating in the bug tracker]]<br /> <br /> == See also ==<br /> <br /> *[http://moodle.org/blocks/HOWTO.html A step-by-step guide to creating blocks]<br /> *[http://moodle.org/bugs/ Moodle bug tracker] - bug reports, feature requests and other tracked issues<br /> *[http://cvs.sourceforge.net/viewcvs.py/moodle/moodle/ CVS code]<br /> *[http://moodle.org/xref/nav.html?index.html Cross reference] - phpxref output for browsing Moodle source code<br /> *[http://moodle.org/mod/resource/view.php?id=1267 Core API]<br /> *[http://moodle.sourceforge.net/dhawes-phpdoc/ Moodle PHP doc reference]<br /> *[http://security.moodle.org/ Moodle Security Centre]<br /> *[http://moodle.com/partners/ Moodle Partners] - providers of custom Moodle development services<br /> <br /> [[Category:Core]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development_talk:Outcomes&diff=4517 2006-02-03T11:07:36Z

<p>Martin: Talk:Moodle metadata moved to Talk:Metadata</p> <hr /> <div>I have designed a simple XML schema to store ISO/IEC XML metadata. It is not a full implementation but it does have all the metadata structures. Please let me know if anyone is interested.<br /> <br /> You can see a brief description of some of the structures in the paper I am giving at the semantic web technology conference.<br /> <br /> http://www.danmccreary.com/presentations/semweb2006/<br /> <br /> I know a lot about metadata and semantics but am just learning moodle. Please forgive me if I am too bold.</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:Outcomes&diff=4515 2006-02-03T11:07:36Z

<p>Martin: Moodle metadata moved to Metadata</p> <hr /> <div>'''Feature description:''' Build on the [[Moodle keywords|keywords]] in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula.<br /> <br /> This pages is an initial place to discuss options for storing and managing moodle metadata. These are just suggestions and are made by a person who does not know moodle internals.<br /> <br /> There are several steps to managing a complex applications metadata:<br /> # Document the key &quot;Data Element Concpets&quot; and their structure. This would include high-level concepts such as Course, Student, Teacher etc.<br /> # Document data element properties associated with each concept. Properties should always be associated with a concept.<br /> # Store this metadata in a metadata &quot;registry&quot;, a centrally managed place to store metadata<br /> # Create a system that allows users to modify and update metadata<br /> <br /> There are several ways to approach this.<br /> <br /> * There are metadata registry standards such as ISO/IEC 11179. This standard has a wide number of interpretations.<br /> * There are other education metadata standards such as IMS global and the School Interoperability Framework (SIF)<br /> * Once the metadata is stored in a consistant place and format, transforms can be made to extract portions of the metadata using reports or transforms<br /> * A matadata registry can be the heart of a model-driven architecture<br /> <br /> Most systems attempt to seperate the semantics from the representation of metadata.<br /> # Semantics tell us the meaning of a data element but are free from version or constraints<br /> # Represtations of the metadata tell us what table and column metadata appears in each version of Moodle and what the limitations are in a specification<br /> <br /> Many metadata managment systems use a 3-part data element name:<br /> <br /> ClassPropertyTerm<br /> <br /> Were Class is the concept, property is a property of that concept and Term is a Representation term such as Count, Date, ID, Indicator, Text<br /> <br /> For example:<br /> <br /> CourseDescriptionText<br /> <br /> ==Questions==<br /> * Where can we get a list of key moodle conceptual data elements and their definitions?<br /> <br /> * How do we set up a data stewardship role so individuals take responsiblity for maintaining subsets of all the data elements?<br /> <br /> * What should the highest level data elements be? Course, Enrollment, Organization, Person, Quiz<br /> <br /> ==See also==<br /> * [[Thing]] A root data element of a metadata registry<br /> * [http://en.wikipedia.org/wiki/Metadata_registry Wikipedia entry for Metadata registry]<br /> * [http://en.wikipedia.org/wiki/ISO/IEC_11179 Wikipedia entry for ISO/IEC 11179 ]<br /> * [http://en.wikipedia.org/wiki/Data_element Wikipedia entry for Data element]<br /> * [http://en.wikipedia.org/wiki/Representation_term Wikipedia entry for Representation term]<br /> * [http://en.wikipedia.org/wiki/Data_element_name Wikipedia entry for Data element name ]<br /> * [http://en.wikipedia.org/wiki/Data_element_definition Wikipedia entry for Data element definition ]<br /> <br /> ==Example of a K-12 education metadata registry for ==<br /> * [http://education.state.mn.us/datadictionary Minnesota (US) Department of Education Data Dictionary]<br /> <br /> [[Category:metadata]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4514 2006-02-03T11:05:55Z

<p>Martin: /* Version 2.0 - Expected end of 2006 */</p> <hr /> <div>This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.<br /> <br /> == Version 1.6 - Beta expected late February 2006 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> <br /> == Version 2.0 - Expected end of 2006 ==<br /> <br /> * [[IMS Learning Design]] - moodle.com<br /> :: Support for importing/exporting LD, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses<br /> * [[Conditional activities]] - moodle.com<br /> ::allowing dependencies and forced paths through the content. It also provides support for <br /> * [[Roles]] - moodle.com<br /> ::this new system will allow the creation of custom roles at site, course and activity level<br /> * [[Metadata]] - moodle.com<br /> ::build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula<br /> * [[Accessibility]] - moodle.com <br /> ::Full compliance with all major accessibility standards<br /> * [[Web Services API]]<br /> ::Providing remote control and access of Moodle services by other systems, as well as sharing of information between Moodle sites with trust relationships.<br /> * [[Repository API]] - moodle.com<br /> ::Abstract all file operations to an API that allows plugins for different external repositories.<br /> * [[Student Information API]]<br /> ::API for integrating external systems for managing student career<br /> * [[Community Hub]] - moodle.com <br /> ::Leverage above improvements into a system to network Moodles together.<br /> <br /> == Version 2.1 ==<br /> <br /> * [[Groups]] <br /> ::groups can also be defined at the site level, and activities can be assigned to course groups<br /> * [[Portfolio API]]<br /> ::Interface Moodle activities and repositories to help produce portfolios for internal assessment AND external publication<br /> <br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4461 2006-02-02T15:46:32Z

<p>Martin: </p> <hr /> <div>This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.<br /> <br /> == Version 1.6 - Beta expected late February 2006 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> <br /> == Version 2.0 - Expected end of 2006 ==<br /> <br /> (These may be split into two or more releases)<br /> <br /> * [[IMS Learning Design]] - moodle.com<br /> :: Support for importing/exporting LD, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses<br /> * [[Conditional activities]] - moodle.com<br /> ::allowing dependencies and forced paths through the content. It also provides support for <br /> * [[Roles]] - moodle.com<br /> ::this new system will allow the creation of custom roles at site, course and activity level<br /> * [[Metadata]] - moodle.com<br /> ::build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula<br /> * [[Accessibility]] - moodle.com <br /> ::Full compliance with all major accessibility standards<br /> * [[Web Services API]]<br /> ::Providing remote control and access of Moodle services by other systems, as well as sharing of information between Moodle sites with trust relationships.<br /> * [[Repository API]] - moodle.com<br /> ::Abstract all file operations to an API that allows plugins for different external repositories.<br /> * [[Student Information API]]<br /> ::API for integrating external systems for managing student career<br /> * [[Community Hub]] - moodle.com <br /> ::Leverage above improvements into a system to network Moodles together.<br /> <br /> <br /> == Version 2.1 ==<br /> <br /> * [[Groups]] <br /> ::groups can also be defined at the site level, and activities can be assigned to course groups<br /> * [[Portfolio API]]<br /> ::Interface Moodle activities and repositories to help produce portfolios for internal assessment AND external publication<br /> <br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4460 2006-02-02T15:38:39Z

<p>Martin: </p> <hr /> <div>This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.<br /> <br /> == Version 1.6 - Beta expected late February 2006 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> <br /> == Version 2.0 - Expected end of 2006 ==<br /> <br /> (These may be split into two or more releases)<br /> <br /> * [[IMS Learning Design]] - moodle.com<br /> :: Support for importing/exporting this format, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses<br /> * [[Conditional activities]] - moodle.com<br /> ::allowing dependencies and forced paths through the content. It also provides support for <br /> * [[Groups]] - moodle.com<br /> ::groups can also be defined at the site level, and activities can be assigned to course groups<br /> * [[Roles]] - moodle.com <br /> ::this new system will allow the creation of custom roles at site, course and activity level<br /> * [[Metadata]] - moodle.com<br /> ::build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula<br /> * [[Accessibility]] - moodle.com <br /> ::Full compliance with all major accessibility standards<br /> * [[Web Services API]]<br /> ::Providing remote control and access of Moodle services by other systems, as well as sharing of information between Moodle sites with trust relationships.<br /> * [[Repository API]] - moodle.com<br /> ::Abstract all file operations to an API that allows plugins for different external repositories.<br /> * [[Student Information API]] - moodle.com <br /> ::API for integrating external systems for managing student career<br /> * [[Portfolio API]]<br /> ::Interface Moodle activities and repositories to help produce portfolios for internal assessment AND external publication<br /> * [[Community Hub]] - moodle.com <br /> ::Leverage above improvements into a system to network Moodles together.<br /> <br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4459 2006-02-02T15:25:00Z

<p>Martin: /* Version 2.0 - Expected later in 2006 */</p> <hr /> <div>This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.<br /> <br /> == Version 1.6 - Beta expected late February 2006 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> <br /> == Version 2.0 - Expected end of 2006 ==<br /> <br /> * [[IMS Learning Design]] - moodle.com<br /> :: Support for importing/exporting this format, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses<br /> * [[Conditional activities]] - moodle.com<br /> ::allowing dependencies and forced paths through the content. It also provides support for <br /> * [[Groups]] - moodle.com<br /> ::groups can also be defined at the site level, and activities can be assigned to course groups<br /> * [[Roles]] - moodle.com <br /> ::this new system will allow the creation of custom roles at site, course and activity level<br /> * [[Metadata]] - moodle.com<br /> ::build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula<br /> * [[Accessibility]] - moodle.com <br /> ::Full compliance with all major accessibility standards<br /> * [[Web Services API]]<br /> ::Providing remote control and access of Moodle services by other systems, as well as sharing of information between Moodle sites with trust relationships.<br /> * [[Repository API]] - moodle.com<br /> ::Abstract all file operations to an API that allows plugins for different external repositories.<br /> * [[Student Information API]] - moodle.com <br /> ::API for integrating external systems for managing student career<br /> * [[Portfolio API]]<br /> ::Interface Moodle activities and repositories to help produce portfolios for assessment AND external <br /> * [[Community Hub]] - moodle.com <br /> ::Leverage above improvements into a system to network Moodles together.<br /> <br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4458 2006-02-02T15:09:27Z

<p>Martin: </p> <hr /> <div>This roadmap collects the best information about upcoming features in Moodle. It is not 100% certain - features may change according to available funding and developers.<br /> <br /> == Version 1.6 - Beta expected late February 2006 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> <br /> == Version 2.0 - Expected later in 2006 ==<br /> <br /> * [[IMS Learning Design]] - moodle.com<br /> :: Support for importing/exporting this format, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses<br /> * [[Conditional activities]] - moodle.com<br /> ::allowing dependencies and forced paths through the content. It also provides support for <br /> * [[Groups]] - moodle.com<br /> ::groups can also be defined at the site level, and activities can be assigned to course groups<br /> * [[Roles]] - moodle.com <br /> ::this new system will allow the creation of custom roles at site, course and activity level<br /> * [[Metadata]] - moodle.com<br /> ::build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula<br /> * [[Web Services API]]<br /> ::Providing remote control and access of Moodle services by other systems, as well as sharing of information between Moodle sites with trust relationships.<br /> * [[Repository API]] - moodle.com<br /> ::Abstract all file operations to an API that allows plugins for different external repositories.<br /> * [[Community Hub]] - moodle.com <br /> ::Leverage above improvements into a system to network Moodles together.<br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4457 2006-02-02T14:52:38Z

<p>Martin: Sorry, Helen, I want this to be more of a developer page, it&#039;s not finished yet</p> <hr /> <div><br /> <br /> Here is the current roadmap of the future, though this is always subject to change depending on [http://moodle.org/donations/ sponsors] and [[Credits|developers]].<br /> <br /> == Version 1.6 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> <br /> == Version 2.0 ==<br /> <br /> * [[IMS Learning Design]] - moodle.com<br /> :: Support for importing/exporting this format, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses<br /> * [[Conditional activities]] - moodle.com<br /> ::allowing dependencies and forced paths through the content. It also provides support for <br /> * [[Groups]] - moodle.com<br /> ::groups can also be defined at the site level, and activities can be assigned to course groups<br /> * [[Roles]] - moodle.com <br /> ::this new system will allow the creation of custom roles at site, course and activity level<br /> * [[Metadata]] - moodle.com<br /> ::build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula<br /> * Many of the main pages customisable using HTML templates.<br /> * Improved Web Services API<br /> * Integration with some repositories<br /> * Some exciting developments in making Moodle more network-aware, with a natural evolution of Moodle's focus on collaboration. More on this here later.<br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Template:About_Moodle&diff=4456 2006-02-02T14:50:48Z

<p>Martin: </p> <hr /> <div>{| cellpadding=&quot;1&quot; style=&quot;float: right; border: 1px solid #aaa; background: #f9f9f9; padding: 5px; margin: 0 0 10px 5px;&quot;<br /> ! style=&quot;padding: 0 5px; background:#e4e4e4&quot; align=&quot;center&quot; | [[About Moodle]]<br /> |-<br /> | style=&quot;font-size: 90%; padding: 0 5px;&quot; |<br /> *[[Background]]<br /> *[[Philosophy]]<br /> *[[License]]<br /> *[[Features]]<br /> *[[Release Notes]]<br /> *[[Future]]<br /> *[[Credits]]<br /> *[[Case for Moodle]]<br /> |}</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4451 2006-02-02T11:20:56Z

<p>Martin: /* Version 2.0 */ continuing ...off to dinner :-)</p> <hr /> <div>Here is the current roadmap of the future, though this is always subject to change depending on [http://moodle.org/donations/ sponsors] and [[Credits|developers]].<br /> <br /> == Version 1.6 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> <br /> <br /> == Version 2.0 ==<br /> <br /> * [IMS Learning Design] - moodle.com<br /> :: Support for importing/exporting this format, converting Moodle activities and sequences of activities into a standard format for sharing, and importing standard sequences into Moodle courses<br /> * [Conditional activities] - moodle.com<br /> ::allowing dependencies and forced paths through the content. It also provides support for <br /> * [Groups] - moodle.com<br /> ::groups can also be defined at the site level, and activities can be assigned to course groups<br /> * [Roles] - moodle.com <br /> ::this new system will allow the creation of custom roles at site, course and activity level<br /> * [Metadata] - moodle.com<br /> ::build on the keywords in 1.6 to provide metadata for all activities and courses, linkable to standard lists of metadata such as State-based learning outomes and curricula<br /> * Many of the main pages customisable using HTML templates.<br /> * Improved Web Services API<br /> * Integration with some repositories<br /> * Some exciting developments in making Moodle more network-aware, with a natural evolution of Moodle's focus on collaboration. More on this here later.<br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4450 2006-02-02T09:59:55Z

<p>Martin: Working on 1.6 format etc</p> <hr /> <div>Here is the current roadmap of the future, though this is always subject to change depending on [http://moodle.org/donations/ sponsors] and [[Credits|developers]].<br /> <br /> == Version 1.6 ==<br /> <br /> * [[Unicode]] - Moodle.com, Eloy Lafuente and Koen Roggemans<br /> ::Moodle is now 100% Unicode, which means any language can be mixed together and an end to a number of problems that different character sets caused us.<br /> * [[Documentation]] - Moodle.com and Helen Foster<br /> ::A new one-stop Wiki site for ALL Moodle documentation, including links from Moodle itself<br /> * [[Database]] - Moodle.com <br /> ::A new activity module that allows collaborative collection of structured data, useful for many things!<br /> * [[LAMS]] - LAMS Foundation<br /> ::Integrated via a course format and an activity module<br /> * [[Blogs]] - Daryl Hawes and Moodle.com<br /> ::Allows reflection on an ongoing basis. Entries are marked and can be viewed by user, course, group, site etc. Contains new keyword support. <br /> * [[Site Stats]] - Catalyst<br /> ::Provides statistics at a higher level than before (by course etc)<br /> * [[My Moodle]] - Catalyst<br /> ::A dashboard interface that allows an overview for each user of all their courses etc<br /> * [[Hive integration]] - Moodle.com and Harvest Road<br /> ::This initial integration with Hive allows teachers to upload, browse, search and select [[mod/resource/index|Resources]] within the external repository.<br /> * [[Multiple Groups]] - Moodle.com and Arab Open University<br /> ::Users can be part of multiple groups within a course.<br /> * [[IMS Resource]] - Eloy Lafuente and Alton College<br /> ::Supports the loading of any content package as a Resource, plus special support for NLN repositories.<br /> * [[Learning Design Export]] - Moodle.com and Open University of The Netherlands<br /> ::We plan to have a very simple export for any Moodle course into IMS LD format, as a proof of concept and to help the community start learning about IMS LD.<br /> <br /> <br /> == Version 2.0 ==<br /> <br /> * Conditional activities, allowing dependencies and forced paths<br /> * Complete support for IMS LD standard<br /> * Improved Groups, allowing groups to be defined at site and activity level<br /> * Improved Roles implementation, allowing custom roles at site, course and activity level<br /> * Many of the main pages customisable using HTML templates.<br /> * Improved Web Services API<br /> * Integration with some repositories<br /> * Some exciting developments in making Moodle more network-aware, with a natural evolution of Moodle's focus on collaboration. More on this here later.<br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4449 2006-02-02T09:27:44Z

<p>Martin: /* Key Moodle Positions */</p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the founder and manager for the whole Moodle project. Since 2005 there is a [http://moodle.com/hq/ team of people] employed over at [http://moodle.com/ Moodle HQ] in Perth, Australia helping him keep on top of things (or at least within sight of the top!).<br /> <br /> The Moodle software package is [[License|Copyright © 1999 onwards, Martin Dougiamas under the GNU GPL]].<br /> <br /> ==Key Moodle Roles==<br /> <br /> * Lead Developer - Martin Dougiamas<br /> * Knight in Shining Armor - Eloy Lafuente<br /> * Translation Coordinator - Koen Roggemans<br /> * Security Officer - Petr Škoda (skodak)<br /> * Documentation Steward - [[User:Helen|Helen Foster]]<br /> * Themes Manager - Urs Hunkler<br /> * Stable Release Manager - Martin Langhoff<br /> <br /> ==Main developers==<br /> <br /> Endless thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff, Urs Hunkler'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please make your suggestions on the discussion tab for this page.<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> * used our [http://moodle.com commercial Moodle Partner services]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://download.moodle.org/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> Urs Hunkler is our Themes Manager, providing support and development.<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (''jlim AT natsoft DOT com DOT my'')<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp (''hermanV AT mindless DOT com'')<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet (''vincent AT phpconcept DOT net'')<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle (''bmatzelle AT yahoo DOT com'')<br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt (''monte AT ispi DOT net'')<br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer (''xnoguer AT rezebra DOT com'')<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan (''chris AT greatbridge DOT com'')<br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4448 2006-02-02T09:27:19Z

<p>Martin: </p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the founder and manager for the whole Moodle project. Since 2005 there is a [http://moodle.com/hq/ team of people] employed over at [http://moodle.com/ Moodle HQ] in Perth, Australia helping him keep on top of things (or at least within sight of the top!).<br /> <br /> The Moodle software package is [[License|Copyright © 1999 onwards, Martin Dougiamas under the GNU GPL]].<br /> <br /> ==Key Moodle Positions==<br /> <br /> * Lead Developer - Martin Dougiamas<br /> * Knight in Shining Armor - Eloy Lafuente<br /> * Translation Coordinator - Koen Roggemans<br /> * Security Officer - Petr Škoda (skodak)<br /> * Documentation Steward - [[User:Helen|Helen Foster]]<br /> * Themes Manager - Urs Hunkler<br /> * Stable Release Manager - Martin Langhoff<br /> <br /> ==Main developers==<br /> <br /> Endless thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff, Urs Hunkler'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please make your suggestions on the discussion tab for this page.<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> * used our [http://moodle.com commercial Moodle Partner services]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://download.moodle.org/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> Urs Hunkler is our Themes Manager, providing support and development.<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (''jlim AT natsoft DOT com DOT my'')<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp (''hermanV AT mindless DOT com'')<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet (''vincent AT phpconcept DOT net'')<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle (''bmatzelle AT yahoo DOT com'')<br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt (''monte AT ispi DOT net'')<br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer (''xnoguer AT rezebra DOT com'')<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan (''chris AT greatbridge DOT com'')<br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4447 2006-02-02T09:25:14Z

<p>Martin: </p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the founder, lead developer, and project manager for the whole Moodle project. Since 2005 there is a [http://moodle.com/hq/ team of people] employed over at [http://moodle.com/ Moodle HQ] in Perth, Australia helping him keep on top of things (or at least within sight of the top!).<br /> <br /> The Moodle software package is [[License|Copyright © 1999 onwards, Martin Dougiamas under the GNU GPL]].<br /> <br /> ==Key Moodle Positions==<br /> <br /> * Moodle Knight - Eloy Lafuente<br /> * Translation Coordinator - Koen Roggemans<br /> * Security Officer - Petr Škoda (skodak)<br /> * Documentation Steward - [[User:Helen|Helen Foster]]<br /> * Themes Manager - Urs Hunkler<br /> * Stable Release Manager - Martin Langhoff<br /> <br /> ==Main developers==<br /> <br /> Endless thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff, Urs Hunkler'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please make your suggestions on the discussion tab for this page.<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> * used our [http://moodle.com commercial Moodle Partner services]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://download.moodle.org/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> Urs Hunkler is our Themes Manager, providing support and development.<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (''jlim AT natsoft DOT com DOT my'')<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp (''hermanV AT mindless DOT com'')<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet (''vincent AT phpconcept DOT net'')<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle (''bmatzelle AT yahoo DOT com'')<br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt (''monte AT ispi DOT net'')<br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer (''xnoguer AT rezebra DOT com'')<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan (''chris AT greatbridge DOT com'')<br /> <br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4446 2006-02-02T09:24:47Z

<p>Martin: </p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the founder, lead developer, and project manager for the whole Moodle project. Since 2005 there is a [http://moodle.com/hq/ team of people] employed over at [http://moodle.com/ Moodle HQ] in Perth, Australia helping him keep on top of things (or at least within sight of the top!).<br /> <br /> The Moodle software package is [[License|Copyright © 1999 onwards, Martin Dougiamas under the GNU GPL]].<br /> <br /> ==Key Moodle Positions==<br /> <br /> * Moodle Knight - Eloy Lafuente<br /> * Translation Coordinator - Koen Roggemans<br /> * Security Officer - Petr Škoda (skodak)<br /> * Documentation Steward - [[User:Helen|Helen Foster]]<br /> * Themes Manager - Urs Hunkler<br /> * Stable Release Manager - Martin Langhoff<br /> <br /> ==Main developers==<br /> <br /> Endless thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff, Urs Hunkler'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please make your suggestions on the discussion tab for this page.<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> * used our [http://moodle.com commercial Moodle Partner services]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://download.moodle.org/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> Urs Hunkler is our Themes Manager, providing support and development.<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]<br /> <br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (''jlim AT natsoft DOT com DOT my'')<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp (''hermanV AT mindless DOT com'')<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet (''vincent AT phpconcept DOT net'')<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle (''bmatzelle AT yahoo DOT com'')<br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt (''monte AT ispi DOT net'')<br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer (''xnoguer AT rezebra DOT com'')<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan (''chris AT greatbridge DOT com'')</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4445 2006-02-02T09:23:50Z

<p>Martin: /* Overall guidance */</p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the founder, lead developer, and project manager for the whole Moodle project. Since 2005 there is a [http://moodle.com/hq/ team of people] employed over at [http://moodle.com/ Moodle HQ] in Perth, Australia helping him keep on top of things (or at least within sight of the top!).<br /> <br /> The Moodle software package is [[License|Copyright © 1999 onwards, Martin Dougiamas under the GNU GPL]].<br /> <br /> ==Key Moodle Positions==<br /> <br /> * Moodle Knight - Eloy Lafuente<br /> * Translation Coordinator - Koen Roggemans<br /> * Security Officer - Petr Škoda (skodak)<br /> * Documentation Steward - [[User:Helen|Helen Foster]]<br /> * Themes Manager - Urs Hunkler<br /> * Stable Release Manager - Martin Langhoff<br /> <br /> ==Main developers==<br /> <br /> Endless thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff, Urs Hunkler'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please make your suggestions on the discussion tab for this page.<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> * used our [http://moodle.com commercial Moodle Partner services]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://download.moodle.org/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> Urs Hunkler is our Themes Manager, providing support and development.<br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (''jlim AT natsoft DOT com DOT my'')<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp (''hermanV AT mindless DOT com'')<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet (''vincent AT phpconcept DOT net'')<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle (''bmatzelle AT yahoo DOT com'')<br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt (''monte AT ispi DOT net'')<br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer (''xnoguer AT rezebra DOT com'')<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan (''chris AT greatbridge DOT com'')<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4444 2006-02-02T09:23:00Z

<p>Martin: just some improvement - I&#039;d like this page to be comprehensive!</p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the founder, lead developer, and project manager for the whole Moodle project. Since 2005 there is a [http://moodle.com/hq/ team of people] employed over at [http://moodle.com/ Moodle HQ] helping him keep on top of things (or at least within sight of the top!).<br /> <br /> The Moodle software package is [[License|Copyright © 1999 onwards, Martin Dougiamas under the GNU GPL]].<br /> <br /> ==Key Moodle Positions==<br /> <br /> * Moodle Knight - Eloy Lafuente<br /> * Translation Coordinator - Koen Roggemans<br /> * Security Officer - Petr Škoda (skodak)<br /> * Documentation Steward - [[User:Helen|Helen Foster]]<br /> * Themes Manager - Urs Hunkler<br /> * Stable Release Manager - Martin Langhoff<br /> <br /> ==Main developers==<br /> <br /> Endless thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff, Urs Hunkler'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please make your suggestions on the discussion tab for this page.<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> * used our [http://moodle.com commercial Moodle Partner services]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://download.moodle.org/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> Urs Hunkler is our Themes Manager, providing support and development.<br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (''jlim AT natsoft DOT com DOT my'')<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp (''hermanV AT mindless DOT com'')<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet (''vincent AT phpconcept DOT net'')<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle (''bmatzelle AT yahoo DOT com'')<br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt (''monte AT ispi DOT net'')<br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer (''xnoguer AT rezebra DOT com'')<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan (''chris AT greatbridge DOT com'')<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4398 2006-02-01T03:26:48Z

<p>Martin: Copied over old roadmap from &quot;Future&quot; page and about to edit it heavily</p> <hr /> <div><br /> Here is the current roadmap of the future, though this is always subject to change depending on [http://moodle.org/donations/ sponsors] and [[Credits|developers]].<br /> <br /> == Version 1.6 ==<br /> <br /> * Blogs as the main tool for reflective activities (providing user, course and site feeds).<br /> * Database module, a general purpose tool for collaborative data entry, searching and browsing<br /> * Integration with LAMS as an activity or course format<br /> * Some better statistics<br /> * Incoming email handling<br /> * Basic Web Services API<br /> <br /> == Version 1.7 ==<br /> <br /> * My Moodle page providing a customisable overview of all courses, plus RSS feeds and so on.<br /> * Improved User Profile page, integrating Blogs, feeds etc in a semi-public home page<br /> * Preliminary support for IMS LD Level A, allowing import and export<br /> * Full support for SCORM 2004<br /> * Improved Web Services API<br /> * Integration with some repositories<br /> <br /> == Version 2.0 ==<br /> <br /> * Conditional activities, allowing dependencies and forced paths<br /> * Complete support for IMS LD standard<br /> * Improved Groups, allowing groups to be defined at site and activity level<br /> * Improved Roles implementation, allowing custom roles at site, course and activity level<br /> * Many of the main pages customisable using HTML templates.<br /> * Some exciting developments in making Moodle more network-aware, with a natural evolution of Moodle's focus on collaboration. More on this here later.<br /> <br /> [[Category:Core]]<br /> [[Category:Administrator]]<br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=FAQ&diff=4252 2006-01-29T09:24:29Z

<p>Martin: </p> <hr /> <div>#REDIRECT [[Category:FAQ]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=FAQ&diff=4251 2006-01-29T09:23:52Z

<p>Martin: </p> <hr /> <div>#REDIRECT Category:FAQ</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4187 2006-01-28T15:32:15Z

<p>Martin: /* Overall guidance */</p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the originator, lead developer, project manager, and release manager for the whole Moodle project. Since 2005 there is a team of people employed over at [http://moodle.com/ Moodle HQ] helping him keep on top of things (or at least within sight of the top!).<br /> <br /> The Moodle software package is [[License|Copyright © 1999 onwards, Martin Dougiamas under the GNU GPL]].<br /> <br /> ==Main developers==<br /> <br /> A special thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please email Martin and make your suggestions! :-)<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://moodle.org/download/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (jlim@natsoft.com.my)<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp, hermanV@mindless.com<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet &lt;vincent@phpconcept.net&gt;<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle &lt;bmatzelle@yahoo.com&gt;<br /> <br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt &lt;monte@ispi.net&gt;<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer &lt;xnoguer@rezebra.com&gt;<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan &lt;chris@greatbridge.com&gt;<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> [[Category:Moodle]]<br /> [[Category:Administrator]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4186 2006-01-28T15:31:25Z

<p>Martin: /* Overall guidance */</p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the originator, lead developer, project manager, and release manager for the whole Moodle project. Since 2005 there is a team of people employed over at [http://moodle.com/ Moodle HQ] helping him keep on top of things (or at least within sight of the top!).<br /> <br /> The Moodle software package is [[License|Copyright © 1999-4999, Moodle Pty Ltd under the GNU GPL]].<br /> <br /> ==Main developers==<br /> <br /> A special thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please email Martin and make your suggestions! :-)<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://moodle.org/download/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (jlim@natsoft.com.my)<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp, hermanV@mindless.com<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet &lt;vincent@phpconcept.net&gt;<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle &lt;bmatzelle@yahoo.com&gt;<br /> <br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt &lt;monte@ispi.net&gt;<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer &lt;xnoguer@rezebra.com&gt;<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan &lt;chris@greatbridge.com&gt;<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> [[Category:Moodle]]<br /> [[Category:Administrator]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=License&diff=4185 2006-01-28T15:24:13Z

<p>Martin: /* Copyright License for Moodle */</p> <hr /> <div>{{About Moodle}}<br /> ==Copyright License for Moodle==<br /> <br /> The ''name'' '''Moodle™''' is a registered trademark of Moodle Pty Ltd.<br /> If you are intending to use the name to promote commercial Moodle services,<br /> then you must seek permission from the Trust via the [http://moodle.com/helpdesk/ moodle.com helpdesk], in accordance with normal trademark restrictions. There are no restrictions<br /> on how you use the name in other contexts.<br /> <br /> The ''software'' '''Moodle''' is Copyright © 1999 onwards, [http://dougiamas.com/ Martin Dougiamas].<br /> <br /> This program is free software; you can redistribute it and/or modify<br /> it under the terms of the GNU General Public License as published by<br /> the Free Software Foundation; either version 2 of the License, or<br /> (at your option) any later version.<br /> <br /> This program is distributed in the hope that it will be useful,<br /> but WITHOUT ANY WARRANTY; without even the implied warranty of<br /> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the<br /> GNU General Public License below for more details.<br /> <br /> ----<br /> <br /> &lt;center&gt;GNU GENERAL PUBLIC LICENCE&lt;/center&gt;<br /> &lt;center&gt;Version 2, June 1991&lt;/center&gt;<br /> <br /> &lt;blockquote&gt;Copyright (C) 1989, 1991 Free Software Foundation, Inc.<br /> 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<br /> Everyone is permitted to copy and distribute verbatim copies<br /> of this license document, but changing it is not allowed.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;The licenses for most software are designed to take away your<br /> freedom to share and change it. By contrast, the GNU General Public<br /> License is intended to guarantee your freedom to share and change free<br /> software--to make sure the software is free for all its users. This<br /> General Public License applies to most of the Free Software<br /> Foundation's software and to any other program whose authors commit to<br /> using it. (Some other Free Software Foundation software is covered by<br /> the GNU Library General Public License instead.) You can apply it to<br /> your programs, too.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;When we speak of free software, we are referring to freedom, not<br /> price. Our General Public Licenses are designed to make sure that you<br /> have the freedom to distribute copies of free software (and charge for<br /> this service if you wish), that you receive source code or can get it<br /> if you want it, that you can change the software or use pieces of it<br /> in new free programs; and that you know you can do these things.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;To protect your rights, we need to make restrictions that forbid<br /> anyone to deny you these rights or to ask you to surrender the rights.<br /> These restrictions translate to certain responsibilities for you if you<br /> distribute copies of the software, or if you modify it.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;For example, if you distribute copies of such a program, whether<br /> gratis or for a fee, you must give the recipients all the rights that<br /> you have. You must make sure that they, too, receive or can get the<br /> source code. And you must show them these terms so they know their<br /> rights.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;We protect your rights with two steps: (1) copyright the software, and<br /> (2) offer you this license which gives you legal permission to copy,<br /> distribute and/or modify the software.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Also, for each author's protection and ours, we want to make certain<br /> that everyone understands that there is no warranty for this free<br /> software. If the software is modified by someone else and passed on, we<br /> want its recipients to know that what they have is not the original, so<br /> that any problems introduced by others will not reflect on the original<br /> authors' reputations.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Finally, any free program is threatened constantly by software<br /> patents. We wish to avoid the danger that redistributors of a free<br /> program will individually obtain patent licenses, in effect making the<br /> program proprietary. To prevent this, we have made it clear that any<br /> patent must be licensed for everyone's free use or not licensed at all.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;The precise terms and conditions for copying, distribution and<br /> modification follow.&lt;/blockquote&gt;<br /> <br /> &lt;center&gt;GNU GENERAL PUBLIC LICENSE&lt;/center&gt;<br /> &lt;center&gt;TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION&lt;/center&gt;<br /> <br /> &lt;blockquote&gt;0. This License applies to any program or other work which contains<br /> a notice placed by the copyright holder saying it may be distributed<br /> under the terms of this General Public License. The &quot;Program&quot;, below,<br /> refers to any such program or work, and a &quot;work based on the Program&quot;<br /> means either the Program or any derivative work under copyright law:<br /> that is to say, a work containing the Program or a portion of it,<br /> either verbatim or with modifications and/or translated into another<br /> language. (Hereinafter, translation is included without limitation in<br /> the term &quot;modification&quot;.) Each licensee is addressed as &quot;you&quot;.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Activities other than copying, distribution and modification are not<br /> covered by this License; they are outside its scope. The act of<br /> running the Program is not restricted, and the output from the Program<br /> is covered only if its contents constitute a work based on the<br /> Program (independent of having been made by running the Program).<br /> Whether that is true depends on what the Program does.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;1. You may copy and distribute verbatim copies of the Program's<br /> source code as you receive it, in any medium, provided that you<br /> conspicuously and appropriately publish on each copy an appropriate<br /> copyright notice and disclaimer of warranty; keep intact all the<br /> notices that refer to this License and to the absence of any warranty;<br /> and give any other recipients of the Program a copy of this License<br /> along with the Program.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;You may charge a fee for the physical act of transferring a copy, and<br /> you may at your option offer warranty protection in exchange for a fee.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;2. You may modify your copy or copies of the Program or any portion<br /> of it, thus forming a work based on the Program, and copy and<br /> distribute such modifications or work under the terms of Section 1<br /> above, provided that you also meet all of these conditions:&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;a) You must cause the modified files to carry prominent notices<br /> stating that you changed the files and the date of any change.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;b) You must cause any work that you distribute or publish, that in<br /> whole or in part contains or is derived from the Program or any<br /> part thereof, to be licensed as a whole at no charge to all third<br /> parties under the terms of this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;c) If the modified program normally reads commands interactively<br /> when run, you must cause it, when started running for such<br /> interactive use in the most ordinary way, to print or display an<br /> announcement including an appropriate copyright notice and a<br /> notice that there is no warranty (or else, saying that you provide<br /> a warranty) and that users may redistribute the program under<br /> these conditions, and telling the user how to view a copy of this<br /> License. (Exception: if the Program itself is interactive but<br /> does not normally print such an announcement, your work based on<br /> the Program is not required to print an announcement.)&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;These requirements apply to the modified work as a whole. If<br /> identifiable sections of that work are not derived from the Program,<br /> and can be reasonably considered independent and separate works in<br /> themselves, then this License, and its terms, do not apply to those<br /> sections when you distribute them as separate works. But when you<br /> distribute the same sections as part of a whole which is a work based<br /> on the Program, the distribution of the whole must be on the terms of<br /> this License, whose permissions for other licensees extend to the<br /> entire whole, and thus to each and every part regardless of who wrote it.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Thus, it is not the intent of this section to claim rights or contest<br /> your rights to work written entirely by you; rather, the intent is to<br /> exercise the right to control the distribution of derivative or<br /> collective works based on the Program.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;In addition, mere aggregation of another work not based on the Program<br /> with the Program (or with a work based on the Program) on a volume of<br /> a storage or distribution medium does not bring the other work under<br /> the scope of this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;3. You may copy and distribute the Program (or a work based on it,<br /> under Section 2) in object code or executable form under the terms of<br /> Sections 1 and 2 above provided that you also do one of the following:&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;a) Accompany it with the complete corresponding machine-readable<br /> source code, which must be distributed under the terms of Sections<br /> 1 and 2 above on a medium customarily used for software interchange; or,&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;b) Accompany it with a written offer, valid for at least three<br /> years, to give any third party, for a charge no more than your<br /> cost of physically performing source distribution, a complete<br /> machine-readable copy of the corresponding source code, to be<br /> distributed under the terms of Sections 1 and 2 above on a medium<br /> customarily used for software interchange; or,&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;c) Accompany it with the information you received as to the offer<br /> to distribute corresponding source code. (This alternative is<br /> allowed only for noncommercial distribution and only if you<br /> received the program in object code or executable form with such<br /> an offer, in accord with Subsection b above.)&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;The source code for a work means the preferred form of the work for<br /> making modifications to it. For an executable work, complete source<br /> code means all the source code for all modules it contains, plus any<br /> associated interface definition files, plus the scripts used to<br /> control compilation and installation of the executable. However, as a<br /> special exception, the source code distributed need not include<br /> anything that is normally distributed (in either source or binary<br /> form) with the major components (compiler, kernel, and so on) of the<br /> operating system on which the executable runs, unless that component<br /> itself accompanies the executable.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;If distribution of executable or object code is made by offering<br /> access to copy from a designated place, then offering equivalent<br /> access to copy the source code from the same place counts as<br /> distribution of the source code, even though third parties are not<br /> compelled to copy the source along with the object code.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;4. You may not copy, modify, sublicense, or distribute the Program<br /> except as expressly provided under this License. Any attempt<br /> otherwise to copy, modify, sublicense or distribute the Program is<br /> void, and will automatically terminate your rights under this License.<br /> However, parties who have received copies, or rights, from you under<br /> this License will not have their licenses terminated so long as such<br /> parties remain in full compliance.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;5. You are not required to accept this License, since you have not<br /> signed it. However, nothing else grants you permission to modify or<br /> distribute the Program or its derivative works. These actions are<br /> prohibited by law if you do not accept this License. Therefore, by<br /> modifying or distributing the Program (or any work based on the<br /> Program), you indicate your acceptance of this License to do so, and<br /> all its terms and conditions for copying, distributing or modifying<br /> the Program or works based on it.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;6. Each time you redistribute the Program (or any work based on the<br /> Program), the recipient automatically receives a license from the<br /> original licensor to copy, distribute or modify the Program subject to<br /> these terms and conditions. You may not impose any further<br /> restrictions on the recipients' exercise of the rights granted herein.<br /> You are not responsible for enforcing compliance by third parties to<br /> this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;7. If, as a consequence of a court judgment or allegation of patent<br /> infringement or for any other reason (not limited to patent issues),<br /> conditions are imposed on you (whether by court order, agreement or<br /> otherwise) that contradict the conditions of this License, they do not<br /> excuse you from the conditions of this License. If you cannot<br /> distribute so as to satisfy simultaneously your obligations under this<br /> License and any other pertinent obligations, then as a consequence you<br /> may not distribute the Program at all. For example, if a patent<br /> license would not permit royalty-free redistribution of the Program by<br /> all those who receive copies directly or indirectly through you, then<br /> the only way you could satisfy both it and this License would be to<br /> refrain entirely from distribution of the Program.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;If any portion of this section is held invalid or unenforceable under<br /> any particular circumstance, the balance of the section is intended to<br /> apply and the section as a whole is intended to apply in other<br /> circumstances.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;It is not the purpose of this section to induce you to infringe any<br /> patents or other property right claims or to contest validity of any<br /> such claims; this section has the sole purpose of protecting the<br /> integrity of the free software distribution system, which is<br /> implemented by public license practices. Many people have made<br /> generous contributions to the wide range of software distributed<br /> through that system in reliance on consistent application of that<br /> system; it is up to the author/donor to decide if he or she is willing<br /> to distribute software through any other system and a licensee cannot<br /> impose that choice.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;This section is intended to make thoroughly clear what is believed to<br /> be a consequence of the rest of this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;8. If the distribution and/or use of the Program is restricted in<br /> certain countries either by patents or by copyrighted interfaces, the<br /> original copyright holder who places the Program under this License<br /> may add an explicit geographical distribution limitation excluding<br /> those countries, so that distribution is permitted only in or among<br /> countries not thus excluded. In such case, this License incorporates<br /> the limitation as if written in the body of this License.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;9. The Free Software Foundation may publish revised and/or new versions<br /> of the General Public License from time to time. Such new versions will<br /> be similar in spirit to the present version, but may differ in detail to<br /> address new problems or concerns.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;Each version is given a distinguishing version number. If the Program<br /> specifies a version number of this License which applies to it and &quot;any<br /> later version&quot;, you have the option of following the terms and conditions<br /> either of that version or of any later version published by the Free<br /> Software Foundation. If the Program does not specify a version number of<br /> this License, you may choose any version ever published by the Free Software<br /> Foundation.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;10. If you wish to incorporate parts of the Program into other free<br /> programs whose distribution conditions are different, write to the author<br /> to ask for permission. For software which is copyrighted by the Free<br /> Software Foundation, write to the Free Software Foundation; we sometimes<br /> make exceptions for this. Our decision will be guided by the two goals<br /> of preserving the free status of all derivatives of our free software and<br /> of promoting the sharing and reuse of software generally.&lt;/blockquote&gt;<br /> <br /> &lt;center&gt;NO WARRANTY&lt;/center&gt;<br /> <br /> &lt;blockquote&gt;11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY<br /> FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN<br /> OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES<br /> PROVIDE THE PROGRAM &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED<br /> OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF<br /> MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS<br /> TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE<br /> PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,<br /> REPAIR OR CORRECTION.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING<br /> WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR<br /> REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,<br /> INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING<br /> OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED<br /> TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY<br /> YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER<br /> PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE<br /> POSSIBILITY OF SUCH DAMAGES.&lt;/blockquote&gt;<br /> <br /> &lt;blockquote&gt;END OF TERMS AND CONDITIONS&lt;/blockquote&gt;<br /> <br /> [[Category:Moodle]]<br /> [[Category:Administrator]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Features&diff=4184 2006-01-28T15:21:29Z

<p>Martin: </p> <hr /> <div>{{About Moodle}}<br /> Moodle is an active and evolving product. This page lists just some of the many features it contains:<br /> <br /> == Overall design ==<br /> <br /> * Promotes a social constructionist pedagogy (collaboration, activities, critical reflection, etc)<br /> * Suitable for 100% online classes as well as supplementing face-to-face learning<br /> * Simple, lightweight, efficient, compatible, low-tech browser interface<br /> * Easy to install on almost any platform that supports PHP. Requires only one database (and can share it).<br /> * Full database abstraction supports all major brands of database (except for initial table definition)<br /> * Course listing shows descriptions for every course on the server, including accessibility to guests.<br /> * Courses can be categorised and searched - one Moodle site can support thousands of courses<br /> * Emphasis on strong security throughout. Forms are all checked, data validated, cookies encrypted etc<br /> * Most text entry areas (resources, forum postings etc) can be edited using an embedded WYSIWYG HTML editor<br /> <br /> == Site management ==<br /> <br /> * Site is managed by an admin user, defined during setup<br /> * Plug-in &quot;themes&quot; allow the admin to customise the site colours, fonts, layout etc to suit local needs<br /> * Plug-in activity modules can be added to existing Moodle installations<br /> * Plug-in language packs allow full localisation to any language. These can be edited using a built-in web-based editor. Currently there are language packs for over [http://download.moodle.org/lang/ 70 languages].<br /> * The code is clearly-written PHP under a GPL license - easy to modify to suit your needs<br /> <br /> == User management ==<br /> <br /> * Goals are to reduce admin involvement to a minimum, while retaining high security<br /> * Supports a range of authentication mechanisms through plug-in authentication modules, allowing easy integration with existing systems.<br /> * Standard email method: students can create their own login accounts. Email addresses are verified by confirmation.<br /> * LDAP method: account logins can be checked against an LDAP server. Admin can specify which fields to use.<br /> * IMAP, POP3, NNTP: account logins are checked against a mail or news server. SSL, certificates and TLS are supported.<br /> * External database: any database containing at least two fields can be used as an external authentication source.<br /> * Each person requires only one account for the whole server - each account can have different access<br /> * An admin account controls the creation of courses and creates teachers by assigning users to courses<br /> * A course creator account is only allowed to create courses and teach in them<br /> * Teachers may have editing privileges removed so that they can't modify the course (e.g. for part-time tutors)<br /> * Security - teachers can add an &quot;enrolment key&quot; to their courses to keep out non-students. They can give out this key face-to-face or via personal email etc<br /> * Teachers can enrol students manually if desired<br /> * Teachers can unenrol students manually if desired, otherwise they are automatically unenrolled after a certain period of inactivity (set by the admin)<br /> * Students are encouraged to build an online profile including photos, description. Email addresses can be protected from display if required.<br /> * Every user can specify their own timezone, and every date in Moodle is translated to that timezone (e.g. posting dates, assignment due dates etc)<br /> * Every user can choose the language used for the Moodle interface (English, French, German, Spanish, Portuguese etc)<br /> <br /> == Course management ==<br /> <br /> * A full teacher has full control over all settings for a course, including restricting other teachers<br /> * Choice of course formats such as by week, by topic or a discussion-focussed social format<br /> * Flexible array of course activities - Forums, Quizzes, Glossaries, Resources, Choices, Surveys, Assignments, Chats, Workshops<br /> * Recent changes to the course since the last login can be displayed on the course home page - helps give sense of community<br /> * Most text entry areas (resources, forum postings etc) can be edited using an embedded WYSIWYG HTML editor<br /> * All grades for Forums, Quizzes and Assignments can be viewed on one page (and downloaded as a spreadsheet file)<br /> * Full user logging and tracking - activity reports for each student are available with graphs and details about each module (last access, number of times read) as well as a detailed &quot;story&quot; of each students involvement including postings etc on one page.<br /> * Mail integration - copies of forum posts, teacher feedback etc can be mailed in HTML or plain text.<br /> * Custom scales - teachers can define their own scales to be used for grading forums and assignments<br /> * Courses can be packaged as a single zip file using the Backup function. These can be restored on any Moodle server.<br /> <br /> == Assignment Module ==<br /> <br /> * Assignments can be specified with a due date and a maximum grade.<br /> * Students can upload their assignments (any file format) to the server - they are date-stamped.<br /> * Late assignments are allowed, but the amount of lateness is shown clearly to the teacher<br /> * For each particular assignment, the whole class can be assessed (grade and comment) on one page in one form.<br /> * Teacher feedback is appended to the assignment page for each student, and notification is mailed out.<br /> * The teacher can choose to allow resubmission of assignments after grading (for regrading)<br /> <br /> == Chat Module ==<br /> <br /> * Allows smooth, synchronous text interaction<br /> * Includes profile pictures in the chat window<br /> * Supports URLs, smilies, embedded HTML, images etc<br /> * All sessions are logged for later viewing, and these can also be made available to students<br /> <br /> == Choice Module ==<br /> <br /> * Like a poll. Can either be used to vote on something, or to get feedback from every student (eg research consent)<br /> * Teacher sees intuitive table view of who chose what<br /> * Students can optionally be allowed to see an up-to-date graph of results<br /> <br /> == Forum Module ==<br /> <br /> * Different types of forums are available, such as teacher-only, course news, open-to-all, and one-thread-per-user.<br /> * All postings have the authors photo attached.<br /> * Discussions can be viewed nested, flat or threaded, oldest or newest first.<br /> * Individual forums can be subscribed to by each person so that copies are forwarded via email, or the teacher can force subscription for all<br /> * The teacher can choose not to allow replies (eg for an announcements-only forum)<br /> * Discussion threads can be easily moved between forums by the teacher<br /> * Attached images are shown inline<br /> * If forum ratings are being used, these can be restricted to a range of dates<br /> <br /> == Quiz Module ==<br /> <br /> * Teachers can define a database of questions for re-use in different quizzes<br /> * Questions can be stored in categories for easy access, and these categories can be &quot;published&quot; to make them accessible from any course on the site.<br /> * Quizzes are automatically graded, and can be re-graded if questions are modified<br /> * Quizzes can have a limited time window outside of which they are not available<br /> * At the teacher's option, quizzes can be attempted multiple times, and can show feedback and/or correct answers<br /> * Quiz questions and quiz answers can be shuffled (randomised) to reduce cheating<br /> * Questions allow HTML and images<br /> * Questions can be imported from external text files<br /> * Quizzes can be attempted multiple times, if desired<br /> * Attempts can be cumulative, if desired, and finished over several sessions<br /> * Multiple-choice questions supporting single or multiple answers<br /> * Short Answer questions (words or phrases)<br /> * True-False questions<br /> * Matching questions<br /> * Random questions<br /> * Numerical questions (with allowable ranges)<br /> * Embedded-answer questions (cloze style) with answers within passages of text<br /> * Embedded descriptive text and graphics<br /> <br /> == Resource Module ==<br /> <br /> * Supports display of any electronic content, Word, Powerpoint, Flash, Video, Sounds etc<br /> * Files can be uploaded and managed on the server, or created on the fly using web forms (text or HTML)<br /> * External content on the web can be linked to or seamlessly included within the course interface.<br /> * External web applications can be linked in with data passed to them<br /> <br /> == Survey Module ==<br /> <br /> * Built-in surveys (COLLES, ATTLS) have been proven as instruments for analysing online classes<br /> * Online survey reports always available, including many graphs. Data is downloadable as an Excel spreadsheet or CSV text file.<br /> * Survey interface prevents partly-finished surveys.<br /> * Feedback is provided to the student of their results compared to the class averages<br /> <br /> == Workshop Module ==<br /> <br /> * Allows peer assessement of documents, and the teacher can manage and grade the assessment.<br /> * Supports a wide range of possible grading scales<br /> * Teacher can provide sample documents for students to practice grading<br /> * Very flexible with many options.<br /> <br /> [[Category:Moodle]]<br /> [[Category:Administrator]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Credits&diff=4183 2006-01-28T15:20:22Z

<p>Martin: </p> <hr /> <div>{{About Moodle}}<br /> ==Overall guidance==<br /> <br /> [http://dougiamas.com/ Martin Dougiamas] is the originator, lead developer, project manager, and release manager for the whole Moodle project. Since 2005 he has a team of people employed over at [http://moodle.com/ moodle.com] who help him out.<br /> <br /> The Moodle software package is [[License|Copyright © 1999-4999, Martin Dougiamas under the GNU GPL]].<br /> <br /> ==Main developers==<br /> <br /> A special thanks from all of us goes to those who have contributed substantial and ongoing amounts of time to writing Moodle code and helping it grow. These are people who &quot;get&quot; what developing Moodle is all about and without whom Moodle would be a far lesser thing:<br /> <br /> '''Eloy Lafuente (stronk7), Ray Kingdon, Williams Castillo, Petri Asikainen, Henrik Kaipe, Zbigniew Fiedorowicz, Gustav Delius, Thomas Robb, Janne Mikkonen, Jon Papaioannou (pj), Scott Elliott, Shane Elliott, Roberto Pinna (Bobo), Mike Churchward, Petr Škoda (skodak), Penny Leach, Martin Langhoff'''<br /> <br /> ==Other contributors==<br /> <br /> Many other people have contributed (and are still contributing) with constructive discussions, support, testing and various chunks of code and documentation. This list is long and always changing, but some names include (in the order they were added):<br /> <br /> '''Peter C. Taylor, Art Lader, Matt Hope, Tom Murdock, Sébastien Namèche, James Miller, Dustin Rue, Holger Schadeck, Giovanni Tummarello, John Windmueller, Sean Keogh, Mitsuhiro Yoshida, Greg Barnett, Mark Kimes, Mary Hunter, Russell Jungwirth, Przemyslaw Stencel, John &quot;Captain&quot; Eyre, Paula Edmiston, Howard Miller, Claudio Tavares, P. Timothy Ervin, Bob Calder, Ursula Raab, David Delgado, Mad Alex, Gaëtan Frenoy, Bernard Boucher, Bryan Williams, Rob Butner, Koen Roggemans, David Scotson, Torsten Anderson, Eamon Costello, Hannes Gassert, Andrew Walker.'''<br /> <br /> Sorry if we've forgotten to include your name here - the Moodle community is large and active so this list is difficult to maintain! Please email Martin and make your suggestions! :-)<br /> <br /> Thanks also to everyone of you who have<br /> * donated via the [http://moodle.org/donations Donations page],<br /> * contributed to the [http://moodle.org/bugs bug tracker], and<br /> * participated in the [http://moodle.org/community Moodle Community]<br /> <br /> ==Translators==<br /> <br /> One of Moodle's strengths is the number of translations it has. Each translation takes many hours of work, as there are over 1000 phrases to translate (plus hundreds of help files!). Many of the languages have more than one contributor, sometimes working together and sometimes working serially.<br /> <br /> Maintaining a list of all these wonderful people is too difficult, so please look at the [http://moodle.org/download/lang/ Language download page] for names and details.<br /> <br /> The Translation Coordinator is Koen Roggemans (translation@moodle.org).<br /> <br /> ==Themes==<br /> <br /> Themes give Moodle sites some colour and life. Here are all the themes carried as part of the Moodle 1.5 distribution, along with their authors:<br /> <br /> * '''standard''' by Martin Dougiamas<br /> * '''orangewhite''' and '''orangewhitepda''' by Urs Hunkler [http://www.unodo.de/ unodo]<br /> * '''oceanblue''' by Mitsuhiro Yoshida http://mitstek.com<br /> * '''cornflower''' by Thomas Murdock http://sand-paper.org<br /> * '''formal_white''' by Andrea Bicciolo<br /> * '''metal''' by A. Chavan (updated for Moodle 1.5 by Martin Dougiamas)<br /> * '''wood''' by Eloy Lafuente<br /> <br /> ==Moodle libraries==<br /> <br /> Some of Moodle's libraries were written by other people, and are being redistributed as part of Moodle under their respective open source licenses that thankfully allow us to do so. My thanks go out to the authors of all these excellent products - without them Moodle would be missing important functionality. Copyright information for each package is included below:<br /> <br /> <br /> '''ADOdb''' - lib/adodb<br /> <br /> Database abstraction library for MySQL, PostgreSQL, MSSQL, Oracle, Interbase, Foxpro, Access, ADO, Sybase, DB2 and ODBC.<br /> <br /> Version: 4.50<br /> <br /> Copyright © 2000-2004 John Lim (jlim@natsoft.com.my)<br /> <br /> License: Dual LGPL and BSD-style<br /> <br /> URL: http://adodb.sourceforge.net<br /> <br /> <br /> '''Graph Class''' - lib/graphlib.php<br /> <br /> Class to draw line, point, bar, and area graphs, including numeric x-axis and double y-axis.<br /> <br /> Version: 1.6.3 (with modifications)<br /> <br /> Copyright © 2000 Herman Veluwenkamp, hermanV@mindless.com<br /> <br /> License: LGPL<br /> <br /> <br /> '''html2text''' - lib/html2text.php<br /> <br /> PHP script to convert HTML into an approximate text equivalent<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Mark Wilton-Jones<br /> <br /> License: HowToCreate script license with written permission<br /> <br /> URL: http://www.howtocreate.co.uk/php/<br /> <br /> <br /> '''htmlArea''' - lib/editor<br /> <br /> Javascript/HTML script to put a GUI editor in textareas on Internet Explorer and Mozilla<br /> <br /> Version: 3.0 beta (with modifications)<br /> <br /> Copyright © 2002 interactivetools.com, inc.<br /> <br /> License: htmlArea License (based on BSD license)<br /> <br /> <br /> '''IP-Atlas''' - lib/ipatlas<br /> <br /> PHP scripts to show the location of an IP address on a map.<br /> <br /> Version: 1.0 (with modifications)<br /> <br /> Copyright © 2002 Ivan Kozik<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.xpenguin.com/ip-atlas.php<br /> <br /> <br /> '''kses''' - lib/kses.php<br /> <br /> HTML/XHTML filter that only allows some elements and attributes<br /> <br /> Version: 0.2.2<br /> <br /> Copyright © 2002, 2003, 2005 Ulf Harnhammar<br /> <br /> License: GNU GPL<br /> <br /> URL: http://sourceforge.net/projects/kses<br /> <br /> <br /> '''mimeTeX''' - filter/tex<br /> <br /> Compiled C program to convert TeX into GIFs<br /> <br /> Version: 1.4<br /> <br /> Copyright © 2002-2004 John Forkosh Associates, Inc<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.forkosh.com/mimetex.html<br /> <br /> URL: http://moodle.org/download/mimetex<br /> <br /> <br /> '''mp3player''' - lib/mp3player<br /> <br /> Flash movie to play streaming MP3s<br /> <br /> Copyright © 2005 Andrew Walker<br /> <br /> License: GNU GPL<br /> <br /> <br /> '''overlibmws''' - lib/overlib.js<br /> <br /> Javascript library to enable DHTML popups, floating windows, events etc<br /> <br /> Version: July 2004<br /> <br /> Copyright © 2002-2004 Foteos Macrides<br /> <br /> Copyright © 1998-2004 Erik Bosrup<br /> <br /> License: Artistic Open Source License<br /> <br /> URL: http://www.macridesweb.com/oltest/<br /> <br /> <br /> '''PclZip''' - lib/pclzip<br /> <br /> Class to create, manage and unpack zip files.<br /> <br /> Version: 2.4 RC1<br /> <br /> Copyright © 2004 Vincent Blavet &lt;vincent@phpconcept.net&gt;<br /> <br /> License: GNU GPL<br /> <br /> URL: http://www.phpconcept.net<br /> <br /> <br /> '''PHP mailer''' - lib/class.phpmailer.php<br /> <br /> Class for sending email using either sendmail, PHP mail(), or SMTP. Methods are based upon the standard AspEmail(tm) classes.<br /> <br /> Version 1.71<br /> <br /> Copyright © 2003 Brent R. Matzelle &lt;bmatzelle@yahoo.com&gt;<br /> <br /> License: LGPL<br /> <br /> URL: http://phpmailer.sourceforge.net<br /> <br /> <br /> '''PHP Markdown''' - lib/markdown.php<br /> <br /> Functions to convert from the Markdown text format into clean XHTML.<br /> <br /> Version: 1.0b9 (with modifications)<br /> <br /> Copyright © 2003-2004 , John Gruber<br /> <br /> Copyright © 2004 , Michel Fortin<br /> <br /> License: LGPL<br /> <br /> URL: http://www.michelf.com/projects/php-markdown/<br /> <br /> <br /> '''Snoopy''' - lib/snoopy<br /> <br /> A PHP net client<br /> <br /> Version: 1.0<br /> <br /> Copyright © 1999-2000 Monte Ohrt &lt;monte@ispi.net&gt;<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://snoopy.sourceforge.com<br /> <br /> <br /> '''Spreadsheet::WriteExcel''' - lib/excel<br /> <br /> A library for generating Excel Spreadsheets.<br /> <br /> Version: 2002-11-28<br /> <br /> Copyright © 2002 Xavier Noguer &lt;xnoguer@rezebra.com&gt;<br /> <br /> License: GNU LGPL<br /> <br /> URL: http://jeffn.users.phpclasses.org/browse.html/package/767.html<br /> <br /> <br /> '''SMTP class''' - lib/class.smtp.php<br /> <br /> Class that can be used to connect and communicate with any SMTP server. It implements all the SMTP functions defined in RFC821 except TURN.<br /> <br /> Version: 03/26/2001<br /> <br /> Copyright © 2001 Chris Ryan &lt;chris@greatbridge.com&gt;<br /> <br /> == Documentation writers ==<br /> <br /> Documentation writing is coordinated by [[User:Helen|Helen Foster]]. We would like to thank the many people who have contributed their work to create various parts of Moodle documentation, among others: '''Przemyslaw Stencel, Matt Riordan, Bryan Williams, Ray Lawrence, Jason Cole, Darren Smith, Sylvia Maciaszczyk and Rafal Morusiewicz'''.<br /> <br /> [[Category:Moodle]]<br /> [[Category:Administrator]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Roadmap&diff=4182 2006-01-28T15:13:37Z

<p>Martin: </p> <hr /> <div>#REDIRECT [[Future]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:CVS_for_developers&diff=4161 2006-01-28T06:35:47Z

<p>Martin: /* Joining the project as a developer */</p> <hr /> <div>'''CVS''' is the Concurrent Versioning System, a commonly-used way of managing source code for large software projects. CVS keeps all versions of all files so that nothing is ever lost, and usage by different people is tracked. It also provides ways to merge code if two or more people are working on the same file. All code and all versions are stored on a central server (in the case of Moodle, at Sourceforge).<br /> <br /> If you just want to download Moodle using CVS to run a site, then you probably don't need this page - just follow the simpler CVS instructions on the [http://moodle.org/download Moodle download] page.<br /> <br /> ==Joining the project as a developer==<br /> <br /> So, you've been offered CVS write access to help us develop and maintain Moodle! [http://sourceforge.net/project/memberlist.php?group_id=30935 Welcome aboard]!<br /> <br /> To be able to write changes into [http://cvs.sourceforge.net/viewcvs.py/moodle/moodle/ Moodle's CVS archive], you first need to have an account at Sourceforge ([http://sourceforge.net/account/newuser_emailverify.php registration is free and easy]). For the examples on this page, let's assume your username is myusername and your password is mypassword.<br /> <br /> Once you have a working Sourceforge account, contact [http://moodle.com/helpdesk Martin Dougiamas] so he can set up your account with write access to particular Moodle directories.<br /> <br /> To avoid being prompted for mypassword every time you run a CVS command, follow [http://sourceforge.net/docman/display_doc.php?docid=761&amp;group_id=1 the Sourceforge directions for using authorized keys]. This step is optional, but it can make your CVS experience a lot nicer.<br /> <br /> With that done, you should have all the permissions you need, so you just need to set up your machine and download the current sources so you can start working on them.<br /> <br /> ==CVS modules==<br /> <br /> Within CVS, the word &quot;modules&quot; refers to separate collections of code. In Moodle we have the following modules within our repository:<br /> <br /> * '''moodle''' - the main Moodle source code<br /> * '''contrib''' - user contributions and other assorted code in development<br /> * '''mysql''' - a customised phpMyAdmin to plug into Moodle for database admin<br /> * '''windows-cron''' - a small package that makes cron possible on Windows systems<br /> * '''docs''' - various extra user-contributed documentation<br /> <br /> Most people are working on the existing features in the moodle module, but many are also contributing new ideas in the contrib modules. Once code reaches a certain level of maturity in the contrib area, it can be migrated over into the main moodle tree.<br /> <br /> ==Basic CVS commands==<br /> <br /> ===CVS on Unix===<br /> <br /> Sourceforge CVS uses ssh as a transport layer for security, so you will have to set a CVS_RSH environment variable in your Unix shell. It's best to put these commands in your .bashrc or .cshrc so you don't have to type it all the time:<br /> setenv CVS_RSH ssh (for csh, tcsh etc)<br /> export CVS_RSH=ssh (for sh, bash etc)<br /> <br /> Next, you can check out the latest development version of Moodle using this (all one line):<br /> cvs -z3 -d:ext:myusername@cvs.sourceforge.net:/cvsroot/moodle co moodle<br /> <br /> The command is similar for other CVS modules:<br /> cvs -z3 -d:ext:myusername@cvs.sourceforge.net:/cvsroot/moodle co contrib<br /> <br /> Don't try to do run this first CVS command over an existing moodle installation: start fresh with a new directory.<br /> <br /> Note that you will be prompted for mypassword for each command unless you set up authorized keys.<br /> <br /> Now, you should have a new 'moodle' directory. You can rename it and move it around if you like. Go into it:<br /> cd moodle<br /> <br /> All the latest Moodle files should be in there. You can now change files in your copy. To compare your files and directories against the main CVS copy on the server use cvs diff, e.g.:<br /> cvs diff -c config-dist.php<br /> cvs diff -c lang<br /> <br /> To fetch the latest updates from the server use:<br /> cvs update -dP<br /> <br /> To copy your new files back to the server you would do something like:<br /> cd lang/ca<br /> cvs commit<br /> <br /> You will be prompted to add some comments (depends on your default text editor) ... add a meaningful comment and close the editor ... the files will be sent to Sourceforge and stored. Done!<br /> <br /> To save more time you can put default arguments into a file called .cvsrc in your home directory. For example, mine contains:<br /> diff -c<br /> update -dP<br /> <br /> Try 'cvs help' for more details ...<br /> <br /> ===CVS on Windows===<br /> <br /> First, you need to download a completely fresh copy of Moodle using your developer account.<br /> <br /> 1. Get TortoiseCVS from tortoisecvs.org and install it, then reboot.<br /> <br /> 2. Find or create a new folder somewhere where you want Moodle to be downloaded to.<br /> <br /> 3. Right-mouse-click that folder and choose &quot;CVS Checkout&quot; from the menu. You should see a dialog box.<br /> <br /> 4. Copy this text into the CVSROOT field (using your own username!):<br /> <br /> :ext:myusername@cvs.sourceforge.net:/cvsroot/moodle<br /> <br /> 5. Under the &quot;Module&quot; field, type &quot;moodle&quot; to get the latest development version of Moodle, &quot;contrib&quot; to get the contributions directory, or &quot;mysql&quot; to get the MySQL Admin module.<br /> <br /> 6. Press the button: &quot;OK&quot; and everything should be downloaded.<br /> <br /> A dialog box should show all the files being downloaded, and after a while you should have a complete copy of Moodle. After this first checkout, you can fetch the latest updated files from the CVS server:<br /> <br /> # Right-mouse-click on your Moodle folder (or any file) and select &quot;CVS Update&quot;.<br /> # Sit back and watch the logs scroll by. Take note of conflicts that may occur if your local code has changes that conflict with the incoming versions - you will need to edit these files and resolve the conflicts manually.<br /> <br /> After modifying files (you will notice their icons change from green to red!), you can commit them back to the CVS server like this:<br /> <br /> # Right-mouse-click on your Moodle folder (or any file) and select &quot;CVS Commit...&quot;.<br /> # In the dialog box, type a clear description of the changes you are committing.<br /> # Click &quot;OK&quot;. Your changes will be sent to the server.<br /> <br /> ==Working with branches==<br /> <br /> This diagram shows how the main moodle module branches into different versions over time.<br /> <br /> [[Image:Cvstree.png|CVS tree]]<br /> <br /> To see all the current tags and branches that are available, use this command on any old file (such as index.php in the top moodle directory):<br /> cvs status -v index.php<br /> <br /> Some tagging guidelines:<br /> * Tag and branch names should always be all upper-case.<br /> * Tags and branches should ALWAYS be applied to the entire module (all of Moodle). Don't tag individual files or directories.<br /> * We don't allow renaming of tags because people may be relying on them, so get them right the first time!<br /> <br /> ===Trunk development===<br /> <br /> The Trunk of CVS is the main development version of Moodle. In CVS it is also known as the HEAD, or default branch.<br /> <br /> Moodle developers try to keep this stable as possible, but as it usually contains new code it probably has bugs and small instabilities.<br /> <br /> Every now and then we decide the product has enough features to make a release. At this time, the trunk is tagged with a MOODLE_XX_BETA tag (in case we ever want to roll back to that point) and a new branch is formed for the release, called MOODLE_XX_STABLE.<br /> <br /> A Beta package is also released at this point - it's for testers who don't use CVS but want to test the latest features and report bugs.<br /> <br /> ===Stable branches for each release===<br /> <br /> As soon as the stable branch MOODLE_XX_STABLE is created, development efforts will fork into two streams for a while. Some people may continue working on new features in the trunk for the next release, but most developers should be concentrating on using the current STABLE branch and fixing bugs that are found in it.<br /> <br /> You can switch your local copy of Moodle to the STABLE version using the following command in Unix from the root directory:<br /> cvs update -dP -r MOODLE_XX_STABLE<br /> <br /> After that, all the commands described above will apply to that stable version. To return to the trunk version just issue:<br /> cvs update -dPA<br /> <br /> On Windows clients you should have a menu from which you can choose the branch.<br /> <br /> Once the new STABLE branch really stabilises, a release can be declared. Packages are created for distribution and the branch will be tagged (by Martin) with a tag named: MOODLE_XXX<br /> <br /> Periodically, bug fixes in the STABLE branch should be merged into the trunk so that they become available in future versions of Moodle. A floating tag called MOODLE_XX_MERGED will be maintained to keep track of the last merge. The procedure for such a merge is as follows:<br /> <br /> 1. Get out the very latest trunk version.<br /> <br /> cvs update -dPA<br /> <br /> 2. Merge everything on the branch since the last merge, into your trunk version<br /> <br /> cvs update -kk -j MOODLE_13_MERGED -j MOODLE_13_STABLE<br /> <br /> 3. Carefully watch the update logs for conflicts, and fix every file that you see with a conflict<br /> <br /> 4. Check the merged copy back into CVS trunk version<br /> <br /> cvs commit<br /> <br /> 5. Go back to the branch version<br /> <br /> cvs update -dPr MOODLE_13_STABLE<br /> <br /> 6. Update the floating merge tag so that this process can be repeated next time<br /> <br /> cvs tag -RF MOODLE_13_MERGED<br /> <br /> Finally, the values for $version in all the Moodle version.php files within the stable branch should not be updated at all if possible (except the last digit if necessary). The reason is that someone updating from a very stable version to the next very stable version could miss database upgrades that happened on the trunk.<br /> <br /> ===Feature branches for large changes===<br /> <br /> Occasionally, there may be a very large feature that needs to be checked in so several people can work on it, but it is too unstable to be included in the main development trunk.<br /> <br /> In these cases a short-term branch can be created to work on the feature, and then merged back into the main trunk as soon as possible. An example called MOODLE_14_WIDGET branch can be seen in the above diagram.<br /> <br /> If you need to do this for your new WIDGET feature, follow these steps:<br /> <br /> 1. Discuss with other developers to make sure it's necessary!<br /> <br /> 2. Make a new tag on the trunk (for all of moodle) called MOODLE_XX_WIDGET_PRE<br /> <br /> cvs tag -R MOODLE_XX_WIDGET_PRE<br /> <br /> 3. Create your branch called MOODLE_XX_WIDGET<br /> <br /> cvs tag -Rb MOODLE_XX_WIDGET<br /> <br /> 4. Work in that branch until the feature is reasonably stable. Commit as necessary.<br /> <br /> cvs commit<br /> <br /> 5. When ready, merge the whole branch into the trunk, fix conflicts, commit it to the trunk and then abandon the branch.<br /> <br /> cvs update -dPA<br /> cvs update -kk -j MOODLE_XX_WIDGET<br /> cvs commit<br /> <br /> Good luck, be careful and have fun!<br /> <br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Development:CVS_for_developers&diff=4160 2006-01-28T06:35:13Z

<p>Martin: /* Joining the project as a developer */</p> <hr /> <div>'''CVS''' is the Concurrent Versioning System, a commonly-used way of managing source code for large software projects. CVS keeps all versions of all files so that nothing is ever lost, and usage by different people is tracked. It also provides ways to merge code if two or more people are working on the same file. All code and all versions are stored on a central server (in the case of Moodle, at Sourceforge).<br /> <br /> If you just want to download Moodle using CVS to run a site, then you probably don't need this page - just follow the simpler CVS instructions on the [http://moodle.org/download Moodle download] page.<br /> <br /> ==Joining the project as a developer==<br /> <br /> So, you've been offered CVS write access to help us develop and maintain Moodle! [http://sourceforge.net/project/memberlist.php?group_id=30935 Welcome aboard]!<br /> <br /> To be able to write changes into [http://cvs.sourceforge.net/viewcvs.py/moodle/moodle/ Moodle's CVS archive], you first need to have an account at Sourceforge ([http://sourceforge.net/account/newuser_emailverify.php registration is free and easy]). For the examples on this page, let's assume your username is myusername and your password is mypassword.<br /> <br /> Once you have a working Sourceforge account, contact [mailto:support@moodle.com Martin Dougiamas] so he can set up your account with write access to particular Moodle directories.<br /> <br /> To avoid being prompted for mypassword every time you run a CVS command, follow [http://sourceforge.net/docman/display_doc.php?docid=761&amp;group_id=1 the Sourceforge directions for using authorized keys]. This step is optional, but it can make your CVS experience a lot nicer.<br /> <br /> With that done, you should have all the permissions you need, so you just need to set up your machine and download the current sources so you can start working on them.<br /> <br /> ==CVS modules==<br /> <br /> Within CVS, the word &quot;modules&quot; refers to separate collections of code. In Moodle we have the following modules within our repository:<br /> <br /> * '''moodle''' - the main Moodle source code<br /> * '''contrib''' - user contributions and other assorted code in development<br /> * '''mysql''' - a customised phpMyAdmin to plug into Moodle for database admin<br /> * '''windows-cron''' - a small package that makes cron possible on Windows systems<br /> * '''docs''' - various extra user-contributed documentation<br /> <br /> Most people are working on the existing features in the moodle module, but many are also contributing new ideas in the contrib modules. Once code reaches a certain level of maturity in the contrib area, it can be migrated over into the main moodle tree.<br /> <br /> ==Basic CVS commands==<br /> <br /> ===CVS on Unix===<br /> <br /> Sourceforge CVS uses ssh as a transport layer for security, so you will have to set a CVS_RSH environment variable in your Unix shell. It's best to put these commands in your .bashrc or .cshrc so you don't have to type it all the time:<br /> setenv CVS_RSH ssh (for csh, tcsh etc)<br /> export CVS_RSH=ssh (for sh, bash etc)<br /> <br /> Next, you can check out the latest development version of Moodle using this (all one line):<br /> cvs -z3 -d:ext:myusername@cvs.sourceforge.net:/cvsroot/moodle co moodle<br /> <br /> The command is similar for other CVS modules:<br /> cvs -z3 -d:ext:myusername@cvs.sourceforge.net:/cvsroot/moodle co contrib<br /> <br /> Don't try to do run this first CVS command over an existing moodle installation: start fresh with a new directory.<br /> <br /> Note that you will be prompted for mypassword for each command unless you set up authorized keys.<br /> <br /> Now, you should have a new 'moodle' directory. You can rename it and move it around if you like. Go into it:<br /> cd moodle<br /> <br /> All the latest Moodle files should be in there. You can now change files in your copy. To compare your files and directories against the main CVS copy on the server use cvs diff, e.g.:<br /> cvs diff -c config-dist.php<br /> cvs diff -c lang<br /> <br /> To fetch the latest updates from the server use:<br /> cvs update -dP<br /> <br /> To copy your new files back to the server you would do something like:<br /> cd lang/ca<br /> cvs commit<br /> <br /> You will be prompted to add some comments (depends on your default text editor) ... add a meaningful comment and close the editor ... the files will be sent to Sourceforge and stored. Done!<br /> <br /> To save more time you can put default arguments into a file called .cvsrc in your home directory. For example, mine contains:<br /> diff -c<br /> update -dP<br /> <br /> Try 'cvs help' for more details ...<br /> <br /> ===CVS on Windows===<br /> <br /> First, you need to download a completely fresh copy of Moodle using your developer account.<br /> <br /> 1. Get TortoiseCVS from tortoisecvs.org and install it, then reboot.<br /> <br /> 2. Find or create a new folder somewhere where you want Moodle to be downloaded to.<br /> <br /> 3. Right-mouse-click that folder and choose &quot;CVS Checkout&quot; from the menu. You should see a dialog box.<br /> <br /> 4. Copy this text into the CVSROOT field (using your own username!):<br /> <br /> :ext:myusername@cvs.sourceforge.net:/cvsroot/moodle<br /> <br /> 5. Under the &quot;Module&quot; field, type &quot;moodle&quot; to get the latest development version of Moodle, &quot;contrib&quot; to get the contributions directory, or &quot;mysql&quot; to get the MySQL Admin module.<br /> <br /> 6. Press the button: &quot;OK&quot; and everything should be downloaded.<br /> <br /> A dialog box should show all the files being downloaded, and after a while you should have a complete copy of Moodle. After this first checkout, you can fetch the latest updated files from the CVS server:<br /> <br /> # Right-mouse-click on your Moodle folder (or any file) and select &quot;CVS Update&quot;.<br /> # Sit back and watch the logs scroll by. Take note of conflicts that may occur if your local code has changes that conflict with the incoming versions - you will need to edit these files and resolve the conflicts manually.<br /> <br /> After modifying files (you will notice their icons change from green to red!), you can commit them back to the CVS server like this:<br /> <br /> # Right-mouse-click on your Moodle folder (or any file) and select &quot;CVS Commit...&quot;.<br /> # In the dialog box, type a clear description of the changes you are committing.<br /> # Click &quot;OK&quot;. Your changes will be sent to the server.<br /> <br /> ==Working with branches==<br /> <br /> This diagram shows how the main moodle module branches into different versions over time.<br /> <br /> [[Image:Cvstree.png|CVS tree]]<br /> <br /> To see all the current tags and branches that are available, use this command on any old file (such as index.php in the top moodle directory):<br /> cvs status -v index.php<br /> <br /> Some tagging guidelines:<br /> * Tag and branch names should always be all upper-case.<br /> * Tags and branches should ALWAYS be applied to the entire module (all of Moodle). Don't tag individual files or directories.<br /> * We don't allow renaming of tags because people may be relying on them, so get them right the first time!<br /> <br /> ===Trunk development===<br /> <br /> The Trunk of CVS is the main development version of Moodle. In CVS it is also known as the HEAD, or default branch.<br /> <br /> Moodle developers try to keep this stable as possible, but as it usually contains new code it probably has bugs and small instabilities.<br /> <br /> Every now and then we decide the product has enough features to make a release. At this time, the trunk is tagged with a MOODLE_XX_BETA tag (in case we ever want to roll back to that point) and a new branch is formed for the release, called MOODLE_XX_STABLE.<br /> <br /> A Beta package is also released at this point - it's for testers who don't use CVS but want to test the latest features and report bugs.<br /> <br /> ===Stable branches for each release===<br /> <br /> As soon as the stable branch MOODLE_XX_STABLE is created, development efforts will fork into two streams for a while. Some people may continue working on new features in the trunk for the next release, but most developers should be concentrating on using the current STABLE branch and fixing bugs that are found in it.<br /> <br /> You can switch your local copy of Moodle to the STABLE version using the following command in Unix from the root directory:<br /> cvs update -dP -r MOODLE_XX_STABLE<br /> <br /> After that, all the commands described above will apply to that stable version. To return to the trunk version just issue:<br /> cvs update -dPA<br /> <br /> On Windows clients you should have a menu from which you can choose the branch.<br /> <br /> Once the new STABLE branch really stabilises, a release can be declared. Packages are created for distribution and the branch will be tagged (by Martin) with a tag named: MOODLE_XXX<br /> <br /> Periodically, bug fixes in the STABLE branch should be merged into the trunk so that they become available in future versions of Moodle. A floating tag called MOODLE_XX_MERGED will be maintained to keep track of the last merge. The procedure for such a merge is as follows:<br /> <br /> 1. Get out the very latest trunk version.<br /> <br /> cvs update -dPA<br /> <br /> 2. Merge everything on the branch since the last merge, into your trunk version<br /> <br /> cvs update -kk -j MOODLE_13_MERGED -j MOODLE_13_STABLE<br /> <br /> 3. Carefully watch the update logs for conflicts, and fix every file that you see with a conflict<br /> <br /> 4. Check the merged copy back into CVS trunk version<br /> <br /> cvs commit<br /> <br /> 5. Go back to the branch version<br /> <br /> cvs update -dPr MOODLE_13_STABLE<br /> <br /> 6. Update the floating merge tag so that this process can be repeated next time<br /> <br /> cvs tag -RF MOODLE_13_MERGED<br /> <br /> Finally, the values for $version in all the Moodle version.php files within the stable branch should not be updated at all if possible (except the last digit if necessary). The reason is that someone updating from a very stable version to the next very stable version could miss database upgrades that happened on the trunk.<br /> <br /> ===Feature branches for large changes===<br /> <br /> Occasionally, there may be a very large feature that needs to be checked in so several people can work on it, but it is too unstable to be included in the main development trunk.<br /> <br /> In these cases a short-term branch can be created to work on the feature, and then merged back into the main trunk as soon as possible. An example called MOODLE_14_WIDGET branch can be seen in the above diagram.<br /> <br /> If you need to do this for your new WIDGET feature, follow these steps:<br /> <br /> 1. Discuss with other developers to make sure it's necessary!<br /> <br /> 2. Make a new tag on the trunk (for all of moodle) called MOODLE_XX_WIDGET_PRE<br /> <br /> cvs tag -R MOODLE_XX_WIDGET_PRE<br /> <br /> 3. Create your branch called MOODLE_XX_WIDGET<br /> <br /> cvs tag -Rb MOODLE_XX_WIDGET<br /> <br /> 4. Work in that branch until the feature is reasonably stable. Commit as necessary.<br /> <br /> cvs commit<br /> <br /> 5. When ready, merge the whole branch into the trunk, fix conflicts, commit it to the trunk and then abandon the branch.<br /> <br /> cvs update -dPA<br /> cvs update -kk -j MOODLE_XX_WIDGET<br /> cvs commit<br /> <br /> Good luck, be careful and have fun!<br /> <br /> [[Category:Developer]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=Moodle_in_education&diff=4023 2006-01-25T08:51:49Z

<p>Martin: </p> <hr /> <div>{| width=85% align=center style=&quot;background: #F8EABA; border: 1px solid #aaa;&quot;<br /> | style=&quot;font-size: 90%; padding-right: 4px; padding-left: 4px;&quot;|<br /> '''Note for contributors:''' Design and/or style improvements to this page are welcome :-) Please add additional teacher documentation links to the See also section.<br /> |}<br /> __NOTOC__<br /> __NOEDITSECTION__<br /> {| cellpadding=&quot;1&quot; style=&quot;border: 1px solid #aaa; background: #f9f9f9; padding: 5px; margin: 5px 0 15px 0; width: 100%;&quot;<br /> |-<br /> | style=&quot;padding: 0 5px 0 5px; background:#e4e4e4;&quot; align=&quot;center&quot; | &lt;h2 style=&quot;border: 0; margin: 0&quot;&gt;Activity modules&lt;/h2&gt;<br /> |-<br /> | align=&quot;center&quot; style=&quot;font-size: 100%;&quot; | [[mod/assignment/index|Assignments]] | [[mod/chat/index|Chats]] | [[mod/choice/index|Choices]] | [[mod/forum/index|Forums]] | [[mod/glossary/index|Glossaries]] | [[mod/hotpot/index|Hot Potatoes]] | [[mod/lesson/index|Lessons]] | [[mod/quiz/index|Quizzes]] | [[mod/scorm/index|SCORM]] | [[mod/survey/index|Surveys]] | [[mod/wiki/index|Wikis]] | [[mod/workshop/index|Workshops]]<br /> |}<br /> <br /> {| cellpadding=&quot;1&quot; style=&quot;border: 1px solid #aaa; background: #f9f9f9; padding: 5px; margin: 5px 0 15px 0; width: 100%;&quot;<br /> |-<br /> | style=&quot;padding: 0 5px 0 5px; background:#e4e4e4&quot; align=&quot;center&quot; | &lt;h2 style=&quot;border: 0; margin: 0&quot;&gt;[[mod/resource/index|Resources]]&lt;/h2&gt;<br /> |-<br /> | align=&quot;center&quot; style=&quot;font-size: 100%;&quot; | [[course/mod/text|Text page]] | [[course/mod/html|Web page]] | [[course/mod/file|File or website link]] | [[course/mod/directory|Directory]] | [[course/mod/label|Label]]<br /> |}<br /> <br /> {| cellpadding=&quot;1&quot; style=&quot;border: 1px solid #aaa; background: #f9f9f9; padding: 5px; margin: 5px 0 10px 0; width: 100%;&quot;<br /> |-<br /> | style=&quot;padding: 0 5px 0 5px; background:#e4e4e4&quot; align=&quot;center&quot; | &lt;h2 style=&quot;border: 0; margin: 0&quot;&gt;[[Blocks]]&lt;/h2&gt;<br /> |-<br /> | align=&quot;center&quot; style=&quot;font-size: 100%;&quot; | [[Activities]] | [[Administration]] | [[Calendar]] | [[Courses]] | [[Course/Site Description]] | [[HTML]] | [[Latest News]] | [[Messages]] | [[Online Users]] | [[People]] | [[Quiz Results]] | [[Random Glossary Entry]] | [[Recent Activity]] | [[RSS feeds]] | [[Search Forums]] | [[Section Links]] | [[Upcoming Events]]<br /> |}<br /> <br /> == See also ==<br /> *[[course/view|The course homepage]]<br /> *[[Course sections]]<br /> *[[Formatting options]]<br /> *[[HTML in Moodle]]<br /> *[[Moodle manuals]]<br /> *[[Adding resources and activities|Adding resources and activities to your course]]<br /> <br /> [[Category:Teacher]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=View_profile&diff=4022 2006-01-25T04:43:07Z

<p>Martin: </p> <hr /> <div>==Viewing the User Profile==<br /> <br /> The user profile page gathers together all the known information about a particular user.<br /> <br /> If you are a teacher, or looking at your own profile, then you will see some extra tabs allowing you to edit the profile settings, or providing detailed report and logs about the activity of that user.</div>

Martin https://docs.moodle.org/501/en/index.php?title=View_profile&diff=4021 2006-01-25T04:30:18Z

<p>Martin: User profile</p> <hr /> <div>The user profile page gathers together all the known information about a particular user.<br /> <br /> If you are a teacher, or looking at your own profile, then you will see some extra tabs allowing you to edit the profile settings, or providing detailed report and logs about the activity of that user.</div>

Martin https://docs.moodle.org/501/en/index.php?title=MoodleDocs:Guidelines_for_contributors&diff=4020 2006-01-25T04:26:55Z

<p>Martin: </p> <hr /> <div>You are welcome to contribute to MoodleDocs. Find something that can be improved, either in content, grammar or formatting, and fix it!<br /> <br /> == Contributing to MoodleDocs ==<br /> <br /> * If you've not done so already, please [[Special:Userlogin|create an account or login]].<br /> * Please note that all contributions are released here under [http://www.gnu.org/copyleft/fdl.html GNU Free Documentation License 1.2].<br /> * Moodle 1.6 will have a button on each page that links to pages in the wiki with the same path as the pages in Moodle. You can see this already on [http://moodle.org moodle.org] in fact. &lt;!--For example, the documentation page &quot;Viewing and grading submissions&quot; explains what can be seen on the page in Moodle where the teacher can view and grade assignment submissions. The URL of that page is something like &lt;code&gt;yourmoodlesite.org/mod/assignment/submissions.php&lt;/code&gt;. When contributing to the documentation, if it contains part of a URL, say &lt;code&gt;mod/assignment/submissions&lt;/code&gt;, it means that this documentation page refers to that page.--&gt;<br /> * Please note that the [http://moodle.org/help.php?file=index.html Moodle help files] will remain in each language pack and so their text need not be included in this documentation.<br /> * You are welcome to create pages for additional documentation. Simply type &lt;code&gt;&lt;nowiki&gt;[[New page]]&lt;/nowiki&gt;&lt;/code&gt; and follow the link to start editing the new page. Please choose a short name (just one or two words) and capitalize the first word only.<br /> <br /> == See also ==<br /> <br /> * [[Documentation philosophy]]<br /> * [[Help:Editing|Editing help]]<br /> * [[Sandbox]] - for experimenting/playing ;-)<br /> <br /> == External links==<br /> * [http://demo.moodle.com/ Moodle Demo Site]<br /> <br /> [[Category:MoodleDocs]]</div>

Martin https://docs.moodle.org/501/en/index.php?title=MoodleDocs:Guidelines_for_contributors&diff=4019 2006-01-25T04:26:24Z

<p>Martin: </p> <hr /> <div>You are welcome to contribute to MoodleDocs. Find something that can be improved, either in content, grammar or formatting, and fix it!<br /> <br /> == Contributing to MoodleDocs ==<br /> <br /> * If you've not done so already, please [[Special:Userlogin|create an account or login]].<br /> * Please note that all contributions are released here under [http://www.gnu.org/copyleft/fdl.html GNU Free Documentation License 1.2].<br /> * Moodle 1.6 will have a button on each page that links to pages in the wiki with the same path as the pages in Moodle. You can see this already on [http://moodle.org] in fact. &lt;!--For example, the documentation page &quot;Viewing and grading submissions&quot; explains what can be seen on the page in Moodle where the teacher can view and grade assignment submissions. The URL of that page is something like &lt;code&gt;yourmoodlesite.org/mod/assignment/submissions.php&lt;/code&gt;. When contributing to the documentation, if it contains part of a URL, say &lt;code&gt;mod/assignment/submissions&lt;/code&gt;, it means that this documentation page refers to that page.--&gt;<br /> * Please note that the [http://moodle.org/help.php?file=index.html Moodle help files] will remain in each language pack and so their text need not be included in this documentation.<br /> * You are welcome to create pages for additional documentation. Simply type &lt;code&gt;&lt;nowiki&gt;[[New page]]&lt;/nowiki&gt;&lt;/code&gt; and follow the link to start editing the new page. Please choose a short name (just one or two words) and capitalize the first word only.<br /> <br /> == See also ==<br /> <br /> * [[Documentation philosophy]]<br /> * [[Help:Editing|Editing help]]<br /> * [[Sandbox]] - for experimenting/playing ;-)<br /> <br /> == External links==<br /> * [http://demo.moodle.com/ Moodle Demo Site]<br /> <br /> [[Category:MoodleDocs]]</div>

Martin