World: r3wp

we have to nodes A et B

when A is modified B is updated

all members of a pipes are equal owners of the same value.

when B is modified, A must be updated

yes... already part of the engine... and again... the magic is doing 
so with the same actual object class   :-)

godd

goog, sorry

*good

and its all VERY stable.  I've already got a view engine running 
the exact thing you describe where a scroll bar updates a field and 
vice versa... although one is a decimal and the other a string.

the nice thing about the pipe engine is that you have bidirectional 
data filtering.  when you SET the data, your pipe can unify it to 
some internal value, which is considered the real value.

i think i could work an a new concept of rebol script editor with 
liquid

then each member (including the one you modified the pipe with ! 
:-)  can then again, clean it up for its own use.

with a draw engine

pipe^s are so cools ^^

HAHAHA why do you think I have been designing liquid for the last 
4 years (and actually more, in design :;-)

,-)

liquidator my current project will change how we can develop apps. 
 its not just a "code" editor... its a data editor.

any data.

graphic designs piped into button images, and docs... change the 
shapes, and see your running application's bitmaps update while you 
are editing the image in the vector paint package  :-)

robber  ^^^

well depens, This is a 14 year old project finally comming to fruition 
 :-)

it was my idea first ^^^

damn... 14 years already...!

not all of this was spent on liquid... obviously  ;-)

ok, you are first

hihi

well, I'm happy that a few of you are starting to come out in anticipation 
(some in private  :-)  this means my platform will have appeal for 
many of us and we will be able to start a real rebolution.

in easy drawer, i use a little this concept

*little bit

regraph uses it at about 80%  and liquidator at about 95%...

source is synchronised with draw board in real time

don't know had a lot of issues dragging thing around... but in liquid, 
this stuff doesn't even have to be coded... and its all uniform the 
same generic api for all data... which is why it pays off in the 
end... you stop trying to design the actual dependencies, and start 
working on the algorythms.

you are comming at the devcon?

i can't even if i'm french , il currently leave in frensh Caraibs

live

Darn... I will be giving a session on liquid there, but especially 
will be demoing liquidator publicly.

you'd have had the chance to get a first hands on trying out the 
interactive node editing.

there will be a streaming video for the confs, i hope

(with the chance to ask questions directly)

that would allow you to ask questions.

i think i will not wait the devcon before using liquid

don't I have been using it commercially and its currently very stable.

I meant... dont Wait.

and u will nost post a first version of your interactive node editing 
tool before devcon ?

(you can ask nicely ;-)

i'm not sure i can do that

^^^

if you're interested, yes, I am willing to share it.  I have a good 
deal of it done (I've already shown it to someone else already)

yes i am , sire

but its not yet actually able to DO anything.  I'm at the fledgling 
days of optimising the gfx engine for the graph editor.  The node 
creation, dragging and linking are done, (all graphically) and even 
already detect cycles, so you can't connect nodes in such a way as 
to get a dependency cycle  :-)