World: r3wp

each node in the stream handles only one condition or type of manipulation. 
  the most obvious way to show how this is cool, is when you handle 
keys.

you can have a special node in the stream which replaces certain 
strokes with others... executing macros, or inserting a whole stream 
of text, even if the app doesn't really support it.

so you could insert the clipboard right in the inputs instead of 
having to support it explicitely in the various face styles... as 
a high-level example.

I even realised that we could add drag and drop OVER a fully working 
apps, sending the events to an external handler.. this allows things 
like interactive face manipulations while the app is running...  
:-)  cool for visual app dev... and its completely non-intrusive 
to the code of the running app.  the app just never receives certain 
events when a series of events occurs... and no need to play in the 
face's individual handlers either  (which is the biggest feature 
IMHO:-)

is that what liquid does?

I built the stream using a purpose built liquid node.  liquid is 
a generic core reference for dataflow programming.

and it comes with a reference (and fully functional) multi-purpose 
node called a plug which allows you to mix and match many types of 
dataflow nodes using the same node.

I propose a very simple enhancement to BTN to the official VID to 
allow the inclusion of images directly via layout. It adds 7 lines 
of code to the BTN init: http://hmkdesign.dk/rebol/img-btn/img-btn.r

Please study the source for commenting/enhancements. Thanks.

I have a problem with field and key in the same layout:

view layout [
	field
	key #"t" [alert "key: t"]
]


If I click in the field and try to enter a "t", the alert pop up. 
I'm doing this under OSX. Is it the same on other versions of View?

Geomol, it's the same in Windows

I'm wondering, why I haven't noticed this before, or maybe I have 
and forgot about it.

Is there a work-around?

Should it be RAMBOed?

yes, I think it should

I've put it in RAMBO.

I wonder if I should put my proposal in RAMBO now as well, but I'd 
like the code to be approved here first...

Tests do show under OSX that the color bug afffects the display of 
images in buttons.

It's the same in Linux, too - just came across it a couple of weeks 
ago

(Ubuntu)

*a couple of days ago

Geomol, here is a fix:

system/view/window-feel/detect: func [face event][
    either all [
        event/type = 'key 
        none? system/view/focal-face ; <--- added this line
        face: find-key-face face event/key
    ] [
        if get in face 'action [do-face face event/key] 
        none
    ] [
        event
    ]
]

view center-face layout [
	key #"t" [print "action"]
	field with [focus self]
]

(not well tested, but looks good.)

We should have checked RAMBO database - Romano posted this one three 
years ago
Do not detect hot-keys when a focal-face with caret is active
http://www.rebol.net/cgi-bin/rambo.r?id=3372&

hum... I have the draw docs for AGG but it seems the gradient fills 
are (as usuall with rebol it seems) so documented, such that We have 
no real clue how the values change or what are the basis...

has anyone done some complement docs to describe things like the 
offet and grad-scale ?

ok... the examples after give a few clues...

hum... is it just me or should the minimum colors needed for the 
gradients be 2 ... is there really a reason why we need to put 3 
colors?  its seems like it messes up most of the fills...

yes, I think gradients are quite hard and non-intuitive to do in 
DRAW

hum... a yellow green blue gradient  give me a ring of BLACK right 
in the middle... not what I call very precise... maybe cyphre could 
explain the maths behind the gradients so we can understand  what 
we are doing?

somehow, it seems like its missing a color blend mode selection, 
multiply, add, screen, etc. right now its a ramp which fades to 0 
on each side, such that when two successive colors do not have any 
bit in common it creates an alpha channel premultiplication grey 
zone...

henrik... any tips you can give me to make it less painless?

since you've played with it a while.

no, it took a lot of fiddling to get things right. I only played 
a bit with Gradient Lab, but it's not very flexible.

it seems like using alpha gives better results, when combining with 
bg colors.

I think Gradient Lab should be made into a useful tool, rather than 
just show off gradients.

I'll build a few usefull nodes in liquidator... its almost ready 
for a first public show-case  :-)  I never thought it would be this 
quick.

A just-in feedback message to REBOL.org:
<<

How to find the documentation for the use of VID and RebGUI} description: 
{Hi;

I find the RebGUI is good, but how can I find the help document for 
the use of this package?

the wewpages in the website donot tell people how to use his software.

How to find the detalied documentation for VID? like how to build 
botton, box, drop-list,combo list?

It seems Rebol is weak in teaching people about how to use the GUI.

Normally people like to learn software quickly, so a good help documentation 
is always welcome.
Thanks,
>>

Can someone give me a useful list of URLs to pass on to the enquirer? 
Thanks.

Maxim, Henrik: I agree current DRAW gradients aren't the best solution 
and I'm aware about this issue from the time Shadwolf's requests. 
But this improvement will happen probably once the new 2.7.x release 
merge get to more stable state. As you might know Carl don't want 
to add new features until 2.7.x is at the same level like 1.3.2.

Sunanda: I think there is couple of good View documents directly 
on rebol.com: http://www.rebol.com/docs.html

Thanks Anton! :-)

cyphre, I realised that drawing two shapes and using alphas to blend 
between them is the best additive method so far... its obviously 
a little bit slower, but at least it looks good.

once we understand how the values work I guess its ok... there should 
just be a little bit more info on the fact that things like grad-start 
are in pixel distances...  it might seem obvious... but with my background 
in CG I was expecting shape size relative scale.  Its ok, as long 
as the info is made explict  :-)

a wish?  allow two color gradients ... I now understand  the middle 
color is used as a curve to bend the way the gradient occurs, but 
in many case a linear curve is all that's needed. especially since 
we can edit the start/end of the gradient.

(just my two cents ;-)

How to find the documentation for the use of VID and RebGUI

 How about Desktop|Demos|EasyVID? Sounds like he wants a step-by-step 
 introductory tutorial. I'll think about how I can address this need 
 for RebGUI (my site makes the assumption that people are somewhat 
 familiar with VID already). Thanks for the heads-up.

Thanks Cyphre and Ashley......I should of course have asked in the 
!RebGui group

Maxim: I agree. There should be more info about the arguments. And 
yes, the need for 3 colors is just because the current gradient interpolation 
uses curve (this was some default AGG code we have used for DRAW 
but  now I think it would be better to rewrite it from scratch. The 
new code will use linear interpolator among other changes.)

re your wish: I'll try to add 2 color arg possibility. At the moment 
as a workaround you can easily compute the 'middle' value and use 
3 args insetad.

thanks for the heads up... If you are going to rewrite it... please 
allow more selections in this kind of thing... curved interpolation 
IS much better, for things like shadows, for example... but the need 
to select filter types (from all available... not just one or two), 
interpolation curve types, start-end snap on beziers, things like 
this are all essential, if we want to allow the next REBOL to be 
able to properly compete.  


defaults are good and often this is all that is needed, but for any 
graphic app, this quickly becomes essential (as you will agree, on 
your own usage), and is a weekness of current toolset.