World: r3wp

Is there an easier way to do this than this?

    code-text-list: tight [

        about: "List of selectable text lines with scrollbar using a monospaced 
        font."
        facets: [
            max-size: 150x3000
        ]
        options: [
            list-data: [block!]
        ]
        content: [

            text-list-box :list-data :area-color options [ text-style: 'code 
            ]
            scroller
        ]
        actors: [
            on-init: [
                if select face 'reactors [
                    extend face/faces/1 'reactors face/reactors
                ]
            ]
            on-set: [
                set-face/list face/faces/1 arg
            ]
            on-get: [
                get-face face/faces/1
            ]
        ]
    ]

I think it's a little potentially confusing that 'options in a style 
refers to the stuff that follows a widget when it is used, but the 
options keyword following the widget refers to the facets

parameters
 instead?

sure

pars or params, to make it shorter to write :-)

you wouldn't need to write it often!  Unless you were writing a lot 
of your own styles

so, above it would be 

parameters: [
	list-data: [block!]
]

vocabulary shows that param, parm, is a regular english word ....

but other than that, anything is ok with me :-)

so that you know that text-list takes a block

Make sure the word is not used anywhere else in the R3 GUI. Font 
changing, AFAIR is a little cumbersome. In the R3 GUI, fonts are 
a resource, similar to colors, certain draw blocks or materials.

So first you have to define the resource if it doesn't already exist, 
and then ask for it by name.

hence my preference to use long names :)

we had one other word to "options" IIRC. I just can't remember it 
now. It was used for top gob (window) parameters ... then we unified 
to options ... what was it?

There is no occurence of the word 'parameter in the r3 source

ah, forget it, it was "flags" ... but that is something different 
...

So - we already started continuation work on Carl's VID? :-)

we are free to make suggestions... but it would be nice with a place 
to store them.

or we could use 

text-list settings [ ... ]
insread of options

Pekr, I'm the last person to make GUi contributions!

settings is even better ...

settings is a better word than options because options is not really 
an option ... since they already occur.  You are setting them.

you have to type more characters (Carl is critical of that)

Luckily there is very little GUI code out there so it's easy to change 
:)

hehe .. .one more character!

yes, Carl is critical about that. I can understand that ... and then 
we have words like 'with, etc. :-)

not a good argument if it leads to confusion

VID was confusing for all newbies .. clarity is essential

exactly ... I think, that what we are aiming at, is natural understanding 
of written GUI code. When reading the code, strange words should 
not disrupt my flow of thoughts ...

I don't like 'facets either ...

What does it mean??

facets are any standard part of the face.

I never liked facets too :-) I remember it being regular english 
word, but I once again don't remember its meaning. So for me it is 
pure only REBOL word :-)

there is a distinction between standard parts, which are inherited 
throughout many faces and private parts for each face instance.

I have no problem with it, perhaps because it's also a Danish word. 
:-)

so call it 'parts instead

I really don't understand the need to invent a new vocabulary

facets is also used in VID. it's an old term.

Yes, I know that ..

And I never liked it then

Graham - then we might replace words like face, feel, engage, etc. 
:-)

Feel and engage are gone in R3. They are replaced by actors.

Yep ... .let's change everything

when I read through the sources (which you can get, properly formatted 
and documented through R3 chat), I can see there probably needs to 
be a better distinction between 'facet and 'faced.

a face is comprised of parts
vs
a face is comprised of facets

that would sound more like you were talking about which GOBs it was 
made from.

a face is an object, and what does an object consist of?

aspects

'facet might be harder to change. I assume Carl chose this name, 
because it's closely related to FACE and we have GET-FACE and GET-FACET 
functions, which I find to be very clear.

and too easier to mix up ?