World: r3wp

to declare the related facets in style.

if some facet is calculated, it could declare that in the /explicet-part. 
but maybe to complex.

You mean when using set-face/get-face ?

yes. and i guess your list-filling does something similar, to save/restore 
facets?

I thought about this pretty hard for shell-list.

save/restore-iterates ("iterates" is my word for "iterated facets") 
remain simple at this stage - they use only GET and SET at present.

You are right, that is faster.

shell-list allows functions to be placed in the map dialect block, 
which is kind of like your /explicit refinement above. The automatic 
iterates are found in the default-iterates block.

Volker: funny about get-set you know. Some time ago I objected, that 
'get-face, 'set-face should be made more general and accept additional 
parameter, so that you would simply use parameter name to set it, 
so e.g. set-face 'color value .... etc.

and some ppl objected that going such way would complicate the thing 
and that we would ended like VB, Delphi or other tools with tonnes 
of parameters to set. I still think that current version of set-face, 
get-face is not thought out properly!

I think thare are two slightly different goals. One is to deal with 
the main data in a face. That should be a single value. The other 
is to make a snapshot of a layout, save it, qui script, and reload 
it later. I like that behavior. And i am not sure a single value 
is sufficient for that. But it would be an internal thing about saving, 
as api i prefer something with more defaults, ala VID.

I would prefer SET-FACE, GET-FACE to be named SET-VALUE, GET-VALUE. 
Cause in fact, it's what id does :

But set-value and get-value are too generic names to be restricted 
to face accessors.

correct me if I'm wrong, but I seem to remember that VIEW can set 
a minimum size a window can have using /options 'RESIZE ?

'minsize ?

it seems to respond to 'min-size but won't accept a pair! value...

view/options layout [ size 200x200 title "test" ] [resize min-size 
100x100]

interesting... thanks. Is this in the docs anywhere?

dont know. remember it from some chat. :)

why of course :-) I can't even see it in '? view'

one would think it's a pretty important feature

put in RAMBO?

Thought that too.

I'm putting it in... can't see it there

done

I wonder why some guy take time to make doc : http://www.rebol.com/docs/view-system.html#section-4.5
;-)

I somehow don't understnd .....

It's an answer to Henrik "interesting... thanks. Is this in the docs 
anywhere?"

:-)

This goes for me too, but it's probably better to ask in RAMBO group 
before adding to the bug database.

didec, thanks. I posted a RAMBO entry about it not being mentioned 
in the console help.

What makes the 'area vid-style to interpret the "^/" chars correctly? 
What has the 'area more than 'text to let it show texts on multiple 
lines?

svv/vid-styles/area/flags ;== [tabbed on-unfocus input]

svv/vid-styles/field/flags ;== [field return tabbed on-unfocus input]

view layout [field 200x48 with [deflag-face self return]]

do http://www.lexicon.net/antonr/rebol/demo/text-swirl-fade.r

Everyone's experience will be different.

Use the keyword 'as-is

Anton - I navigated each single 'area word but I couldn't find the 
reason. I didn't think that the difference was in 'field instead. 
Thank you!

Chris - 'as-is works too, but what is it? I coundn't find it nowhere.

It's a flag in the 'text style that will prevent face/init from doing 
a trim/lines on the face/text.

probe get in get-style 'text 'init

Thank you :-)

I can't seem to figure out the solution to do this elegantly: If 
I have a pane with 4 faces [a b c d] and I want 'b to move to position 
'd: [a c d b], is there no easier way than to copy, remove and append 
'b?

ah, found something that seems to work. never mind

Would it be a good idea to open source the Viewtop editor just like 
it happened with the Viewtop? It has a lot of obvious bugs that could 
be fixed by people outside RT.

(or is it a part of the Viewtop?)

Its part of Viewtop (vt-editor.r).

But it as been update in View 1.3, so current ViewTop sources are 
outdated. Unless it has been re-release, but I'm not aware of that.

Its now in the beta-sdk, dont know how public that is. and you can 
get the source by "probe ctx-edit" from a fresh console. but without 
comments then.

In IOS there is a flag that allows, the users default editor to be 
used instead. It was proposed to implement that in the view desktop 
as well, I'm not sure if it got in there.

just redefine 'editor and use call. but i like the inbuild one for 
quick things.