AltME groups: search

Gregg, it isn't DRAW, but do you mean something like:

palms: load-thru/binary http://www.rebol.com/view/palms.jpg

view layout [backdrop black image palms image palms effect [merge 
flip 0x1 gradmul 0x1 128.128.128 black]]
or

view layout [backdrop black image palms image palms effect [flip 
0x1] pad palms/size * 0x-1 - 0x8 box palms/size effect [merge gradmul 
0x1 128.128.128 black]]

I've figured out part of what's going on with the calendar - got 
it down to a single line of draw dialect that's causing Rebol to 
segfault, both on the most recent Windows and Linux versions:


view layout [box 120x70 effect [draw [pen red white polygon 0x0 119x0 
119x69 0x69]]]


Something changed between View versions 1.3.1 and 1.3.2 that's causing 
this...  It was working fine with 1.3.1

The scale on Google Maps looks like most are around 400 feet, but 
there's the river that messes it up, and some locations have a slightly 
different layout...  Unfortunately, that's the best I can do

please note that now when using custom layout, it's not possible 
to have a horizontallly resizable list, because it's hard to determine 
how the elements should be resized without making the layout code 
complex (if no one has any suggestions, that is...)

try pasting the below in

layout [text "Hello world"]
 or 
effect [grid 10x10]
or
effect [gradient 0x1 255.20.20 20.20.255]

view layout [f: field "hello" btn "focus" [system/view/focal-face: 
f system/view/caret: tail f/text show f]]

what does layout/parent do? I can't see anything in the docs about 
it

Henrik, I have confirmed that the graphic for the following section 
is correct...
   view layout [
     list-view with [
       in-cols: [Name Level Score]
       data: [
         ["Joe" 12 5645.6]
         ["James" 6 4472.2]
         ["Jimmy" 11 5631.7]
       ]
       fonts: [
         [style: 'bold]
         [align: 'center]
         [align: 'right]
       ]
     ]
   ]

Do you plan to use the 'words facet to allow a VIDish way to specify 
(i.e) data.
So you can write :

	view layout [list-view data ["one" "two" "three"]]

do/args http://polly.rebol.it/test/test/scratch/simcon.r[
probe event-port
# length? system/ports/wait-list
# same? first system/ports/wait-list system/view/event-port
# get in system/view/event-port 'awake
# probe we: get in system/view 'wake-event
# insert second :we [prin "*"] 
# view layout[area] none
]

view layout [progress 200x50 "hello there" font-color white with 
[data: 0.6 append init [pane/offset: size / 5]]]

view layout [progress 200x50 "hello there" font-color white with 
[data: 0.6 append init [pane/offset: size / 6 pane/effect: [merge 
alphamul 128]]]]

view layout [
	box 400x400 black effect [
		draw [
			fill-pen red    arc 200x200 90x90 0   90 closed
			fill-pen green  arc 200x200 90x90 90  90 closed
			fill-pen blue   arc 200x200 90x90 180 90 closed
			fill-pen yellow arc 200x200 90x90 270 90 closed
		]
	]
]

view layout [
	box 400x400 black effect [
		draw [
			pen white line-width 2
			fill-pen red    arc 204x204 150x150   0  90 closed
			fill-pen green  arc 196x204 150x150  90  30 closed
			fill-pen blue   arc 180x190 150x150 120 150 closed
			fill-pen yellow arc 204x196 150x150 270  90 closed
		]
	]
]

Be aware of linebreaks:

data: [
    18 cyan
    22 blue
    15 green
    20 yellow
    10 purple
    54 magenta
]

sum: 0
foreach [val color] data [sum: sum + val]

plot: copy [
    pen black
]

total: 0 ; we start at 0 degree
foreach [val color] data [
    angle: 360 * val / sum
    repend plot [
    	'fill-pen color
    	'arc 125x125 90x90 total angle 'closed

   'text 'anti-aliased to-string val 125x125 + to-pair reduce [110 * 
   (cosine (total + (angle / 2))) - 5 	110 * (sine (total + (angle / 
   2))) - 5]
    ]
    total: total + angle
]

view layout [
    box snow 250x250 effect reduce ['draw plot]
]

What could cause font script(encoding) change from f.ex. baltics 
to western  when downloading and running scripts on other computer.

In this case I am getting language specific symbols displayed like 
the font encoding scipt is Western while I need Baltics.

At the same time I had no problem, when I called the same layout 
script in office.
Problem appears when I am at home connected to office via VPN.
Rebol view console font encoding script is set to Baltics.

My script looks like this

view layout [
   title "Address"
   across
   name-list: list 300x400 [
      text bold 400 [

         person-info: first sql rejoin [{select * from person where guid like 
         "%} face/user-data {%";} ]

         ;person-info: ["1" "ingo" "hohmann" "static test" "" "" ""]
         vals: get person-disp

         repeat i length? person-info [insert clear vals/:i person-info/:i]
         show w
      ]
   ]
   supply [
      count: count + cnt
      face/color: ivory
      face/text: none
      if even? count [face/color: ivory - 50.50.50]
      if none? v: pick list-data count [exit]
      face/text: reform [pick v 4 "-" pick v 2 pick v 3]
      face/user-data: pick v 1
   ]
   sld: slider 16x400 [
      c: max 0 to-integer (length? list-data) * value
      if c <> cnt [cnt: c show name-list]
   ]
   w: box 400x400 with [pane: layout address/make-person-lay]
]


If I click on a list entry, it's like all other entries are removed 
from the list. Wherever I click I always get the same entry, if I 
move the mouse over the list, all other lines are emptied when the 
mouse moves over them.
Using the static test-data everything warks fine

person-disp is an object, which contains the strings to be displayed 
in my layout.

with doing clear insert  the string keeps bound to the layout

list-data: [
	["" "hello"]
	["" "there"]
	["" "Ingo"]
	["" "Hohmann"]
]
cnt: 0
view layout [
   title "Address"
   across
   name-list: list 300x400 [
      text bold 400 [

         ;person-info: first sql rejoin [{select * from person where guid 
         like "%} face/user-data {%";} ]

         ;person-info: ["1" "ingo" "hohmann" "static test" "" "" ""]
         ;vals: get person-disp

         ;repeat i length? person-info [insert clear vals/:i person-info/:i]
         ;show w
      ]
   ]
   supply [
      count: count + cnt
      face/color: ivory
      face/text: none
      if even? count [face/color: ivory - 50.50.50]
      if none? v: pick list-data count [exit]
      face/text: reform [pick v 4 "-" pick v 2 pick v 3]
      face/user-data: pick v 1
   ]
   sld: slider 16x400 [
      c: max 0 to-integer (length? list-data) * value
      if c <> cnt [cnt: c show name-list]
   ]
   ;w: box 400x400 with [pane: layout address/make-person-lay]
]

a bug? view layout [ch: choice 100 "a" "b" "c"  btn "zmen" [set-face 
ch "c" show ch]]

view layout [text "Test" font-color none]

view layout [box navy at 30x30 text 200x30 effect [merge draw [pen 
0.0.0.255 text "hello there"]]]

is it possible to save a layout as image, e.g. png?

save/png %image.png  to-image layout [button "Hi, Raimund"]

This is probably sooo stupid.. because i work always with a make 
face I now need to add a simple face to a layout.. ;-) But i simply 
dont get it running... ie.

main: layout [] 
append main/pane [ something ]
view main

does not work..hehe ;-) any hints? its sooo simple probably..

append main/pane make face layout [button "OK" [print "ok"]]

aaa wait... its the 'make face that needs to go inside a layout ofcourse...

view layout [button  area  face with [init: [] size: 100x100 color: 
navy]]

But i actualy like the felixibilty of 'layout function there are 
more ways to combine layout and make face ...intresting if your not 
like to reinvent /vid again ...

But actualy I wonder what the best way is to merge the use of Layout 
together ith 'make face.. Which is eating less overhead?

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..

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

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] ]

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

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

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"]

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.

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]

scale: 10
img: make image! reduce [370x290 white]

blk: compose [scale (1 / scale) (1 / scale) pen blue line-width 7 
line ]
for t 0.0 2.0 0.01 [
	s: sine 360 * t

 append blk as-pair round t * 185 * scale round 290 - (s * 145 + 145) 
 * scale
]
draw img blk
view layout [image img]

The EFFECT block is like a graphical pipeline. You can have a serie 
of effects and DRAW blocks after each other. Like:

img: to-image layout [box red "Red" box green "Green" box blue "Blue"]

view layout [box 200x400 white effect [draw [image img] tint 40 draw 
[translate 100x100 image img]]]

now I've run into the problem with VID elements sharing the same 
font object, which means that if I create three tab views, and change 
the font in the first one, the other two incorrectly also change. 
where exactly is this fixed? I've tried putting the font object inside 
the init code for the element, but this makes it impossible to change 
the font settings from within the layout.

If it's the LAYOUT user who want's different fonts, let him specify 
them.

If it''s you wanting to to have e.g. a second bold font just for 
the pressed tab in one tab-view, I think you may for example allocate 
two font objects and dynamically swap them in the FEEL/REDRAW.
Code fragment:


 redraw: func [face action offset] [... face/font: pick face/fonts 
 face/state ...]

You may even get along with changing a single font object:


 redraw: func [face action offset] [... face/font/style: if face/state 
 ['bold] ...]

now it's a chicken and egg thing. If I clone the object inside INIT, 
the font settings inside the layout is ignored, apparently because 
they are parsed before INIT is run.

Henrik, can I see an example of what you mean by "font settings inside 
the layout" ? because I am not sure it's true, given:

view layout [style bx box "box" navy with [append init [font: make 
font []]] bx bx bx font-size 40 bx]

On Gabriele's note, use FLAG-FACE? to check for flags:

	>> layout [b: box]
	>> flag-face? b font
	== none
	>> layout [b: box font-size 30]
	>> flag-face? b font
	== [font]

and FLAG-FACE when you want to set a flag yourself.

I've tried following to get 'b local in panel but 'b is still global

>>layout [panel with [b: none][b: button]]

Is there some other way?

layout [panel with [b: none][face/b: button]]

It looks OK, but actually, it's not working.
>> layout [panel with [b: none][face/b: button]]
Misplaced item: face/b:

>> layout [p: panel with [ctx: none insert init [ctx: context [b: 
none] bind second :action ctx]][b: button]]
>> ctx
** Script Error: ctx has no value
** Near: ctx
>> b
** Script Error: b has no value
** Near: b
>> p/ctx/b/style
== button

I tried to create with the following code a circle with a transparent 
background and save it. I tried some different versions, but currently 
I have no glue how to achieve this. The point is I need a file with 
a circle and a transparent background :-) and I thought I quickly 
do this with Rebol instead of using a paintprogram. So am I doing 
something wrong ? It's saving the background from the window and 
if that is set to 'none then it's black ?

view layout [
    b: box 22x22 effect [
        draw [pen red line-width 2 circle 11x11 10]
    ]
    across 
    f: field 200 button "Save" [
        file-name: to-file f/text

        unless find/last file-name ".png" [append file-name ".png"]
        save/png file-name to-image b
    ]
]

Im using Layout where im appending panes into layouts.. But i dont 
think thats the problem... The problem is resizing an 'effect to 
negative numbers... like a box from 0x0 500x500 to ->  -50x0 -100x100 
...and only using it in the Engage event... Odd?? anyone an explanation 
perhaps ? This is Linux /rebview from SDk262

view/new window: layout [area]
window/feel: make window/feel [

 detect: func [face event][if find [active inactive] event/type [probe 
 event/type] event]
]
do-events

Q: invalid args: []

Hi, I have a layout, and I always get the above mentioned error ... 
does anyone know a some hints to find the culprit? I haven't succeeded 
so far.

view center-face layout [
	box: box navy 300x300 with [
		pane: make-face/spec 'box [
			size: 80x80 
			offset: 40x40 
			color: red 
			text: "drag me"
			feel: make feel [
				engage: func [face action event][
					print remold [action event/offset]
					if find [over away] action [
						if drag-off [
							; we are dragging
							face/offset: face/offset + event/offset - drag-off
							; now constrain the face within its parent box
							;face/offset: confine face/offset face/size 0x0 box/size
							show face
						]
					]
					if action = 'down [drag-off: event/offset] ; begin drag
					if action = 'up [drag-off: none] ; end drag
				]
				drag-off: none
			]
		]
	]
]

Maybe something like this:

view layout [box 400x400 effect [draw [image logo.gif 20x20 380x50 
300x380 40x100]]]

view layout compose [face "hello" (svv/vid-styles/button/facets) 
(svv/vid-styles/h1/facets)]

I just tried out the source code version .. if I type into the bottom 
one, nothing appears there until a click, but it appears immediately 
in the top layout.

ie. instead of using LAYOUT which makes a face with a box in it, 
just make the box.

Rebolek - use label instead? uh, hard to change when layout is out 
already .... I have disable/enable functions, but it works only for 
mouse sadly, you can still tab to the field ...

view layout [f: field tog "enabled" "disabled" [either value [feel: 
f/feel f/feel: none][f/feel: feel]]]

Better...

view layout [f: field feel [] tog "enabled" "disabled" [f/feel/detect: 
all [value func [face event][none]]]]

this doesn't look at all like it should

translate-draw: func [
	height [integer!]
	blk [block!]
	/local dr p
][

 parse blk [some ['draw set dr block! (parse dr [some [p: pair! (p/1: 
 as-pair p/1/x height - p/1/y) | skip]]) | skip]]
	blk
]

view layout [
	origin 0
	bx: box 400x400 black effect translate-draw 400 [
		draw [
			pen red
			line 50x50 350x50
			pen blue
			line 50x50 50x350
			pen yellow
			line 50x50 100x200 200x150 300x250 350x225
			pen white
			text aliased 10x350 "Y axis"
			text aliased 320x40 "X axis"
		]
	]
]

view layout [box red key 'f5 [print "how do I capture F-keys?"]]

view layout [button "F5 Button" keycode 'f5 [print "got F5"]]

probe first system/view 
probe get in system/view/event-port 'awake 
make system/view [source wake-event] 
system/view/wake-event: func [port /local event no-btn] bind [
    event: pick port 1 
print remold [event/type event/offset event/key] 
    if none? event [

        if debug [print "Event port awoke, but no event was present."] 
        return false
    ] 
    either pop-face [

        if in pop-face/feel 'pop-detect [event: pop-face/feel/pop-detect 
        pop 
            -face event
        ] 
        do event 
        found? all [
            pop-face <> pick pop-list length? pop-list 
            (pop-face: pick pop-list length? pop-list true)
        ]
    ] [
        do event 
        empty? screen-face/pane
    ]
] system/view 
echo on 
print "con" 
view layout [button "test" [probe "test"]]

system/view/wake-event: func [port /local event no-btn] bind [
    event: pick port 1
print[type? event]
if event! = type? event[ 
print remold [event/type event/offset event/key] 
]
    if none? event [

        if debug [print "Event port awoke, but no event was present."] 
        return false
    ] 
    either pop-face [

        if in pop-face/feel 'pop-detect [event: pop-face/feel/pop-detect 
        pop 
            -face event
        ] 
        do event 
        found? all [
            pop-face <> pick pop-list length? pop-list 
            (pop-face: pick pop-list length? pop-list true)
        ]
    ] [
        do event 
        empty? screen-face/pane
    ]
] system/view 
echo on 
print "con" 
view/new layout [button "test" [probe "test"]]

if you  added data and it works, sounds like something memory-related. 
changed memory-layout, other part is hit.

l: layout [ box with [source 'function!]]

l: layout [field text "toto" text-list  box with [source function!]]]
; works too

These are all ways of specifying the same thing:
view layout [area wrap]
view layout [area para [wrap?: yes]]
view layout [area with [para: make para [wrap?: yes]]]

view layout [area with [append init [para: make para [wrap?: yes]]]]

and you can test a little bit faster by making the area nice and 
thin:
view layout [area 40 wrap]

view layout [i: icon "Hello!"]


demonstrates this: Click and hold on the text and drag towards the 
icon. Or do the same from the icon towards the text. The click is 
lost.

Not sure what you mean, either:

  view lay: layout [btn "Resize" [lay/size: 400x400 show lay]]

or

  my-evt: make event! [type: 'resize]
  system/view/wake-event my-evt  ;-- doesn't work, another way?

or


  do-on-resize: func [f e][if e/type = 'resize [alert "Resize!!!"] 
  e]
  insert-event-func :do-on-resize
  view lay: layout [btn "Resize" [lay/size: 400x400 show lay]]

how do you bind layout words to an object easily? I want to set faces 
to variables which are supposed to be local to the context of my 
Tester program. I realize this is really the old "dynamic variable 
list in an object problem" all over again (I run into this very often 
it seems), but was wondering if LAYOUT specifically allowed some 
tricks...

well the thing is how variables are initialized when doing an object. 
I've discussed this before, but it would be nice to keep the list 
shown at the top of that example in the docs as a dynamic list. this 
prevents me from having to maintain that list and the layout words 
when doing changes. I guess I need to approach how to make the object 
block differently.

the way I see it, I need to create the object block with layout blocks 
first. then analyze those layout blocks for set words and finally 
create a new block with the set words set to none and append the 
object block afterwards

>> view layout [base-text "hello" with [focus self]]
** Script Error: Invalid graphics face object
** Where: focus
** Near: show face

view layout [field field "hello" with [focus self]]   ; OK

; Redraw action SHOW occurs first, then DRAW.

view center-face layout [
	f: field feel [
		crt: none 
		append body: second :redraw bind [

   either act = 'show [crt: system/view/caret system/view/caret: none][system/view/caret: 
   crt]
		] body/3/2
	]
	field 
	do [focus f]
]

Actually, the opposite can be a problem - expecting parent-face to 
be set before the face has been SHOWed. eg. you have LAYOUT a window, 
but not VIEWed it yet.

uhmm... not sure about weirdest :-) but I build the toolbar layout 
from a block that is parsed, appending faces and their attributes 
as it gets parsed. when that's done, I show it..

REBOL []

stylize/master [
  f: FACE WITH [
    do-this: does [
      insert tail pane: [] make face [
        feel: make feel [
          detect: func [face evt] [
            if evt/type = 'up [
              repeat i 5000 [
                do-this
              ]
            ]
            evt
          ]
        ]
        pane: make face []
      ]
    ]
    init: [do-this]
  ]
]
view layout [
  f 100x100
]

Ok, this still shows the bug:
- removed stylize
- removed layout and view
- set object facets to none

view layout [scroller with [ratio: 0.9 step: 1 / 10]]

but its different... all it would need is a layout dialect (using 
GLayout resizing)

I also remember some aspect (worries) of Chris, who requested layout 
being more like in css world. Dunno what exactly was the request, 
but something like - once you do layout, VID dialect is not live 
anymore (live=tight to changes you make later?) Not sure what was 
his intention here ...

I would like to be part of the team.  Just like Anton, I've been 
fighting my way inside of VID for years.


I'll be blunt The only thing I'd keep is the dialect concept while 
add glayout ish row/column layout which even Carl admitted is much 
easier to handle and "see".

Should VID has this, or that, etc., how to aproach layout, on-something 
handlers in upper level? etc.

its a prototype so yess the *code* has some ugly bits... but the 
layout concept is very agile, and makes tidy guis with little effort 
and understanding needed... its acutally much simpler than current 
vVID.

remember there is also a difference between skinning and actual GUI 
design, e.g. the layout of elements on screen. One can have a beautiful 
skin on an annoying interface. The same goes the other way around.

Henrik, that's one of the reason i'd want to have automatic layout 
- most programmers are so bad at layout that even a program can do 
better if it follows good rules.

We should get someone to formulate some formal design rules into 
the engine of a layout dialect.

Gabriele, how high level would you carry auto-layout? I have myself 
thought about creating standard layouts, certain combinations of 
faces that are common, not just for yes/no dialogs, but, say, a two-pane 
or three-pane layout. Something that strongly encourages you to put 
a menu at the top, generic content in the middle and buttons at the 
bottom, where for example OK/Cancel/Retry buttons also are laid out 
in a specific sequence. Never got around to it though.

Silly example:

view layout [
  three-panel [
    menu [File Project Edit Show History]
  ] [
    ordinary VID code here
  ] [
    buttons [OK Cancel]
  ]
]

Hmm.. however, how is that different from:
view layout [
	vertical-panel [
		menu [File Project ...]
	][
		ordinary VID code ...
	][
		buttons [OK Cancel]
	]
]