Programming without global constants and variables.
In the medium term it is planned to build up a 'Registry' in WebsiteBaker. Until this is ready, the class 'WbAdaptor' will take over this task. First of all, the class provides properties that are more or less identical with the previous constants. At the same time, also the old constants are -still- available unchanged for old code, however they may no longer be used for new or revised Code!
Global constants show a fundamental characteristic which very much supports 'lazy' programming: Once declared, they are directly available at absolutely any location of the source code requiring no additional expense. Visibility and scope don't play any role for them. Absolutely 'lazy' programmers abuse constants as variables that, eventually set in sequence, and then are available at no extra transfer in the following functions. The apparent advantages, however, also face significant disadvantages. Security-critical data are never stored in constants. The best negative example in previous WB versions are the credentials for access to the database, which were available in each droplet, each piece of dynamic code of a template etc., absolutely freely accessible for everyone.
Global constants (as well as global variables), used within classes, break up their clear encapsulation and can prevent the reusability of the code. See 'Basics of object-oriented programming'.
Global constants are, as has long been stated, from this version on deprecated, that is undesirable. See: Deprecated-List Entry 10 from 12.2013.
Of course, discarding all previous constants without any replacement is clearly not a feasible approach. That's simply impossible. At least in the first step, the class 'WbAdaptor' makes properties available that are similar to the previous constants.
A significant change has arisen about the spelling of the identifier:
The identifiers have been written entirely in capital letters and separated several individual words with an underscore _, the new identifiers however still consist of the same sub strings, but now they are written in 'StudlyCaps' notation without delimiters between words.
Example: DEFAULT_TEMPLATE becomes DefaultTemplate now
The transformation of the identifier is performed automatically when reading in the class WbAdaptor.
So far so good. To make it not too simple, for about a dozen former constants the identifier (key) and also partially the content has completely changed!!
List of new identifiers and examples of the current contents.
(note: this list is not complete!)
|old constant||new key||content (example)|
|NEW||Db||the current object for accessing the database|
|NEW||Trans||the current translation object|
|NEW||App||the current application/core object|
|NEW||PageId||the ID of the current page|
|NEW||BlockId||the ID of the current block|
|NEW||SectionId||the ID of the current section|
|WB_URL||AppUrl||http: ⁄⁄ example.com/wb/|
alternatively, in Windows ('c:/var/www/httpdocs/wb/')
|ADMIN_URL||AcpUrl||http: ⁄⁄ example.com/wb/admin/|
|NEW||TemplateUrl||http: ⁄⁄ example.com/wb/templates/MyTemplate/|
|STRING_DIR_MODE||DirModeString||rwxrwxr-x (textual representation, corresponds to 0775 octal)|
|OCTAL_DIR_MODE||DirModeOctal||509 (stored integer, corresponds to 0775 written in octal)|
|STRING_FILE_MODE||FileModeString||rw-rw-r-- (textual representation, corresponds to 0664 octal)|
|OCTAL_FILE_MODE||FileModeOctal||436 (stored integer, corresponds to 0664 written in octal)|
Who looks attentively at the list, will recognize a few new laws:
The string WB_ became App (has nothing to do with any of these App Stores !!), it's just the original abbreviation for application ⇒ program.
The string ADMIN_ became Acp which is the abbreviation for Admin Control Panel, because the functions and names 'backend' and 'admin tools' will be abolished or replaced in one of the subsequent versions.
Regardless of the changed prefixes, the following rules apply for extensions:
for all statements in common the following rules apply:
OLD ⇒ NEW example:
|old||WB_URL||http: ⁄⁄ example.com/wb|
|new||AppUrl||http: ⁄⁄ example.com/wb/|
|old||TEMPLATE_DIR||http: ⁄⁄ example.com/wb/templates/MyTemplate|
This class can be reached from anywhere. It is sufficient to import that only existing active instance of the class with
<php> $oReg = WbAdaptor::getInstance(); </php> to import into the current scope. But even better is the use of dependency injection, i.e. the transfer of the instance from outside to the function or class.
It is strongly recommended that the identifier $oReg is used for the instance of the WbAdaptor object in order to achieve a better and consistent readability of all program components.
Also the request of the individual values quite straightforward:
<php> echo $oReg→TemplateDir.'images/logo.png'; </php>
What is not visible from the outside, the fact is that all retrievable values are stored in two basic groups:
The system values are protected and can not be overridden by Request values or anything else.