as a registered user you have some advantages like free downloads, comments and posting on our forums, depending upon this site's configuration and options.
Forums
Documentation
MAXdev Community
|
Module Developers Guide
The MDPro module system is a work-in-progress. There are no doubt many good ideas out there that have not been incorporated into the MDPro module system, and if a developer has a request for a particular set of functionality then they can submit it to the MDPro features request list on SourceForge at the MDPro Homepage. If you have found a bug within the current module system then you can submit it to the bug list at the same address. Please note that the main requirement for the MDPro module design is stability. Due to this it is possible that your request for new or updated functionality will get refused on the grounds that it is too specific, can easily be built from core API functions, or carries out work that should rightly be done by a module. In such situations the MDPro team will always try to provide a simple alternative, but please remember that submission of a new or updated addition to the module design does not guarantee inclusion. This chapter describes the basic architecture of MDPro, explains the major parts, and contains information on the design choices made for the system. You are advised (even for performance reasons) to use the following naming convention: $name := $module_name . '_' . $real_name
Here is the grammar for the validation string:
type can be one of these values: 'num', 'string', 'stringlen', 'func' valid operators for num type are: ==, !=, <, >, <=, >= valid operators for string type are: is, contains, starts, ends, regex valid operators for stringlen are the same as num type. You can create complex validators simply by concatenating them with the logic & (AND) operator.
Consider the following example:
Consider the following example:
The MDPro module system design has been carried out by the MDPro development team to allow for the maximum flexibility to developers whilst ensuring that the module can be accessed in a generic fashion by the MDPro core, other modules, and remote systems given access through other interfaces such as XML-RPC. The main design characteristics of the module system are listed below. This chapter covers how modules interact with MDPro. The information in this chapter is correct for the 0.71 release of MDPro, for other releases please get the most recent copy of the Module Developers Guide.
There are a number of steps that need to be taken before you can start building your module. | ||||||||||||||||||||||||||||||||