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

From Woozle Writes Code
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
{{fmt/title|Ferreteria v0.5 classes|{{fmt/code|ferret}} namespace}}
{{fmt/title|Ferreteria v0.5 classes|
==Classes==
<code>[[../|ferret]]\layout</code> namespace}}
* {{l/ver/class|caApp}} application class family
{| style="border: solid 1px grey; background: #eef;"
|-
| {{l/ver/class|caApp}}
|-
|
{|
|-
|
{{l/ver/class|caDynamicLink}} &rarr;<br>
{{l/ver/class|tRequiresPermit}} &rarr;
|
{{l/ver/class|cDropinLink}}
|
&rarr; {{l/ver/class|cDropinAction}}
|}
|}
==Sub-Namespaces==
==Sub-Namespaces==
* [[/layout]]
* [[/layout]]

Revision as of 15:38, 9 July 2022

Ferreteria v0.5 classes

ferret\layout namespace

caApp

caDynamicLink
tRequiresPermit

cDropinLink

cDropinAction

Sub-Namespaces

Meta: Paradigm

This is the class documentation paradigm I'm currently trying.

  • Titles for pages about classlike types (classes, traits, interfaces) should use the minimum unambiguous name. i.e. only include namespace if there's another classlike with the same name in another namespace, and include only as much of the namespace as needed to disambiguate.
  • The {{l/ver/class|<class name>}} template can be used to point to the documentation page for a classlike type.
  • If a classlike page title could refer to more than one class, there will be a disambiguation page.