World: r3wp

ah, that is simple...thanks.

there is some caret functions for decoding relative position too, 
but I havent used them in years.

caret-to bla bla bla

bla bla bla to-caret

sounds like "eh, what's up, doc?"

ahh, offset-to-caret

and caret-to-offset

is that for drag-selecting text?

you would use it to implement text dragging possibly. offset-to-caret 
 returns the position of text relative to a graphical position x/y.

i assume you have probably already used highlight-start and highlight-end.

no, I have just used text-area for stuff like that...now I need to 
change the behavior of it some.

it's a skinny caret on the left side of the area...but thick everywhere 
else.

sel-start: does [
	if none? system/view/highlight-start [return none]	

 if (index? system/view/highlight-end) < (index? system/view/highlight-start) 
 [
		return system/view/highlight-end
	] 
	system/view/highlight-start
]
sel-end: does [
	if none? system/view/highlight-end [return none]	

 if (index? system/view/highlight-start) > (index? system/view/highlight-end) 
 [
		return system/view/highlight-start
	] 
	system/view/highlight-end
]

try para [origin: 4x4]

understand...but that is there already...origin: 4x4 I mean

BTW: The above functions keep sel-start as a lower index position 
than sel-end. These can be either way with highlight

cant replicate the skinny caret. view layout [area]

is there some old discussions on this where I can read some discussions?...I 
don't want to hog the channel as I play text area catch up.

Dont know, I figured it out largely by examining the ctx-edit object 
(view editor)

ah, cool, I will play with that some.  Aren't you making an editor 
of some type?

A rebol code editor.

ah, one that is syntax sensitive, right?

I have played with that, but not this one.

it does do some code interpetation, but just for generating a manifest 
for function libraries.

halfway there.

cool. Thanks for the ideas, I am going to go back and bang on it 
for the rest of the night...

same here, cya!

Is there someway to do this.. 

X: [btn: "test" [print "test"]]

view layout [ X ]

View layout X should work
(You probably don't want the colon on btn)

>> x: [btn "quit"[]]
== [btn "quit" []]
>> view layout [x]
Unknown word or style: x
>>

view layout x    -- x is already a block/.....No need to put in in 
another one.

ok, but how can i form the X code and use it within a layout?

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 ]

I"m not just doing X, i might do Y and Z as well.

but you didn't say that ...

Terry, you probably need a lot of Composes in that case.

The Vid dialect has ti survive the Do's, so you may need to use more 
lit-words  {'button rather than button)

this works

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

You said you might need to Do it firstL
Try
 x: [quit]
 do x
to see the problem here if you do need to use do first.

Hmm, i was just wondering if there is a way to use  'words to represent 
some vid code, be it a button, area... whatever.

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

another way is to use styles. if you want a customized button.

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

eFish -- note that Romano has a patch for the ctx-text object: http://www.rebol.it/~romano/#sect2.2.
 You could explore that too...

Terry, I'd suggest either 'compose or 'stylize (or 'stylize/master).

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