View source for PrF UG meta standard class

__NOTOC__
== Looking at :STANDARD-CLASS ==

{{PrF_UG_TOC_meta}}<div id='prf_ug'>

By default, when a class is created as part of a project, {{#var:PrF}};
treats that class as an instance of the metaclass <b>:STANDARD-CLASS</b>.
The slots of <b>:STANDARD-CLASS</b> define generic properties of the class.
For example, <b>:NAME</b> is a slot of type <b>String</b> which you use to name your class;
<b>:ROLE</b> is a slot of type <b>Symbol</b>
which can take the values <b>Abstract</b> or <b>Concrete</b>.

<div>[[Image:PrF_UG_meta_standard_class_editor.png|thumb|none|600px|
       metaclasses_standard_class_editor]]</div>

Some template slots for <b>:STANDARD-CLASS</b> are translated
to entry fields in the Class Editor.
The <b>:NAME</b> slot becomes the <b>Name</b> entry field,
while the <b>:ROLE</b> slot becomes the <b>Role</b> menu.
When you create or attach a template slot to a metaclass,
it also becomes an entry field in the Class Editor.

<div>[[Image:PrF_UG_classes_class_editor.png|
       classes_class_editor]]</div>

The other slots are more complex.
For example, consider the <b>:DIRECT-SUPERCLASSES</b> slot.
This slot keeps track of the direct superclasses of a class
by storing them as a list of instances.
Internal programmatic operations add (delete) instances to (from)
the appropriate slot value whenever you make changes to a {{#var:PrF}} project.
In this way, {{#var:PrF}} represents the structure of your project
using its tools for storing and representing structure,
in much the same way you create the project structure.

Since any new class is by default created using <b>:STANDARD-CLASS</b>,
the Class Editor itself reflects the structure and layout specified
for <b>:STANDARD-CLASS</b> at the Forms Tab.
If you create a new project,
then [[PrF_UG_meta_customize_editor|modify the Class Editor]] at the Forms Tab,
your modifications will show up for every class, whether existing or new.

</div>