PrF UG meta standard class - Revision history

RichMorin at 01:29, November 14, 2008

2008-11-14T01:29:02Z

RichMorin at 19:23, October 29, 2008

2008-10-29T19:23:35Z

RichMorin at 23:58, October 24, 2008

2008-10-24T23:58:40Z

RichMorin at 18:55, October 17, 2008

2008-10-17T18:55:32Z

RichMorin at 18:55, October 17, 2008

2008-10-17T18:55:07Z

RichMorin at 19:03, October 16, 2008

2008-10-16T19:03:08Z

RichMorin: Automated import of articles

2008-10-09T09:04:17Z

Automated import of articles

New page

__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 :STANDARD-CLASS.
The slots of :STANDARD-CLASS define generic properties of the class.
For example, :NAME is a slot of type String which you use to name your class; :ROLE is a slot of type Symbol which can take the values Abstract or Concrete.

<div>[[Image:PrF_UG_meta_standard_class_editor.png|metaclasses_standard_class_editor]]</div>

Some template slots for :STANDARD-CLASS are translated to entry fields in the Class Editor.
The :NAME slot becomes the Name entry field,
while the :ROLE slot becomes the Role 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 :DIRECT-SUPERCLASSES 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 :STANDARD-CLASS,
the Class Editor itself reflects the structure and layout specified for :STANDARD-CLASS 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>

@@ Line 2: / Line 2: @@
 == Looking at :STANDARD-CLASS ==
-{{PrF_UG_TOC_meta}}<div id='prf_ug'>
+<noinclude>{{PrF_UG_TOC_meta}}<div id='prf_ug'></noinclude>
 By default, when a class is created as part of a project, {{#var:PrF}};
@@ Line 42: / Line 42: @@
-</div>
+<noinclude></div></noinclude>

@@ Line 36: / Line 36: @@
 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.
+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,
+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>

@@ Line 12: / Line 12: @@
 <div>[[Image:PrF_UG_meta_standard_class_editor.png|thumb|none|600px|
-        metaclasses_standard_class_editor]]</div>
+        :STANDARD-CLASS instance dialog]]</div>
 Some template slots for <b>:STANDARD-CLASS</b> are translated
@@ Line 21: / Line 21: @@
 it also becomes an entry field in the Class Editor.
-<div>[[Image:PrF_UG_classes_class_editor.png|
+<div>[[Image:PrF_UG_classes_class_editor.png|frame|none|
-        classes_class_editor]]</div>
+        Class Editor]]</div>
 The other slots are more complex.
@@ Line 40: / Line 40: @@
 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>

@@ Line 4: / Line 4: @@
 {{PrF_UG_TOC_meta}}<div id='prf_ug'>
-By default,
+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>.
+For example, <b>:NAME</b> is a slot of type <b>String</b> which you use to name your class;
-<div>[[Image:PrF_UG_meta_standard_class_editor.png|metaclasses_standard_class_editor]]</div>
+<div>[[Image:PrF_UG_meta_standard_class_editor.png|
-Some template slots for <b>:STANDARD-CLASS</b> are translated to entry fields in the Class Editor.
+Some template slots for <b>:STANDARD-CLASS</b> are translated
 The <b>:NAME</b> slot becomes the <b>Name</b> entry field,
 while the <b>:ROLE</b> slot becomes the <b>Role</b> menu.
@@ Line 18: / Line 21: @@
 it also becomes an entry field in the Class Editor.
-<div>[[Image:PrF_UG_classes_class_editor.png|classes_class_editor]]</div>
+<div>[[Image:PrF_UG_classes_class_editor.png|
 The other slots are more complex.
-For example,
+For example, consider the <b>:DIRECT-SUPERCLASSES</b> slot.
-consider the <b>:DIRECT-SUPERCLASSES</b> slot.
+This slot keeps track of the direct superclasses of a class
-This slot keeps track of the direct superclasses of a class by storing them as a list of instances.
+by storing them as a list of instances.
-Internal programmatic operations add
+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 this way, {{#var:PrF}} represents the structure of your project
 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.
+the Class Editor itself reflects the structure and layout specified
 If you create a new project,
-then
+then [[PrF_UG_meta_customize_editor|modify the Class Editor]] at the Forms Tab,
-[[PrF_UG_meta_customize_editor|modify the Class Editor]]
+your modifications will show up for every class, whether existing or new.
 </div>