World: r3wp

Yes, that is a valid interpretation as well (things like that are 
not a good thing to do in REBOL). I do think that you can't give 
a more "rebolish" implementation without the context (that's the 
whole point of REBOL).

Is this helpful?

>> trim none

** Script Error: trim expected series argument of type: series port
** Near: trim none

What harm would there be in ignoring none?

I guess it's about the propagation of NONE. If TRIM is used as part 
of a larger concatenated string, you could be forced to handle the 
NONE case after TRIM.

I'm having difficulty using the find function to find an image in 
an image. The image specification seems to indicate that this should 
be fine. Is this a known issue?

Can you give an example where it doesn't work?

;Rule30
rule30: to-image layout/tight [box 6x1 yellow edge none]
foreach n [2 5 6] [poke rule30 n orange]

;Img
screen: system/view/screen-face

img: draw make image! screen/size  reduce ['pen 'yellow 'fill-pen 
'yellow 'box 0x0 screen/size]


img: at img img/size/x / 2
change img orange
img: at img -2x0
width: 3


it: copy/part rule30 3
find img it

;simpler

i1: make image! [60x60 #{FFFF00FFFF00FF960AFFFF00FFFF00FFFF00FFFF00FFFF00FFFF00FFFF00
FFFF00FFFF00FFFF00FFFF00FFFF}]
i2: make image! [3x1 #{FFFF00 FF960A FFFF00}]
find i1 i2

any thoughts?

Am I doomed to convert the image to binary?

;this works

find i1/rgb i2/rgb

it's broken since a while

can someone rambo this?

how does one rambo?

http://www.rebol.net/cgi-bin/rambo.r

This is the bug database for R2 and before

please check also if this bug exists in R3.

ok

check out this groovy cellular automaton I made with rebol  http://docs.google.com/leaf?id=0B37bnU84uDb5OGE4YWFiNzUtNmM4ZC00Zjg2LTg5OTYtMzMwNGYzNmMxNzE1&hl=en

view layout [ f1: field button "test" [ context [ view/new layout 
[ f1: field "testing" ]]] button "F1 value" [ probe f1/text ]]


why does the context not prevent the second f1 overwriting the first 
?

because LAYOUT sets set-word!s globally. they don't exist in a particular 
context.

because make object! only scans for set-word!s in the main block, 
not sub blocks.

view layout [ f1: field button "test" [ use [ f1] [  view/new layout 
[ f1: field "testing" ]]] button "F1 value" [ probe f1/text ]]

this works though

>> context [do [f: 'something]]
>> f
== something

so you need context [f1: none view/new ....]

I don't want it to overwrite the f1 I have in the global context

see the VID-CONTEXT function here: http://www.colellachiara.com/soft/libs/utility.r

or, if you want a more general solution, see my implementation of 
modules: http://www.rebol.it/power-mezz/mezz/module.html

thanks .. you've got module for everything!

i guess 11 years of reboling pay off sometimes :-)

absolutely

so this is like a 'funct for layout

yes. it's still main block only iirc

but i found it very useful with VID

MODULE instead scan sub-blocks as well and preserves globals by copying 
them.

I guess I was incorrect. 8 years of REBOLing is not enough.

how exactly do you use it?

layout vid-context [....]

it will make set-words in there local. i think i had a refinement 
to also get the context in case you need to access it...

ok, should work for rebgui too then

vid-context/to

yep, vid-context/to [...] 'word

(it's a small function so you can easily modify it to fit your needs, 
as well)

I have a screen ( VID) and a function that loads values into that 
screen.  I was hoping to reuse that screen elsewhere by enclosing 
into an anonymous context, and use the function that loads the data 
with the same.

so does it make sense to fix make object! to scan for set-words in 
the sub blocks?

You might end up with some rather large objects with lots of redundant 
words - perhaps not so useful for data modelling...

Well, instead then a context function that deep scans for all set 
words

I want to be able to reuse these screens I have defined elsewhere 
and the functions that operate on these screens without overwriting 
the original values ...

c: does [ f/text: "hello" show f ] view layout [ f: field button 
"New" [ context [ f: g: none bind [ c ] 'g view/new layout [ f: field 
button "test" [ c ]
] ]]]


this doesn't work ... pressing the test button sets the f field in 
the first window and not the second

c: does [
	f/text: "hello" show f
]
view layout [
	f: field
	button "New" [
		context [
			f: g: none
			bind [c] 'g
			view/new layout [
				f: field
				button "test" [c]
			]
		]
	]
]