World: r3wp

the canvas engine took a few hours to make, & then the demo took 
a few hours more (mostly handling the events)  so although you could 
choose to make the tool using custom code and trying to fix all data 
relationships manually... using liquid allows one to do so very quickly 
and results in rather speedy code.

(and then I know that liquid itself can be made 10-25% faster by 
removing some of the debugging stuff :-)  but I'm waiting for my 
code compositor before strarting to mangle with release threads.

Maxim : Possibly, I can't remember exactly and it didn't cause the 
script to abort. I  couldn't recreate the error today.

k

Henrik, just reading your blog on Toolbar. It says the toolbar will 
stretch if its initial width is 0. I would like to point out the 
standard way used by other VID styles is to use -1.
(I haven't examined the source, so not sure of your intentions.)

it is? I thought it was 0. oh, well, I'll fix that.

That button-bar is a good idea, I think.

please, test it, torture it, play with it. :-)

Yes, let me try to find some examples...

foreach [style obj] svv/vid-styles [if all [obj/init find mold obj/init 
"-1x-1"][print style]]
BASE-TEXT
VTEXT
TEXT
BODY
TXT 
.....
print mold svv/vid-styles/text/init

of course this will only count for X direction as I haven't implemented 
anything for vertical button bars yet

Most button bars seem to be horizontal so it makes sense to limit 
the scope for now.

it does provide a "fancy" background gradient. maybe it should be 
removed?

-1 fix uploaded

I don't think the gradient is a problem. There was a time when I 
shunned the extra complication.

It's working as you need it, and looks good, right ?

yes... although it would probably be more "correct". then again, 
the defaults in VID also have a certain look. as long as it's simple 
to override, then it may not be a problem.

I would wait to see what actual needs arise as you use it, before 
worrying too much.

I get the feeling you are trying to make something more generalised 
for the wider public.

Well, it is a "sideeffect" of TOOLBAR. I just found that it's a simple 
way to make button bars with right aligned buttons. OK-BAR and OK-CANCEL-BAR 
are even simpler. I do have my own system for requests, as I think 
the ones that are built in are too ugly and simple, but I'm not sure 
if they are general enough for publication.

http://hmkdesign.dk/shop9.png<--- This kind of requesters.

Ok, TOOLBAR is based on VID-FACE, so let's first check if it has 
a words dialect.
	>> print mold svv/vid-styles/face/words
	none
Good, so we can set our own without breaking anything.
	toolbar: FACE with [
		; define DATA function in the style-specific dialect

  words: compose [data (func [new args][new/data: args/2 next args])]
	]

All this does is allow a slightly easier spec. Your example from 
the blog:
	view layout [button-bar with [data: [ok-btn cancel-btn]]] 
can now be:
	view layout [button-bar data:[ok-btn cancel-btn]]

Ok, it doesn't save you much in this one example, but over time, 
it will.

Sorry, correcting that last example:
can now be:
	view layout [ button-bar data [ok-btn cancel-btn] ]

oh, thanks for that one. I've been wondering for a while how to do 
that. :-)

I want that in LIST-VIEW as well

The words dialect is not terribly obvious how it works, because it 
advances the index of ARGS by one for you. You still have to remember 
to advance by one for every argument that you understand and consume.

maybe one should make a document on that...

Good idea.

document growing here:
http://anton.wildit.net.au/rebol/doc/vid-words-dialect.txt

explain first what WORDS does

it makes it possible for you in your style to provide words in the 
layout dialect to.. blabla

Yes, .. .hmm. I'm sort of approaching it from a different direction. 
Very informal style so far.

Ok, updated.

Oh my. That is uber cool document, and it should be part of VID docs. 
That really nicely explains, in very human fashion, how some internals 
work!

nice document there. will it stay where it is?

Nice work at that document Anton.

Permanent unless I move my site, but it should remain at that relative 
path doc/vid-words-dialect.txt

Thanks guys. I hope it's useful.

Hmm.  Anton has shifted sites 4x in recent years ... !

Why not just pay $5 per year and get a domain?

That would be another shift...

Ok... so it's "semi-permanent".

Maxim: very nice!

thanks... I can't wait to let you guys play around with all of this. 
 I am thinking of implementing magnets and physics within the editor.

what I think many developers would be willing to pay for is - real 
screen editor :-)

real screen editor?

yes, screen painter. That is the most missing part of the View scenario

oh... you mean a gui builder?

strangely I have found out that when using row/column engines like 
glayout (and others) I get 10 times quicker results than using any 
mouse driven, static page editor.

I wish I could say more about liquidator, but I don't want to increase 
the hype too much.  for now, I just wanted to share the first signs 
of successfully automated node creation  :-)