World: r3wp

ok, cool

Pekr, possibly, but that's out of my league.

There are also some docs and comments in code:)

Is the DRAWING style suppose to be working?

GUI work log update: ON-CONTENT revision done, debugging the changes. 
One of the changes is a removal of the PANEL/FACES block. Reasons:


- data aren't normalized, since the contents of the panel are listed 
both in panel/gob and in panel/faces

- thus, twice as much memory used, and unnecessary maintenance of 
the panel/faces block is necessary

- the not normalized nature was visible anyway, since the order of 
faces was not guaranteed to be the same

- to get the block when needed, it is possible to use a FACES? function 
returning such a block on demand

what about calling it get-faces?

or get-content? That would be a good match for container styles? 
....

I assume FACES? will only be used inside styles, so it should be 
a short name.

faces-of

+1

New 'X-mas' release of R3-GUI is available for download at http://www.rm-asset.com/code/downloads/

top-level changes:

-smarter face update mechanism
-improved dynamic panel content handling
-internal optimizations and more system-friendly redesign
-cleanup of obsolete code parts

some more detailed notes:


- panels can now contain normal, VISIBLE faces, HIDDEN faces (just 
invisible, but taking the same space as the visible faces), IGNORED 
faces (invisible, and not taking any space), FIXED (visible, but 
not resizing with the panel, having a fixed position and size)

- the ON-CONTENT actors for all panels (HGROUP, VGROUP, VPANEL, HPANEL) 
now are as much compatible with series function as practical, taking 
an integer index, high-level function can take a gob or a face to 
specify the position as well

- Data optimization: FACES attribute removed to not need to store 
and maintain the same information twice, risking the conflicts (they 
were already present, order of faces was not identical)


You can also download the latest R3.exe from our site which contains 
LOAD-GUI that directly loads the actual release. This way you are 
always using the latest R3GUI codebase.


We'll be updating the 'old' documentation soon to be up-to-date with 
our current R3GUI version. So interested developers can start using 
it for real or participate on the project.

And, to not forget, thanks to Cyphre's effort, the VGROUP and HGROUP 
styles now properly use the RETURN keywords allowing the *group styles 
to have rows/columns with unequal lengths

Very nice, congrats!

Sounds good

ha! :-)

super many thanks for it .....but demo not working !!!!!

Demo is still based on Carl's old GUI, I believe. only LOAD-GUI has 
changed.

You may want to patch that, too

it could be a good idea to upgrade demo too.

Upgrading would probably mean a rewrite

well some guru could do this job and show us bests practices with 
load-gui !

actually, there is a big bunch of tests in the zipped source code 
that I uploaded a few days ago. those contain some examples for study.

Thanks GUI team!

I don't like how you use function names like faces? to return other 
than boolean values.

names like: back-face?, next-face? should be better:  prev-face, 
next-face

Do you a demo script ?

I mean in R3 gui.

For example I would prefere FACES-OF instead of FACES? as Anton sugested.. 
in the latest sources is used faces? And there is more such a cases 
which I don't like. I really use the names ended with ? only for 
logic.

I agree

I think the idea was to separate functions from actual faces.

the functions map-inner and map-outer are not used anymore?

http://94.145.78.91/files/r3/gui/r3-gui-src.zip

Updated to latest sources and a build is now inside as well.

Ah... map-event is the old map-inner native function

FACES-OF:FACES? preferences - the current count is 3 (developers 
- Cyphre, Ladislav, Henrik) : 3 ( Anton, Pekr, Oldes)

Oldes, I agree about the slight inappropriateness of back-face? next-face? 
having the '?'. However, I also don't like much the same names without 
the '?', as I used such words as variables in some algorithms. I 
tentatively suggest back-face-of next-face-of.

Anton, that might be a good idea.

+1 for FACES-OF

I totally agree with you, Anton. I don't care that the world is longer 
if it improves readability of the code.

+1 for FACES-OF

+1 for FACES-OF

Oldes: there are a number of REBOL functions with a ? that return 
something other than boolean - length? and type? immediately spring 
to mind!

I can see that they would be more meaningful if they were called 
length-of and type-of  though.

They're also exceptions to the general rule, because the word without 
? is used too much as a variable or another function, as Anton says

+1 for FACES-OF

Merry Christmas

Re: "They're also exceptions to the general rule" - the general rule 
*is* to use the question mark for such functions, though. The FACES-OF 
"convention" is not a REBOL convention. In fact, it is more like 
a C convention.

Ladislav: and what about words-of, values-of? Those did not exist 
in R2, but were added to R3. Faces-of fits that naming scheme ....

having consistent naming conventions across the board is imo always 
a tough call. Naturally I can understand, why you have selected short 
"faces", and adding question mark ...

Even in R2 we had maximum-of and minimum-of.

In R3 A110 we have 8 "-of" words and 16 non-logic! "?" words (+4 
"?" console convenience words).