World: r3wp

as stated you got me to the ~vent group to get me out of your sight 
and avoid the discussion... So predictable.

shadwolf -- this group is for <For discussion of the R3 GUI> (see 
first post).
You are posting about the whole of R3 and its development cycle.
This is not the appropriate group for that.

Please switch to a group that is on topic for that.....Or use one 
of the generic ones, such as ~vent as Anton has suggesfed.

sunanda if you send me read the first meassges here i will send you 
read the first messages i made with the questions i made and the 
repy I got from the intervenant that way the wanabe dictator you 
want to be will see that if actually we seems to be out of topic 
that's related to the way people treat my asks.


Sunanda  If i was speaking ot jesus I wouldn't be trearted that way 
but I would still be out of topic ...

for my actual of topic reply to you will i get banned sunanda ?

Too few people have ever been banned for there to be hard-and-fast 
rules.

Approximatelt.....Combining [off-topic] with [personal abuse] and 
[failure to engage in dialog] would be the main markers for someone 
heading for a ban.

so ban me you will prouve you can't stand a conversation and opose 
true arguments...

And it won't change the actual noone cares about rebol situation 
and less about rebol3 GUI...

rich text is out where can i see it ? 

Why no one comment it ? is it so awfull that noone wants to talk 
about it in fear of having the treatment shadwolf got ?

No one commented on it, because it is _not_ "out" yet.

robert said yesterday "Ok, latest host-kit compiled. Rich-text now 
included."....

I don't know guys you have a boring shadwolf  clamining rich text 
stuff you insult him you say he is nothing but a jerk a troll etc 
but anyway the week later you have it ready (proof that it was a 
point of interrest for you too ) then you don't say to shadwolf hey 
look at this maybe that will get you involved with us ? 


Naaaaaaaaah it's so much more fun to insult me and act like kids 
....

Please keep the ranting out of here, and stick to more approriate 
groups for that.

Regarding the only factual statement in the above: "compiled" != 
"released".

andreas ok so why announcing it's ready if it's not ?

No one announced that it is ready. Robert said it compiled; nothing 
more, nothing less.

why compiling things that don't work ? Ok so i should have understoud 
it more like rich-text widget is done now and it compiles well so 
on next release at that time you will be able to experience it. We 
are impatient to get your comments on this new module.

would have been better said that way indeed ...

You are interpreting far too much into things. No one said that the 
rich-text widget is done. Robert said it compiled (presumably for 
him). That's a progress report, nothing else. The progress, presumable, 
being that the richt-text stuff not only compiled for the original 
author (Cyphre? Henrik?) but for Robert as well.

but you can compile only some code ? or have we changed century and 
now you can compile empty conceptual ideas ?

Once again: you wanted to know wether the rich text stuff is out 
yet. I told you that this is not so. I think that concludes this 
discussion.

Rich text: Carl's tweet on 4-aug-2010 is the published source:

<We are currently converting the richtext dialect to work with the 
new host-kit.> 
http://twitter.com/rebol3/status/20300043616

thank you sunanda ... but then we don't have any idea of the converting 
lenght ... ok so the info are ''at August 14 th  2010, the Rich text 
dialect is adapted to the new project GUI using host kit . And Robert 
could compile it properly"

and i think if i try to discuss the dialect content in the new host 
kit i will be once again of topic ...

off topic ...

Cyphre, you GUI update inside a network looks similar to what I did 
... but which didn't work!  Ok, time for me to try again.

All my GUI updates occurred after network activity completed.

Graham , you have to send small chunks of the data (according to 
Carls notes for the R3 schemes the chunk should be smaller than 32Kb..this 
is true othervise the port connection 'hangs' for me if the chunks 
are bigger ) and do the update during that periods when you need. 
That's all the magic.

My data was a lot smaller than 32k so I think i have some other issue

Just in relation to the binding issues being discussed in core, how 
does R3 gui work ... are named gobs in the global context or private?

they are in a private context

so how does one access them?

this is a problem that needs to be solved. I don't remember the exact 
path inside the GUIE context to the faces.

however the context privacy feature should be kept. it's very useful 
with multiple instances of the same layout.

sure ...

But I was wondering how to access the faces by name

inside the layout, you are fine:

view [f: field button do [set-face f "boo"]]


Outside, you need to go through the GUIE context, but I don't recall 
the path.

I think what would be neat would be a way to access widgets by index 
...

the GUIE context may also change, once the R3 GUI becomes a module.

eg. set the face of the 3rd field ...

we have something like that with the NEXT-FACE? BACK-FACE? FIND-FACE? 
functions.

and to traverse the pane of a face, you traverse the FACES block. 
the setup for the face tree is simpler to navigate than in R2, because 
you are for example not allowed to make that block into a face, I 
believe.

I mean from outside ..

found the path. not in GUIE, but from what's returned from VIEW:

l: view/no-wait [f: field]

l/data/faces/1/faces/1 ; the field, but not with variable name

so there's a context which has to be found

an alternative, probably a more sensible one for large GUIs is to 
reference the faces from within the layout and then using functions 
externally:

boo: func [face] [print get-face face]

view [f: field button submit 'f boo]

with the problem that if your function sets a large number of faces 
...

fortunately we can set a large number of faces at once, if your layout 
is properly arranged.

Bolek, our private world is down, so I have to post here:


1. Some pointers on SPACING, MARGIN and PADDING: I think they should 
be standardized so that SPACING is 2-5 pixels, while PADDING and 
MARGIN remain at zero, so we can special-case them. We should reference 
these values in each style by STANDARD-SPACING, STANDARD-MARGIN and 
STANDARD-PADDING, rather than hardcoded values.


2. The PAD style retains its color on a differently colored PANEL.

2. (which it shouldn't do. it should be transparent.)

http://rebol.hmkdesign.dk/files/r3/gui/232.png

Slightly more meaningful display of form validation.

keep them coming :-)