What is an application (APP)?¶
An application is the combination of a brand and model. The brand being the name of the application and the model being a specific design. Most applications have only one model, but larger applications contain many models.
Think of an application as a BMW M5, where BMW is the brand and M5 is the model. Some people might refer to the car as an M5, knowing it is made by BMW. In this system, all commands are executed by the application model identifier, therefore a BMW M5 application would command-line would start with /M5, without reference to BMW.
Example breakdown:
- BMW build cars.
- One model is the M5
- A variation of the M5 is the Turbo
- The full name of the car is BMW M5 Turbo
- The model number is BMWM5T or M5T if it is unique
- If the car was an application, commands would always start with: /M5T
- Always use CAPS for the application identifier.
Application Identifier Aliases¶
It is possible to use an alias that maps to the application identifier. In the example above, the alias might be /M5T => /M5T2. If a newer model (not version) came out, the mapping could point to the newer /M5T2 while still using the old /M5T. This is good for SEO and compatibility.
Web App Expression (wAEX)¶
The command syntax uses profile security to allow any command to execute from any application. Structure
/APP/Entity/Name --sw=value ~~sw=value
Console App Expression (cAEX)¶
Console commands are executed using scripts based on the development cycle number. The following commands are available:
file | description | example |
---|---|---|
v0.phpsh | Release level console commands. | v0.phpsh /App/Entity/Name |
v1.phpsh | Same as v0.phpsh using beta level console commands. | v1.phpsh /App/Entity/Name --acct=1000 |
v2.phpsh | Same as v0.phpsh using alpha level console comments. | v2.phpsh /App/Entity/Name --quiet |
AEX Explained¶
APP¶
The name of the application model located under the vendor/repository folder. (see "What is an Application?")
Entity¶
A type, category or unstructured name given to a command or process. Excluding the entity will execute commands under the / Application// directory, which is used for uncategorized commands within the application. You may also use an // as the entity.
Example:
/Application//Name is equivelant to /Application/_/Name
Name¶
Name of the command under the application entity.
Switches¶
Switches can be added to the wAEX or cAEX if necessary.
Switch | Description |
---|---|
--sw | Permanent switch. Remembered in the branch. |
~~sw | Process switch. Not remembered in the branch. |