World: r3wp

1) copying it all into a block and append
2) using make face layout inside a layout
3) using a layout with a make face with
??

Hi Rebolinth, there's a compromise between the low-level MAKE FACE 
and the LAYOUT [] approach for single faces called MAKE-FACE. It's 
basically a way to create single faces using the VID style name and 
a spec block for of specifying facets. Of course, MAKE FACE should 
have the lowest overhead, whereas - just as it says - LAYOUT is more 
for describing whole layouts. You may find MAKE-FACE slightly easier 
to create VID-compatble faces without getting into too much detail.

Ah oke thanks for the explanation Christian.. Well Yes im using make 
face far more often in bigger programs/scripts where layout i use 
for the quick build of gui's..

Mmm i have asked this once befor but can someone explain to me when 
to use 'with  ?

When you want to assign facets that you can't assign with the dialect 
or any time you find it easier to assign facets using with than using 
the dialect. ;-)

As ammon said :
	view layout [
		vh1 "The text" 
		vh1 with [text: "The text"]
	]
It's the same.

With is nice i.e. to set the background color of a text style (where 
colors used in the dialect are assigned to font) :

and everything in that block is equivalent to working with an object 
block, so you can put in functions, etc. and all the variables are 
bound to the face

view layout [
	vh1 "Text"  blue
	vh1 "Text" with [color: blue]
]

Also the facet does not need to already exist in the style, it can 
be used to add your own custom ones e.g

 view layout [button "click" with [squid: 3] [alert join "My squid 
 is " face/squid] ]

I'm testing a tab button group with BTN look. What do you think? 
http://www.hmkdesign.dk/tabview.png

the idea is for them to be toggles in a group, where only one of 
them can be selected. then there needs to be an easy method to perform 
some kind of action, such as selecting a mode or changing a layout 
in a pane

http://www.hmkdesign.dk/tabview2.png<-- how they would look selected

view layout [style group-tog tog [print [face/text]] with [related: 
'default] group-tog "Anton" group-tog "Henrik" group-tog "other unpeeled 
vegetables"]

(using the existing TOG style)

anton, that's not the point of it

the point is to have a button group that actually looks like a button 
group

Oh I see.

view layout [style group-tog tog [remove find face/parent-face/pane 
face append face/parent-face/pane face print [face/text]] with

 [related: 'default] across space -5 group-tog "Anton" group-tog "Henrik" 
 group-tog "vegetables"]

not good enough :-)

what's missing ?

well, first of all it's easy to tell that it's just buttons layered 
over eachother

which makes it look crude and simple and unprofessional

I like the BTN style, but it's underused in VID for other applications, 
such as a tab button group

Change the space -5 to -2 and it looks better.

second, I use pane switching a lot and it's a hassle to write your 
own routines for that all the time. it should be much simpler.

Just write a couple of functions, face-to-front and face-to-back 
and you can reuse them many times.

that's not the point either...

The point is that it should be easy for everyone to do this. VID 
does not offer a standardized way to do this and you need to study 
how to switch layouts in panes, etc. It should work out of the box

Yes, that would be nice.

then switching panes wouldn't be any more complex than:

view layout [tab-view 400 with [tabs: ["One" "Two" "Three"] panes: 
[layout1 layout2 layout3]
]
]

or this is quite feasible:  layout [tab-panel "One" "Two" "Three" 
panes [ layout1 layout2 layout3 ] ]

Default size of the tab-panel is calculated as the maximum of the 
three layout pane sizes. The three texts are available in face/texts 
so can be processed by init easily to create the three buttons. PANES 
would be a dialect word that simply sets face/panes, absolving the 
need for WITH in the most often used cases.

Note that rebgui has a tab-panel with a pretty simple spec, eg:
	tab-panel data ["one" layout1 "two" layout2 "three" layout3]

good one

..

Thanks folks!!

someone wante graphing, dunno what group was it posted in - one interesting 
project using AGG and Python - Matplotlib - done using AGG - http://matplotlib.sourceforge.net/screenshots.html

Looks nice, Pekr. Would it advocate REBOL making REBOL versions of 
those examples? The code should be less, of course. Else there wouldn't 
be much point in doing it. Maybe it's possible to make a Python -> 
REBOL converter (cross compiler)? I know zip of Python, so I can't 
say.

I am not sure how universal the library is for graphing ... maybe 
if we want to do graphing, we should look for the best of kind library, 
then to port ... I am not sure if there is any advantage to matplotlib 
- it calls agg library, which we have inside of rebol already, so 
:-)

http://big.faceless.org/products/graph/examples.jsp?initial=browsershare

I see. The examples are in matplotlib syntax. And matplotlib is a 
python 2D plotting library. So, as you say, it's probably better 
to find the best plotting library (or make a new one), than making 
an implementation of matplotlib. It could be the best one around 
though.

I think, we have a problem with the way, AGG is implemented. E.g. 
arguments to LINE are pairs (like 100x100). To be able to make a 
smooth curve using LINE, the arguments have to be decimals. Try the 
following code to see:

img: make image! reduce [370x290 white]
blk: [pen blue line-width 0.7 line]

for t 0.0 2.0 0.01 [s: sine 360 * t append blk as-pair round t * 
185 round 290 - (s * 145 + 145)]
draw img blk
view layout [image img]

Yes, decimal support for pair!  I hope this comes in R3 (or sooner? 
;)

Flash is using twips, which seems to be enough.

And not just Flash - http://www.applecore99.com/api/api012.asp

Twips are screen-independent units to ensure that the proportion 
of screen elements are the same on all display systems. A twip is 
defined as being 1/1440 of an inch.

This seems more complicated than decimal pair to me, because you 
need to recompute from twips to actual pixels, so you need to know 
screen resolution and size.

I think the ephemeral vector! datatype might have been using decimals.