The name is used to namespace the module's function by prefixing required functions with that directory name. The name given to the directory must be chosen carefully. It is up to the module developer to ensure that their module name is unique. A module should not be made available if an existing module is already being distributed under that same name. The module name, and hence the directory and function names (see below for additional details), must be unique across all possible modules. Whenever a module identifier is needed within code, it should appear in lowercase with spaces converted to underscores. Although the process of developing modules is the same for each type of module, only extra modules can be distributed separately, while core and standard modules are added to the ATutor code repository (i.e. Extra modules are stored in the mods directory and are installed and distributed independently of ATutor. Standard modules can be disabled by the administrator. Standard modules are stored in the mods/_standard subdirectory and are also made available with every release of ATutor. These modules cannot be disabled by the administrator as they are vital to ATutor's functionality. Core modules are stored in the mods/_core subdirectory and are made available with every release of ATutor. Modules are stored under ATutor's mods directory. Also see the files from other modules that operate like you expect your module to operate. A copy of the Hello World module works well as a starting point for creating a new module, since it implements (in a simple way) just about all the features found in modules. The module is found in the mods/hello_world directory. The Hello World example module is included with each ATutor distribution for developers who want to investigate how modules work. The module structure does allow for the creation of modules that run software that is not distributed under the GNU General Public License, but distributed separately under their own, perhaps commercial licenses. The intent is to allow for the development and distribution of modules independent of the ongoing development and release of ATutor. The framework defines methods for assigning privileges, backing-up and restoring content, deleting course specific content, and adding side menu blocks, student tools, course management and administrative tools, as well as public tools and other types of added functionality. ATutor Module Documentation Module Development DocumentationĪTutor 1.5.2 introduced the concept of modules, providing developers with a framework to implement additional functionality in a coherent and loosely coupled way.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |