World: r3wp

Short words are preferred in REBOL.

We have to type this stuff.

I find absolutely nothing confusing about facets. They are used in 
one single place in the system and they are used in hundreds of places 
inside styles as paths.

faced

 appears more to be a play on words and it should probably be replaced 
 with something else.

And technically, "attribute" is incorrect. "Attribute" means something 
that comes from the subject (is attributed to it). "Part" is right.

As long as "faced" is replaced with something specifically face-related, 
preferably with the word "face" in it, then cool.

since when has this been a requirement for anything?

faced are instance variables .. just call them locals

The currently used words for styles:

name:    ; WORD!   - style's name (identifies the style)

facets:  ; OBJECT! - the modifyable attributes of the style (properties)

draw:    ; BLOCK!  - draw block with facet words (from face and style)

actors:  ; MAP!    - face actor functions (e.g. on-click, on-resize)
options: ; OBJECT! - prototype of face/options object
parent:  ; WORD!   - parent style (if specified)

state:   ; BLOCK!  - prototype of (extensions to) face/state object
content: ; BLOCK!  - panel layout for composite styles

faced:  ; OBJECT! - prototype of face/facets (face instance facets)
about: "Not documented."

So faced isn't "locals", it's a prototype of the facet object.

Sorry, the object containing the facets.

hehe ... "the modifyable attributes of the style (properties)"

modifiable ...

about: "Not documented"  ... lol

that is soooo funny

About is the documentation of the style. Unless a derived style defines 
some documentation, it's "Not documented".

What (preferrably short) word means a prototype for a collection 
of facets? Perhaps "model"?

Graham, the word list is from the prototype, so "Not documented" 
would be accurate.

These are the words for a face instance:

style:   ; WORD!   - name of the style for this face

facets:  ; OBJECT! - properties unique to this face (from style/faced)
state:   ; OBJECT! - state variables (not properties)
gob:     ; GOB!    - graphical object(s) for this face
options: ; OBJECT! - optional facet changes as specified

; NOTE: optionally extended in face creation with:
;name    ; WORD!   - reference name
;reactors; BLOCK!  - block of user actions

; PANEL faces also add:
;grid    ; OBJECT! - layout parameters and limits
;faces   ; BLOCK!  - faces of the panel:
;triggers; BLOCK!  - triggers used by panels

template

mask

mold

Template is a good one, though it would need to be documented. Mask 
isn't quite right. Mold would be awkward because of MOLD.

about: "documentationi" would be better ...

no more confusing than 'copy or 'to in parse

well, possibly more ...

About "Documentation" would be more misleading when reading out the 
autogenerated help for the style.

You don't assign copy or to in parse to variables - they're keywords.

It's a prototype for a style. There default documentation for a style, 
so "Not documented" makes sense.

Graham, if you called it "mold" then the word 'mold would be bound 
in that object, which would make use of the function MOLD difficult 
in code that is bound to that object.

There default -> There is no default

Oh, I get it, "faced" is short for "prototype of the face visible 
properties (facets) collection". Perhaps "ideal" (in the Platonic 
sense).

The FACED block is similar to FACETS, but makes them local to each 
instance of the face. Now, they can be modified without effecting 
any other faces that are of the same CIRCLE style.

http://www.rebol.net/wiki/GUI_howto_styles

Right, I got the usage. I was just trying to find a good name.

Your "template" and "model" are the most accurate, if not specific. 
The word "ideal" would require too much explanation.

they look like local variables to me ...

on-make: [

                face/facets/area-fill: span-colors get-facet face 'area-color [2.0 
                .2]
            ]

            on-resize: [ ; arg is the size
                face/gob/size: arg
                face/facets/area-size: arg - 2
                face/facets/diameter: (min arg/y arg/x) - 5 / 2
            ]

Ah, but they're not local variables. They're the prototype for local 
variables in another object.

And facets are the visible properties, not just any locals.

The faced object is the prototype - that's what I'm trying to name.

their usage is not shown in this example

ok, try 'defaults

Right, I didn't realize at first that you were talking about facets. 
I thought you were talking about faced. Defaults are what the facets 
object in the style object is. The faced objects are the prototype 
of the specifics (non-defaults).

faced objects are -> faced object is
And it might not be an object, I don't remember.

view/no-wait [ text-list []]
crashe if you try and use the mouse to close the window down

>> w: view [ tl: text-list []]
handler added

== make gob! [offset: 569x340 size: 142x120 alpha: 0 text: "REBOL: 
untitle

>> value? 'tl
== false

so how do you access the faces ?

that's another issue to solve.

you can access them freely from other faces in the layout.

Yes ... 
and some are 

set-face and others are set ...