World: r3wp

I would at least expect chained gob structure, so that one can traverse 
it via gob/pane, gob/parent .... it escapes my mind, why window/pane 
does not contain its subelements, but maybe the meaing is here quite 
different ...

I'm actually not seeing anything in the new GUI that allows you to 
find a given face's parent.  It's really very frustrating me...

Well...  WTF do you know?  

window: view/no-wait [t: text "this is a test"] 
set-face window/data/faces/1/names/t "Mwahahahah"
show window
do-events

I posted my reaction to rebdev chat too. I am missing some aproach 
to easily traverse gui:


- there is bog/pane, but not face/pane. There is face/faces e.g. 
for panel style. If it is the same concept, why name it differently?
- there is no face/parent-face to traverse backwards

- face/gob contains just one gob. It also seems to me, that it is 
not even a pointer to the gob, but not sure. Not sure if it would 
be usefull, but currently face can't be built from multiple unrelated 
gobs. You have to have one gob, and other ones in gob/pane

Hmm, but as you show, there is some way. But it is strange. Docs 
say, that gob/data point to face. So what is "face" actually here? 
Some special Window face? Ah, I might understand and I pointed out 
already the discrepancy. While for gobs, we use /pane, as we all 
know it from VID2, but the same concept for faces is /faces .... 
While the name is clear, I vote to rename it to /pane, to make it 
apparent it is the same thing ...

Yup. I read it.  You did a very good job of describing what's been 
annoying the hell out of me for the past 4 hours.  Hopefully we'll 
get some straight answrs to all of that.

I completely agree with you on the /faces vs. /pane issue!

Eh...  I got distracted and quit playing with the RebDev client but 
I've been making good progress on the text editor I'm writing. =D

I post here what I posted elsewhere. I refuse to use RebDev - another 
non-web UI for "supporting development".  With nice features, no 
serious back end (imagine real user amounts like, a few thousands 
using this...) and no UI. And to have to move yet AGAIN....

Maarten, a few thousand? Not likely to happen right now and as Carl 
said, he would add features as needed, and there's no need to support 
a few thousand users right now. Right now the next step is a proper 
GUI.

Ammon, it sounds simply to me that some features for setting window 
titles, etc. are either missing or undocumented. I'm pretty sure 
you're not meant to use obscure paths to access features, but to 
use SET-FACE, GET-FACE, SET-FACET and GET-FACET. These features are 
much more powerful in the R3 GUI than the ones in VID.

And if they're missing, it doesn't take long to add them, so instead 
of "getting annoyed as hell", ask nicely on rebdev and Carl will 
probably find some time to add them. :-)

Henrik, my point is that you never get to a few thousand this way, 
let alone serious world domination. I'll probably check on R3 when 
it  "surfaces".

Maarten - I did agree with your POV and told Carl, that RebDev kills 
Altme. But - his reply made sense to me. We should not see it as 
a threat to Altme/web (yet), so let's suppose current RebDev is nothing 
more than CVS with ability to chat to whatever topic or file ...

... and - it was declared from the very beginning, that GUI is much 
needed here, and it will be surely done ...

I have to agree with Maarten

we should have gone for the BBS option that everyone but Carl agreed 
with.

It's nice that people completely forget the backend, the reason Carl 
built Devbase in the first place, and why he wouldn't look at other 
options. :-)

LOL. See, now Devbase is  giving me amnesia as well! Let's just say 
it's not my "thing".

We can go for any BBS anytime, it just officially will not be guaranteed 
by RT.

I was against new system, but I am satisfied with Carl's explanation 
of his POV. He needed streamlined channels for chat, bugs, CVS, filesharing. 
New system, in comparison to AltME, gives us:

- threaded discussions
- ranking
- tagging
- threaded discussions
- message/topic moving
- versioning system
- document management. Docs posted anywhere to any message.
- console version


So far, the big minus is - no GUI client. But - that might be over 
in few months ... So - if we think of RebDev as nothing more than 
RT's supporting infrastructure, I am OK with it. It is just that 
for fast dev related chat, e.g. nowadays GUI related, it can't reach 
Altme comfort and speed in not more than 20%. Threading is very confusing 
now ...

According to Carl there's no correct way to do what I'm trying to 
do yet.  That just might explain why it was so difficult to find 
the correct way to do it...

to bad liquid crashes R3.

are any of you having troubles with dynamically creating code and 
binding it as objects and stuff like that?  (In R3)

specific examples?

I'm updating DocBase GUI docs.


1. Changing the links at the bottom of each of the pages to point 
to a single template so that they are automically updated across 
all pages by changing one document.
2. Adding [[Category:GUI]] to each of them.

3. If I have time I'll start working on a VID2 to 3 document that 
describes what changed.  Things like face/parent-face is now parent-face? 
face.

I just wanted to mention that when I run the gui demo and click the 
"text view" test it causes an error on my vista machine.

Yup, Paul, that's a known bug.

Someone, BrianH I think, posted a link to this group (I think) to 
a document on DocBase that talks about the performance differences 
with some of the loop functions in R3.  I can't seem to find it though. 
 This is why MediaWiki bothers me.  It search sucks.

I would like to see such a document as well. I know that the loop 
functions in R3 are faster since they are all native, but I don't 
know how much faster. Clearly if I was the one who posted it I forgot 
where it was too :(

Paul, yes, this is due to one text area trying to load the source 
code for the original version of the demo, which doesn't exist anymore. 
However it throws a different bug than it should, so it's lucky that 
it came up.

Ammon, BrianH, it's search sucks: Which is why such a document should 
be a cookbook recipe. Easier to find.

anyone has tested size-text on a gob ?

is there a problem?

i get  a wrong size/x

example?

wait a minute...

I've not noticed anything yet, but there could be problems with certain 
fonts, multiple lines or shadows.

in fact there is a rich text bug that causes a size to be calculated 
incorrectly by a couple of pixels in a very specific condition.

i get the bug with the standard font too.

try this:
gob: make gob! [offset: 50x50 text: ["test"]]
gob/size: size-text gob
view gob

here "test" is truncated

y is incorrect too, missing some pixels (tested with text: ["gggjj"]

yes, I think that's a bug.

another one bug, if the size of the gob is previously set to 0x0, 
size-text is entering in an eternal loop.
gob: make gob! [size: 0x0 text: ["test"]]
size-text gob

i wonder how th

i wonder how the VID can work currently

size-text is used by some styles

Actually, not.

In VID, Size-text is only used to change the y coordinate of a gob, 
which means the bug has never been traced.

yes, I've not noticed the problem before. Now that I look at it, 
it seems to be constantly about 2 chars too narrow and a tad too 
short in height.

actually less than 2 chars.