What is a module?
A module is an abbreviated session (five – six weeks as opposed to a semester which usually lasts for 12-14 weeks) in which our courses are held. Each course lasts for five to six weeks and consists of fifteen instructional hours. An individual can start the program at the beginning of any module. There are six modules in each academic year.
A module is a psychological adaptation (see above). Note that this usage of the term ‘module’ differs from several of the definitions of ‘module’ used by cognitive psychologists. For those familiar with the ‘modularity’ debate, I will make one brief comment: Fodor distinguishes between cognitive modularity with, and without, information encapsulation (Fodor 2000, p. 56-58). If, when performing the computations, modules only have access to information stored in the module itself, and cannot access information in other modules, the module is said to be informationally encapsulated. As a concept, information encapsulation is so unhelpful that one wonders whether its importation from computer science into cognitive science was botched. Why, except when processing speed or perhaps robustness is exceptionally important, should modules not have access to data in other modules?
A module is an essential part of any Xoops website. After a first installation of Xoops, many users look at their home page and feel a little upset. “Is that it …? a boring page with little on it except a login box and a banner. Don’t be disappointed, this is a purposeful move so that each user can choose how to build their own website and design the structure content and style to their own preferences. In fact all Xoops sites are installed with one essential and sophisticated module, the System module. What looks very empty on the outside hides an internal core of powerful features just waiting to be unleased. Now this is where your own preferences for the site can begin. Modules form the structure of the site, but they display the content. So, when installing modules, it’s a good idea to have some basic plan about what your website will be like. Modules are usually built to work in conjunction with the Xoops system module and other core functions.
A module is a psychological adaptation (see above). Note that this usage of the term ‘module’ differs from several of the definitions of ‘module’ used by cognitive psychologists. For those familiar with the ‘modularity’ debate, I will make one brief comment: Fodor distinguishes between cognitive modularity with, and without, information encapsulation (Fodor 2000, p. 56-58). If, when performing the computations, modules only have access to information stored in the module itself, and cannot access information in other modules, the module is said to be informationally encapsulated. As a concept, information encapsulation is so unhelpful that one wonders whether its importation from computer science into cognitive science was botched. Why, except when processing speed or perhaps robustness is exceptionally important, should modules not have access to data in other modules? Most modules should communicate readily with numerous (though by no means all) other modules when performing their fu
A module is a third-party platform or plugin that works with the JW Player in some way. It doesn’t work “within” the player like a Skin or a Plugin. Instead, it serves as a bridge between the JW Player and other applications, platforms, and CMSs. For example, content management systems like Joomla or WordPress that incorporate the JW Player into their platforms are considered modules.
