Commands
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. BMW is the brand or container of all BMW models.
Another example is Apple iPhone. Apple makes many different models of iPhone, iMac, Macbook, Macbook Pro, iPad, etc. The models of each are giving a identifier like iPhone XS. We would call Apple iPhone XS or possibly iPhone XS the application, considering everyone knows iPhone is made by Apple.
This is very important to understand because all comands are executed by application, which is actually the model identifier given to the application. Don’t confuse models with versions; each model has its own versioning.
Example of how it works:
- Software Publishing Group created an application.
- The application base name is: Daily Diary
- The model: Series IV
- The full name of the application: Daily Diary Series IV by Software Publishing Group
- The model number might be DDS4
- The application identifier would always start with: /DDS4
- This syntax must be unique on the server running application so it might make sense to prefix any application identifier with SPG, it might be /SPGDD4
- 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 /DailyDiary => /SPGDD4. If a newer model Series V came out, the mapping could point to /SPGDD5 without changing /DailyDiary. This is good for SEO.
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. |