World: r3wp

*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  :-)

I will post a little note on this list, when I am ready to give out 
a first demo of liquidator maybe next week.

ok, i'll be there

the layers things is very powerfull, but is giving me a few design 
headaches.

do you think it's possible to use liquid to emulate the rebol engine

cause I'm basically hacking away at a working version and breaking 
it completely, hoping to patch it up and get it working with more 
features and cleaned up afterwards.

to do a rebol debugger

i see

the issue with dataflow is that its very bad at iteration.  so doing 
actual code loops is touchy.

for debugging purpose it's not so critic

the debugging part is trivial, but the code "execution" part is harder.

what we can do is manage code and edit the code on the fly... which 
is what I will be doing as my first liquidator module.

hmm...

liquidator's first module I wish to build is  a REBOL IDE.  so that 
means...  a decent editor, code compositing, concurrent souce version 
control... right on the source without CVS (no need), notes, unit 
testing, etc... and debugging, when possible.

debugging is hard to do in rebol without some hooks.

so this means that the debugging part will most probably manual or 
tightly coupled to liquid node use (for now)

except if the source is parser in another one thing

*is parsed

by manual I mean, that you will decide what to debug BEFORE running 
code as opposed to after.

but that means you are running the code within a liquid node...

I am talking about a real debugger, where you actually DO the code 
hands off.

i see

with liquid management of code, we can easily alter whole script 
at the flick of a switch, to add thousands of lines to allow debugging.

but for some functions this can be fatal, so its a tricky game... 
which needs a lot of thought... so I will be going at it one step 
at a time.

first give a solid dev platform, then add some debugging help.  unit 
testing alone is trivial to implement in liquid, so that's a very 
good path for a first pass.

i'm impatient to see that

so much, that i could do my own try on my side

^^

hum I think your char set is addding chars that I can't read  :-( 
  I see many ^^^ in the stuff you post.