r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[!REBOL3 GUI]

BrianH
3-Feb-2010
[255]
It's possible that the compressed mezzanine data cooincidentally 
included a sequence of bytes that matched some signiature of someone 
else's code, which wouldn't matter to us since that code is decompressed, 
not executed.
Rebolek
3-Feb-2010
[256]
I may try to ask a friend who works at AVG, but I cannot promise 
anything.
Graham
4-Feb-2010
[257]
no-edit: [
        #"^H" left
        #"^X" #"^C"
        #"^V" ignore
        #"^M" ignore
        delete deslect
        delete-end deselect
    ]

filed as ticket 1455 ...
Graham
5-Feb-2010
[258x3]
It looks I can use a monospaced font in a text list by changing the 
text-list-box face/text-style to 'code instead of 'list-item ... 
but quite unclear to me how one does this easily
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
Henrik
5-Feb-2010
[261]
parameters
 instead?
Graham
5-Feb-2010
[262]
sure
Pekr
5-Feb-2010
[263]
pars or params, to make it shorter to write :-)
Graham
5-Feb-2010
[264x2]
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!]
]
Pekr
5-Feb-2010
[266x2]
vocabulary shows that param, parm, is a regular english word ....
but other than that, anything is ok with me :-)
Graham
5-Feb-2010
[268]
so that you know that text-list takes a block
Henrik
5-Feb-2010
[269x2]
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.
Graham
5-Feb-2010
[271]
hence my preference to use long names :)
Pekr
5-Feb-2010
[272]
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?
Graham
5-Feb-2010
[273]
There is no occurence of the word 'parameter in the r3 source
Pekr
5-Feb-2010
[274x2]
ah, forget it, it was "flags" ... but that is something different 
...
So - we already started continuation work on Carl's VID? :-)
Henrik
5-Feb-2010
[276]
we are free to make suggestions... but it would be nice with a place 
to store them.
Graham
5-Feb-2010
[277x2]
or we could use 

text-list settings [ ... ]
insread of options
Pekr, I'm the last person to make GUi contributions!
Pekr
5-Feb-2010
[279]
settings is even better ...
Graham
5-Feb-2010
[280]
settings is a better word than options because options is not really 
an option ... since they already occur.  You are setting them.
Henrik
5-Feb-2010
[281]
you have to type more characters (Carl is critical of that)
Graham
5-Feb-2010
[282x2]
Luckily there is very little GUI code out there so it's easy to change 
:)
hehe .. .one more character!
Pekr
5-Feb-2010
[284]
yes, Carl is critical about that. I can understand that ... and then 
we have words like 'with, etc. :-)
Graham
5-Feb-2010
[285x2]
not a good argument if it leads to confusion
VID was confusing for all newbies .. clarity is essential
Pekr
5-Feb-2010
[287]
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 ...
Graham
5-Feb-2010
[288x2]
I don't like 'facets either ...
What does it mean??
Henrik
5-Feb-2010
[290]
facets are any standard part of the face.
Pekr
5-Feb-2010
[291]
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 :-)
Henrik
5-Feb-2010
[292x2]
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. 
:-)
Graham
5-Feb-2010
[294x2]
so call it 'parts instead
I really don't understand the need to invent a new vocabulary
Henrik
5-Feb-2010
[296]
facets is also used in VID. it's an old term.
Graham
5-Feb-2010
[297x2]
Yes, I know that ..
And I never liked it then
Pekr
5-Feb-2010
[299]
Graham - then we might replace words like face, feel, engage, etc. 
:-)
Henrik
5-Feb-2010
[300]
Feel and engage are gone in R3. They are replaced by actors.
Graham
5-Feb-2010
[301]
Yep ... .let's change everything
Henrik
5-Feb-2010
[302]
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.
Graham
5-Feb-2010
[303]
a face is comprised of parts
vs
a face is comprised of facets
Henrik
5-Feb-2010
[304]
that would sound more like you were talking about which GOBs it was 
made from.