World: r3wp

when you say the same thing, what do you mean?

The first time (when the console pops up) it is set to none, but 
after that it will work alright

Thanks for looking into it

when I type and then highlight without changing the focus, and then 
click the button, the field is unfocused and the highlight is none. 
this actually seems like correct behavior, although you would want 
to retain the highlight.

try it more than once

yes, I did. there is clearly a pattern there.

I didn't even know about  'local-request-file

Doesn't work everywhere, though - 2.7.6 on Ubuntu Hardy:
>> local-request-file []
** Script Error: Feature not available in this REBOL
** Near: local-request-file []

read this link:       http://www.mail-archive.com/[rebol-list-:-rebol-:-com]/msg12381.html
but in my REBOL, 2.7.7.3.1

'local-request-file always returns 'true and 'false,   what does 
this mean.

local-request-file is only available for Windows and Mac ... and 
the Mac version supports a subset of the functionality available 
on Windows (e.g. no multi-item selection). Two simple examples of 
usuage:

	open-file: make function! [
		/dir path [file!] "Default file name"
	][
		all [ 

   local-request-file path: reduce ["Open" "" clean-path %. either dir 
   [compose [(path)]] [copy []][][] false false]
			join third path first fourth path
		]
	]

	save-file: make function! [
		/dir path [file!] "Default file name"
	][
		all [ 

   local-request-file path: reduce ["Save" "" clean-path %. either dir 
   [compose [(path)]] [copy []][][] false true]
			join third path first fourth path
		]
	]

Floyd-Steinberg dithering:
do http://box.lebeda.ws/~rebolek/rebol/dither-fs.r
Not the fastest thing around, I know.

R3? It complains about map!

>> do http://box.lebeda.ws/~rebolek/rebol/dither-fs.r

Script: "Floyd-Steinberg dithering" Version: 0.0.1 Date: 30-Jan-2010

** Script error: invalid argument: [0.0.0 63.63.63 127.127.127 191.191.191 
255.2
55.255]
** Where: make catch either either applier do

** Near: make map! [0.0.0 63.63.63 127.127.127 191.191.191 255.255.25...

Ah, I'm testing it under 2.7.7

I'll change it to hash! that should be OK then.

ah, ok. I don't use 2.7.7 as I have a big project that relies on 
2.7.6 and don't want to mess it up.

Reuploaded and tested under 2.7.6

cool it works. what do you mean by "slow"? :-) well, it was done 
when I came back to the desk.

I think you should post it on rebol.org as an educational script.

Good idea, I'll improve it a bit and post it.

the BW version is quite fast... good enough for print preprocessing 
 :-)

facet question http://synapse-ehr.com/forums/showthread.php?15-REBOL-DOCUMENTAION-suggestions-for-improvement/page2#post133

Posted a response.

This "with	The with block allows you to specify any other type of 
face characteristic using standard REBOL object format."


is therefore incorrect as it does not allow one to set the offset.

http://www.rebol.com/docs/view-guide.html#section-78

it's not incorrect. it's specifying offset alright. it's just being 
overridden later in the face setup during layout. :-)

one could imagine an additional layout mode, where the cursor doesn't 
move, and therefore the offset from 'with would be applied correctly, 
but really, 'at is the shortest option to type of all.

I would have thought the layout engine sets the offset before it 
sees the 'with ...

it does so internally for the cursor, but the cursor position is 
not applied to the face until after the specs are in place.

VID was a revolution at the time of its invention .. but we hope 
that it will be soon superceded by R3 GUI  and we won't have to worry 
anymore :)

yes, true

Few languages can lay claim to inventing new ways of doing things 
..  we just still need to prove it's viable :)

VID was never really finished. That's its only problem.

That could indicate a deficiency in the method of dialecting visual 
interfaces .. it's just not flexible enough

No, the dialect is simply a tool for building a face tree and it 
can be as complex as we want. Same in the R3 GUI.


How that face tree is otherwise managed during runtime (resizing, 
events, etc.) is up to other functions that exist elsewhere in VID, 
long after the role of the dialect is gone. What the VID Extension 
Kit does is add keywords for resizing and a few other elements, so 
the face tree holds a bit more information.


The resizing system is then used later to perform adjustments to 
the face tree, when you resize the window. That's just one example 
of doing only minor modifications to the dialect itself.

So, where is it failing?

Pareto failure?

It's all the "meat" that comes after using the dialect to generate 
the face tree. There just isn't enough functions to manipulate the 
face tree. VID is almost a misnomer in this sense, because the dialect 
only performs the very first part of controlling the UI. The rest 
is up to the meat.

I wonder why we can't build eg native windows guis the same way

It's been many years since I've used an IDE, but I recall selecting 
widgets and placing them on a screen, setting the Z order, and various 
properties for certain events.  Isn't VID just a RAD tool for doing 
this in a dialect ...

yes, and also for doing layouts programmatically, which you can't 
with a point'n'click IDE.

How often are you doing that though?

it's a very nice feature for doing certain lists and face-constructs 
(part of the VID Extension Kit)

Presumably in a completed GUI we wouldn't need to generate anything 
on the fly

Actually you would, and I'd hate to lose that ability.


http://rebol.hmkdesign.dk/files/admin.png<- the view in the center 
is built like that as well as the dynamic lists in the right hand 
side with the popups in them.

You're saying that you couldn't prebuid that?

that would be a complete nightmare to do

This is not obvious with VID, because you might build such a layout 
in a special setup, but in the VID Extension Kit, you have face constructs. 
A face construct is simply a style that accepts a particular dialect 
as input. The dialect is parsed into VID which then in turn generates 
an internal face tree. This means you can build styles that do something 
like:

view layout [
	paper [
		size a4
		dpi 300
		at 20x20 image bay.jpg
	]
]


The point is that every time you feed the paper new data, using SET-FACE, 
it's re-rendered from scratch using VID.


You can also build very complicated list views that dramatically 
change appearance and number of faces, every time you feed it new 
data.

The issue is that VID makes many things simple and so is very enabling 
in that respect.  But difficult things are close to impossible for 
seasoned users ...

Even now I see that having a true rich text we can type with is not 
possible in R3 gui