AltME groups: search

could it be a buffer overflow related to an older View bug? I've 
seen older View versions crash sometimes if a layout gets too big

There shouldn't be magical numbers, if you run with different data, 
and have c-level memory-bugs. Because then the memory-layout differs, 
and then the same bug hits different data. i had those bugs, perfectly 
repeatable. Disappeared when i changed the filename a bit. I guess 
different length -> slightly different memory layout. Hmm, slightly, 
sounds like an of by one in that case, or alignment?

view/options center-face layout [area] 'resize

james: "When I exit the program...the app's window closes but the 
app stays around as a task"

hmm..does this your encapped program only when running from altme 
or als when you run it 'normally'?

If the second is true maybe you are using in your program something 
like:
view/new layout [...some layout here...]
forever [
	do [...some loop code...]
	wait <some time> 
]


If so the you need to properly handle the event when you closing 
the View window because othervise the window is only closed but the 
FOREVER (or any other) loop is still running. The solution is for 
example put before the "view/new" line:


insert-event-func func [face event][if event/type = 'close [quit] 
return event]


(ofcourse if your app is using multiple windows you need to add some 
more logic to decide which window should QUIT the app and which not 
when using the 'X' close button)

>> view layout [t: area]
(escape)
>> t/text
== "this is^Ma^Mtest"

Pasted from TextEdit

http://www.rebol.net/cgi-bin/rambo.r?id=3314&


Memory usage climbs, but there is no longer any crash on View 1.3.1

i: 0 until [
	attempt [
		view layout [
		button feel [
		redraw: func [face action pos][
		;if action = 'draw [show face] ; memory use climbs very high
		if action = 'show [show face]  ; memory use looks quite stable
		]
		]
		]
	]
	1000 <= i: i + 1
]
unview

view/new win: layout [] win/changes: reduce [:+] show win  ; crash

Try this:

view/new layout [button 233x233]

load read-net http://www.userfriendly.org/cartoons/archives/97nov/uf13b471.gif

Now try this...:

view/new layout [button 233x232]

load read-net http://www.userfriendly.org/cartoons/archives/97nov/uf13b471.gif

view layout [b: box feel [engage: func [face action event][if action 
= 'key [print event/key]]] do [focus b]]

view layout [
	fld: field "hello" [?? value]
	btn "change" [set-face fld "changed"]
]

view layout [
	face with [ 
		init: [
			size: 600x400

			pane: layout [
				my-list: list 600x400 [
					my-text: text 600 feel [
						detect: func [face event][
							print ["inner -" mold type? event]
							event
						]
					]
				] data [["hello"]["there"]]
			] 

		] 

		feel: make face/feel [
			detect: func [face event][
				print ["outer -" mold type? event]
				event
			]
		]
	]
]

The code is bigger, but I've removed both instances of layout, and 
still showing the bug:

view layout [box 100x100 effect [draw [fill-pen LINEAR 0x0 0 99 90 
1 1 white gold red box 0x0 99x99]]]

view layout [box 100x100 effect [draw [fill-pen linear 0x0 0 99 90 
1 1 white gold red box 0x0 99x99]]]

img: copy help.gif
equal? img help.gif
view layout [image img effect [key 128]]
equal? img help.gif

view layout [box 10x50 effect [draw [pen black white line-width 1 
line 1x1 1x50 line-pattern 5 5]]]

This line crashes Rebol/View 1.3.2 reliably under WinXP

glayout, being a nested VID engine, will effectively call layout 
many times each one might have its own style word calls.

I accidentally put a string in the font size, like this:

view layout [area font [size: "m"]]


Windows gives me a small font, which seems right. On OSX I either 
get screen trashing inside the text area, hanging or a segmentation 
fault.

can anyone make the layout code I wrote above crash in Linux? I don't 
have Linux handy...

Actually, I see quite the opposite. Using following code:

view layout [text "MIQXA" text "MIQXA"  font [size: "m"]]


the second line is bigger .I'm trying this on xubuntu 6.06 (using 
area has same results, but area is much bigger than text so it's 
harder to notice).
I'm rebooting to Win to see the difference.

view layout/offset [h1 "query:"] 770x50
view layout/offset [h1 "query:"] 760x50

view layout [h1 "Hello!"]
view layout/offset [h1 "Hello!"] 770x50
view layout/offset [h1 "Hello!"] 760x50
view layout/offset [h1 "Hello!"] 1076x50

yep, using the layout offset is screwy !

Looking in LAYOUT we see this piece of code:
    new-face/size: pane-size: any [
        all [size pane-size] 
        new-face/size 
        system/view/screen-face/size - (2 * new-face/offset)
    ]

Oh, you're right.
Graham, just do this in your programs:

	view/new window: layout [...]
	if error? set/any 'reserr try [ do-events ][
		print mold disarm reserr
	]

O'k. My mistake are offen do not tell what is my target. So it is 
to get working status bar in a layout. As I understood it is possible 
by read-thru.

Janek. request-download has the example callback you need. View its 
source. here is a snippet. Where prog is the progressbar and stat 
is a label in your layout and stop is a value that controls that 
should be be set false outside of this func to start with, and can 
set to true via a cancel button to force a download to stop before 
completion. 
func [total bytes] [
        prog/data: bytes / (max 1 total) 
        stat/text: reform [bytes "bytes"] 
        show [prog stat] 
        not stop
    ]

rebol [ title: "SOCKS SERWER" ]

conn: make port! tcp://:800

proxy: make object! [ host: 208.59.117.69
                      port: 2988  ]



black-lista: [ 69.64.51.223 194.69.207.145 80.252.0.145 194.69.207.165 
217.73.17.115]




adns: open/no-wait make port! dns:///async

adns/awake: func [port /local data][                
		
		data: copy port

                print data
		
		false 
	]				

insert tail system/ports/wait-list adns





heandler: func [ port /local data dns  serwer client]

               [ serwer: first port

                          
 wait serwer
             
data: copy serwer
;data: make string! 10000
;read-io serwer data 10000
print ["data1" to-binary data]

dns: to-tuple copy/part skip to-binary  data 4 4  

insert adns dns ;print dns name



either find black-lista dns [ close serwer  print "firtled" print 
read join dns:// dns ]
                           
                            [ print "new connetion"

insert serwer  join #{005A} [debase/base  skip to-hex serwer/port-id 
4 16 to-binary dns ] 


client: make port! [ scheme: 'tcp 
                     host: system/words/proxy/host
                     port-id: system/words/proxy/port
]



;insert tail system/ports/timeout-list client

      open/no-wait/binary/async/direct client :response


client/sub-port: serwer





insert tail system/ports/wait-list  client

client/date: data

serwer/sub-port: client

serwer/awake: :request









] 



       false         
]




request: func [ port /local data  f ] 

              [ data: make string! 10000
               read-io port data 10000


if f: find data "GET /favicon.ico" [ insert port "HTTP/1.1 404 Not 
Found" 
                                      print "favicon.ico"]
 


                either (data <> {}) and not f [     print [ "data3" data  ]
                              

                                if error? try [    write-io port/sub-port data length? data ][ print 
                                "error: close serwer"]
                                   ; insert port/sub-port data 
]

                            [  close port 

                              remove find system/ports/wait-list port port
                               close port/sub-port

                              remove find system/ports/wait-list port/sub-port port/sub-port
                              print "close connetion client"

                               print length? system/ports/wait-list
                               ]

               false]




       
   


  
response: func [ port e a /local data  f  ] 

               [  switch e [ open [ insert port port/date ]
                                    
                             read [ data: copy/part port a

                                   either ( a <> 8 ) [write-io port/sub-port data length? data] 

                                                     [  insert tail system/ports/wait-list  port/sub-port ]
                                    ]
                                     
                             close [ close port 

                                     remove find system/ports/wait-list port port
                                     close port/sub-port

                                     remove find system/ports/wait-list port/sub-port port/sub-port

                                       print "close connetion serwer"

                                      print length? system/ports/wait-list]
 

                          ]   ]


start: func [] [

conn: make port! tcp://:800

conn/awake: :heandler

set-modes conn [no-wait: false]

insert tail system/ports/wait-list  conn

open/no-wait/direct/binary conn ]


stop: func [][ close conn
               remove find system/ports/wait-list conn]

set-proxy: func [ h p ] [ proxy/host: h
                          proxy/port: p ]
                          


print "proxy"

lay:  layout [ backdrop blue
              across  h3  red "PROXY" f: field 145 
              return
              button green "start" [ p: parse f/text  ":"
                                     remove find p "" 

                                     set-proxy  to-tuple p/1  to-integer p/2
                                     source p
                                    
                                     start]
              button  green "stop" [f/text: "" stop ] ]

view/offset lay 4x29 
halt

I tend to dio something like:
 x: copy []
append x 'btn append x "quit"
Compose is useful here too for more complex layout building.

That still doesnt get my bit of view code into the layout.

unless you're building the layout.. but I'm looking to add a word 
that represents some bit of view code.

It's trickier if you've already usd layout to convert the dialect 
to VID objects -- then you need to read up on make-face and similar 
functions.
Pre build, just do things like:
x: [button "hi" [print "hello"]]
y: [button "bye" [print "goodbye"]]
z: []
append z y
append z x
view layout z
>>

>> x: [ btn "quit" [] ]
== [btn "quit" []]
>> view layout do [ x ]

this works

>> x: [quit]
== [quit]
>> view layout [btn x]

Yes -- but you need to append, compose or mold it to make it the 
right series of characters for Layout to understand.

depends on what you are doing you can use panel:
 view layout[ panel x panel y .. ]

just view layout compose [(x) (y) (z)]

; You could set up a function or two to simplify this code:
my-styles: []
append my-styles stylize [x: btn "Quit" [quit]]
append my-styles stylize [y: btn "Print" [print 'foo]]
view layout [styles my-styles x y]

perhaps i do not understand what you want to do, but if the goal 
is building a growing set of styles, i think that this is the standard 
way:
x: stylize/styles [a: field] []
x: stylize/styles [b: field] x
view layout [styles x a "style a" b "style b"]

:-) There's the idea for what keys to put on the left side of the 
keyboard to make it more balanced. Well, maybe it will become too 
big!? And then use Dvorak layout (http://www.mwbrooks.com/dvorak/) 
to speed up typing.

serriously the rendering is slow beacause it's a hudge cheat ( Ahley 
compone on fly a multi composed widget layout) make a change and 
click ave to see how long it take to be refreshed...

maybe I'm over estimating the capabilities of AGG on it's actual 
form too... because it's still depending on View layout rendering 
engine

But Henrick wants it in any order, like LAYOUT code. (Thus, it's 
worth to look how LAYOUT works. :)

About Layout : parse handles only the layout words (origin, space, 
at...), see source layout.

The face description is handled by a loop, not by parse. See system/view/vid/grow-facets

For other applications, I use different dialects, like eText for 
simple text -> HTML layout.

Check out the source of the R2's layout function.
?? layout

VID:   How I can change button color? I tried:
view layout [ a: button red [  a/color: 0.0.0
        show a]
    ]

but nothing happens....

>> view layout [b: button "OK" red [probe b/effect]]
[gradient 0x-1 255.32.32 223.0.0]


I think that you might be able to change those tuple values, but 
will it work with gradient easily? :-)

>> view layout [b: btn "OK" red [probe b/effect]]
[colorize 255.0.0 128 extend 14]

>> view layout [b: button "OK" red [probe reduce [b/color b/font/colors 
b/effect]]]

[255.0.0 [255.255.255 255.180.75] [gradient 0x-1 255.32.32 223.0.0]]

>> view layout [b: button "OK" [probe reduce [b/color b/font/colors 
b/effect b/effects]]]
[44.80.132 [255.255.255 255.180.75]
    [gradient 0x-1 66.120.192 44.80.132] [
        [gradient 0x1 66.120.192 44.80.132]
        [gradient 0x-1 66.120.192 44.80.132]
    ]
]

view layout [b: button "OK" red [b/effects/1: [gradient 0x1 100.100.100 
120.120.120]]]

FillType: make object! [
	grad-mode: 'linear
	startpos: 20x20
]

img: make image! 100x100
draw img	[pen none fill-pen FillType/grad-mode FillType/startpos
		0.0 100.0
		0.0 1.0 1.0
		0.0.0 255.255.255 0.0.0 255.255.255 0.0.0
		polygon 20x20 80x20 80x80 20x80]

view layout [image img]

Louis: it's hard to say without having the source. Using the new 
SDK with the old SDK sources will probably not work. I think your 
problem is probably a change in VID (the latter error you report 
is from LAYOUT parsing values), so you should probably check your 
layout blocks (and related code). Try to run them from View and see 
what could be wrong.

t: copy [] a: insert-event-func [append t event event]
view layout [button "unview" [unview]]
remove-event-func :a
print length? t

mixing vid with rebgui has also some api-problems. some i found:

 /action: has in vid this args: [face value]. value is something usefull, 
 like area/text, slider/tdata, first text-list/picked etc. maybe its 
 not needed, "value" saves not much to "face/text". but supporting 
 that arg would be compatible

 /init: in vid this is a block and 'done. in rebgui it is a function. 
 vid has the advantage that init can be easily extended in substyles, 
 just add to it. rebgui has locals because it uses a function.
 /init2: not called by vid. 

resizing: not in vid, but one could write a /resize and plug it in 
the vid-face.

also there are some global changes which may break other things (removing 
event-func and changing global face IIRC).


If there is interest in making such small changes, i would help with 
making the rest compatible. adding #xh - parsing to 'layout and such. 
for "keep small" rebgui could have a "load-time-flag" to decide about 
using vid-stuff or all own.

What i would really like is rebgui for complex style-building (area 
with slider etc). this is closer to raw faces. and vid for quickly 
writing "pages", IMHO it has a rest of advantages there. (maybe not, 
i am a rebgui-beginner).

win: layout [Text "Hello"]

win/feel: make win/feel [detect: func [f event] [if event/type = 
'key [print [event/control event/shift event/key]]]]
view win

If anyone can work out why popup/away doesn't work from within display 
(by uncommenting the display line and commenting the view line), 
please let me know.

	REBOL []

	do %rebgui.r

	;display "test" [
	view layout [

  button "Click here" [show-popup/away make system/standard/face [] 
  do-events]
		text "Then here."
	]

	do-events

It would be very good to get this working [with RebGUI].

perhaps I need to display/layout, and then use hide ?

Got it.
Use a 

do [ widget/show?: false ] 

in the layout.

The following *should* work:

	display "Test" [text false]  or  [text #[false]]


But don't for some reason (the layout parser checks for it). I'll 
fix this for the next build.

lay: layout[text "1" text "2"]
probe lay/pane/1/text

Latest build available at: http://www.dobeash.com/files/RebGUI-032.zip


*** Unzip this file into your existing RebGUI 0.3.0 distribution. 
Requires View 1.3. ***

Highlights include:

	- New keycode handler (to assign keystrokes to actions)

 - Tab focus expanded to include button handling (see %focus-demo.r 
 for details)
	- Buttons are now image based
	- Number of password widget fixes

 - Added basic SVG support (proof of concept at this stage - shadwolf 
 is working on *real* SVG support)
	- Added icon and svg-toolbar widgets to support above
	- Large number of bug fixes

 - Bit of code refactoring (split layout logic out of display function)

The trick of para is to share, to save space. else we could just 
do it in 'layout.

Latest build available at: http://www.dobeash.com/files/RebGUI-034.zip


*** Unzip this file into your existing RebGUI 0.3.0 distribution. 
Requires View 1.3.1 ***

Highlights include:

	- request-dir requestor updated
	- alert and question requestors added

 - Tab focus expanded to include edit-list handling (see %focus-demo.r 
 for details)
	- Button image now resizes correctly

 - text-list widget totally rewritten to use [newly documented] View 
 1.3.1 iterated faces
	- text-list now supports Ctrl+click, Shift+click, Ctrl+A

 - text-list scrollbar now reacts to current display state (eg. disappears 
 if not required, alters dragger ratio as rows are added, etc) 
	- check and radio widget aesthetics improved

 - added options support to layout function and text-list and check 
 widgets

 - changed base-size from 4x5pixels to 5x4 pixels (better granularity)
	- reworked all widget sizes to account for above
	- fixed scaling problems with many widgets
	- updated focus-demo.r

 - greatly enhanced and expanded %tour.r to demonstrate more variations 
 and usage cases
	- added "live" unit-size and font-size drop-lists to %tour.r
	- numerous other minor bug fixes and coding improvements

In the works


 - table widget being rewritten along the same lines as the new improved 
 text-list widget
	- aiming for a 0.4.0 beta release prior to DevCon2005

But you could prevent the layout from beeing smaller, even if not 
fully visible? Instead of having negative offsets or this 0-thing?

i would use a combination, window with min-size, but if min-size 
is smaller than min-layout-size, dont shrink layout further. keeps 
at least layout intact and user can resize back.

since users (or Pekr;) see a destroyed layout the current way.

But this allows you to resize a window below an invisible threshold 
only to have your resize [partially] ignored when the layout jumps 
back to it's minimum size. I still maintain that setting a realistic 
min-size is not only subjective but the role of the GUI designer 
... if RebGUI tries to infer this setting it will invariably get 
it wrong ("why did it let my title field shrink to less than three 
characters ... everyone knows a one-char field is useless" type of 
issues).

My preconception is that adding the graphical layer complicates things 
too much 

 -- A valid concern in many environments, but VID is great, and simple, 
 for simple things.


view layout [button "Show help" [alert "Sorry, I can't help you"]]


No need to manage the event loop, no redraw handlers (until you need 
to get into them of course), just put an action block after a face 
style and it binds to it automatically.

Here is simplified your problem:
ke: func[f e][ if e/type = 'time [print now/time/precise] e]
insert-event-func :ke
view layout [box with [rate: 10]]


But I cannot help you. I'm not a view guru. It looks you should not 
use insert-event-func if you don't want to get all time events.

Use somethink like:

view layout [
	box with [
		rate: 10
		feel: make feel [
			engage: func [f a e] [
				if a = 'time [print now/time/precise]
			]
		]
	]
]

If you want just blinking cursor, don't use insert-event-func, but 
just something like that:
cursorMover: func[f e][
	if e/type = 'key [
		switch e/key [
            up    [cursor/offset/y: cursor/offset/y - 10]
	        down  [cursor/offset/y: cursor/offset/y + 10]
            left  [cursor/offset/x: cursor/offset/x - 10]
            right [cursor/offset/x: cursor/offset/x + 10]
		]
		show cursor
	]
	e
]
insert-event-func :cursorMover

view layout/size [
	cursor: box 10x10 with [
		rate: 10
		colors: [0.0.0 255.255.255]
		feel: make feel [
			engage: func [f a e] [
				if a = 'time [
					f/color: first head reverse f/colors
					show f
				]
			]
		]
	]
] 400x400

It looks like the event function isn't being triggered for the box, 
but rather for system/view/screen-face or something -

>> ke: func [f e][if e/type = 'time [print f/text]]
>> insert-event-func :ke
>> view layout [box "Testing" with [rate: 1]]
none
none

None of them print "Testing", as a call from the box should

What could be problem with this script?

set-net [[user-:-mail-:-com] smtp.mail.com pop3.mail.com] 
today: now/date
view center-face layout [
		size 340x120
 		button "Send mail" font [size: 26] 300x80	[

    send/attach/subject [user-:-mail-:-com] "" %"/c/file.xls" reduce [join 
    "Today  " :danas]
 			quit
 		]
	]

I get this error:


** User Error: Server error: tcp 554 5.7.1 <[user-:-mail-:-com]>: Relay 
access denied
** Near: insert smtp-port reduce [from reduce [addr] message]

Could it be some security issue?

It worked with previous internet provider... A week ago we changed 
it and now this happens...

Should I contact my provider to change some security settings or 
should I change something in the script?

rgba-to-int: rebcode [r g b a][
	lsl a 24
	lsl r 16
	lsl g 8
	or a r
	or a g
	or a b
	return a
]

draw-pix: rebcode [r g b a][
	apply a rgba-to-int [r g b a]
	poke img 1 a
]

update-pixel: does [
	do draw-pix col/1 col/2 col/3 col/4
	probe img
	show i
]

col: 0.0.0.0
img: make image! 1x1

view layout [
	backcolor black
	i: image img 100x100
	scroller 200x16 [
		col/1: to-integer face/data * 255
		update-pixel
	]
	scroller 200x16 [
		col/2: to-integer face/data * 255
		update-pixel
	]
	scroller 200x16 [
		col/3: to-integer face/data * 255
		update-pixel
	]
	scroller 200x16 [
		col/4: to-integer face/data * 255
		update-pixel
	]
]

dot looks like a space and spaces are veryimportant in rebol-layout. 
i would not use that.

An image can be used as a backdrop to a layout.  Stick some fields 
on top and you're done.

What is better?

view layout [at 20x20 image http://java.sun.com/j2se/1.5.0/docs/guide/awt/1.3/designspec/images/hips.sm.gif]
or
import f3.ui.canvas.*;
import f3.ui.*;

Canvas {
    content: Group {   
        transform: translate(20, 20)
        content: ImageView {
            transform: []

            image: Image { url: "http://java.sun.com/j2se/1.5.0/docs/guide/awt/1.3/designspec/images/hips.sm.gif"
            }
        }
    }
}

I'm able to get a large set of results from mysql and use it (View 
the images in a layout) but when I try to insert this data into sqlite 
it seems to get currupted...
It sounds like a sqlite problem...

SLIDER in the layout and then use /data to extract the position which 
is between 0 and 1

nope, I made a little layout that works like a preview

font1: make object! [
		name: "Nimbus Roman No9 L"
		style: none
		size: 33
		color: 255.0.0
		offset: 2x2
		space: 0x0
		align: 'center
		valign: 'center
		shadow: none
	]

font2: make object! [
		name: "Nimbus Roman No9 L"
		style: none
		size: 13
		color: 0.0.0
		offset: 2x2
		space: 0x0
		align: 'center
		valign: 'center
		shadow: none
	]

view layout [box 500x700 white effect [draw [
	box 0x0 493x698 
	fill-pen none 
	box 0x0 493x698 
	line-width 0 

 font font1 pen 255.0.0 text vectorial "REBOL PostScript Dialect" 
 59x68 
	pen 0.0.0 line 59x104 431x104 

 font font2 pen 0.0.0 text vectorial {With this dialect it's possible 
 to easily produce PostScript output.} 79x121
]]]

>> layout [ a: text "this is a line" font [ size: 20 ]]
>> line-list: make system/view/line-info []
>> textinfo a line-list 0
>> probe line-list
make object! [
    start: "this is a line"
    num-chars: 14
    offset: 2x2
    size: 104x23
]
>> layout [ a: text "this is a line" font [ size: 12 ]]
>> textinfo a line-list 0
>> probe line-list
make object! [
    start: "this is a line"
    num-chars: 14
    offset: 2x2
    size: 68x15
]

anyhoo:


img: draw make image! 297x210 compose [pen red font (make face/font 
[size: 30]) text (as-pair center "BOOM!" 297x210 make face/font [size: 
30] 20) "BOOM!"]
view layout [image img]

If you look at my layout examples above, you can see that the font 
size is not the same as the point size used in View.

Is this indicative of the current problem?

>> foreach typeface ["arial" "times new roman" "verdana" "trebuchet 
ms"][

[    layout [tx: text font [name: typeface size: 10] do [probe second 
size-text tx]]
[    ]
13
12
12
15

I think we don't have many choices - you can to-image your layout, 
or go for external engines, using some make-docs - pdf, postscript, 
html plus css standard ...

www.rebol.com opened OK in NeoOffice, and I could change to "Print 
Layout". Right-margin is not perfect (as often with HTML, because 
it isn't a wysiwyg format), and it can probably be configured. Saving 
as PDF gave me exactly what was seen on the screen.

the point of having this dialect is to create page templates for 
viewing data from databases or whatever.  The text is replaced either 
by evaluation or by compose, and you have your draw layout.

r: rot: 0 view layout [origin 0 box 400x400 white effect [draw [pen 
black translate 200x200 rotate

 rot translate -200x-200 box 100x150 300x250]] rate 0 feel [engage: 
 func [f a e][if a = 'time [r: r +
 1 rot: 360 // 360 - r show f]]]]

yes, it can become very powerful. one could actually build a system 
like LAYOUT this way to build PS documents.

I have problem with an image like in this example:

do http://home.tiscali.dk/john.niclasen/postscript/postscript.r
img: to-image layout [box 20x20 red box blue]

write %imagetest.ps postscript [page [translate 100 400 scale 72 
72 image img]]


Try print (or view) the imagetest.ps file. Do you also get an error?

Sorry, that I find it hard to understand, what you mean from time 
to time, my fault. I get you now. I would put things like margins, 
linespace, vertical position within tables, etc. in a dialect above 
the postscript dialect level. Doing it that way, the same postscript 
dialect can be used for all sorts of layout engines, because it has 
little restriction.

Quilt user interface layout spec examples ?

Do they have graph-layout included?

Many games operate with Truevision TGA image files, also known as 
TARGA file format. I've made a function to load such a format:
http://www.fys.ku.dk/~niclasen/rebol/libs/gfx/tga.r
Usage:
i: load-tga %some-file.tga
img: i/as-image


img is now a REBOL image! type image, that can be viewed as normal, 
e.g.:
view layout [backdrop black image img]

REBOL []


colors: [
; 7 primary colors
	bn-green 		0.102.76
	green-field 	51.133.110
	reed-green		102.163.146
	patina-green	153.194.183
	glass-green	204.224.219
	light-green	232.241.239
	ash-gray			209.209.209

	; 7 secondary colors
	midnight 			0.29.43
	foggy-morning 	31.93.154
	hazy-day 			102.154.204
	light-mint			154.204.205
	terra-cotta 		205.153.103
	desert-sand		229.201.115
	sunflower			254.191.0
]

change-colors: func [val /local h hsv][
	forskip colors 2 [
		hsv: rgb-to-hsv colors/2
		h: hsv/1 + val // 255
		hsv/1: h
		colors/2: hsv-to-rgb hsv
	]
	~b1/color: colors/bn-green
	~b2/color: colors/green-field
	~b3/color: colors/reed-green
	~b4/color: colors/patina-green
	~b5/color: colors/glass-green
	~b6/color: colors/light-green
	~b7/color: colors/ash-gray
	~b11/color: colors/midnight
	~b12/color: colors/foggy-morning
	~b13/color: colors/hazy-day
	~b14/color: colors/light-mint
	~b15/color: colors/terra-cotta
	~b16/color: colors/desert-sand
	~b17/color: colors/sunflower	
]

lay: layout [
	across
	~b1: box colors/bn-green
	~b2: box colors/green-field
	~b3: box colors/reed-green
	~b4: box colors/patina-green
	~b5: box colors/glass-green
	~b6: box colors/light-green
	~b7: box colors/ash-gray
	return
	~b11: box colors/midnight
	~b12: box colors/foggy-morning
	~b13: box colors/hazy-day
	~b14: box colors/light-mint
	~b15: box colors/terra-cotta
	~b16: box colors/desert-sand
	~b17: box colors/sunflower
	return
	button "change color" [change-colors 64 show lay]
]
view lay

REBOL produce a green result here, when scaling the test image to 
half size.


view layout [image http://www.4p8.com/eric.brasseur/gamma_dalai_lama_gray.jpg
image http:
//www.4p8.com/eric.brasseur/gamma_dalai_lama_gray.jpg 129x111]

DRAW produces a gray result:


i: load-image http://www.4p8.com/eric.brasseur/gamma_dalai_lama_gray.jpg
view layout [box 200x200 effect [draw [scale 0.5 0.5 image i]]]