Ferreteria/v0.5/@cls/caApp: Difference between revisions

From Woozle Writes Code
< Ferreteria‎ | v0.5‎ | @cls
Jump to navigation Jump to search
(Created page with "{{fmt/title|Ferreteria 0.5 App classes}} * '''File''': {{l/ferreteria/code|base/app.php}} ==Classes== * caApp * caAppBasic * caAppUser * caAppWeb - for now, just an alias of c...")
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{fmt/title|Ferreteria 0.5 App classes}}
{{fmt/title|Ferreteria class <code>[[../|ferret]]\caApp</code>}}
{| style="border: solid 1px grey; background: #eef;"
|-
|
{{l/ver/class|tSingletonAuto}} &rarr;
{{l/ver/class|caApp}}
&rarr; {{l/ver/class|caAppBasic}}
|}
* '''File''': {{l/ferreteria/code|base/app.php}}
* '''File''': {{l/ferreteria/code|base/app.php}}
==Classes==
* '''Class family''':
* caApp
** {{l/ver/class|caAppBasic}}
* caAppBasic
*** {{l/ver/class|caAppUser}} - application with login and account-security services
* caAppUser
**** {{l/ver/class|caAppWeb}} - just an alias for now, but use this for web apps
* caAppWeb - for now, just an alias of caAppUser
==About==
The App classes are all intended as singleton objects that guide the {{l/ver|startup}} process and determine certain other key classes to use for certain operations. Any given application will typically create its own class that inherits from one of these, that being the easiest way to ensure that required setup is taken care of.

Latest revision as of 15:29, 25 July 2022

Ferreteria class ferret\caApp

tSingletonAutocaAppcaAppBasic

About

The App classes are all intended as singleton objects that guide the startup process and determine certain other key classes to use for certain operations. Any given application will typically create its own class that inherits from one of these, that being the easiest way to ensure that required setup is taken care of.