World: r3wp

just one one... pipe servers ARE NOT built to handle multiple values... 
its the opposite.  handling multiple values is done through dependencies 
(linked nodes) all going into one node.

*one note*

pipe servers hanlde multiple view of a single value, coordonating 
everyone so they collaborate in how they share that value.

also note, scanning the subordinates and observers is an extremely 
advanced maneuver... cause the way data is represented in subordinates, 
has different possibilities, for example, you may have word labels 
in the block.  in liquid v2, there will also be possibility to store 
data directly within the subordinates block.  there might, eventually, 
be other uses for the subordinates  I have not yet thought of.

Is there a movie that shows how liquid works?

:)

ie. liquid refreshment

pekr:  yes using liquid interactively is one of its mandates.  the 
liquid editor, will be used in this way, changes will be viewable 
in real-time, so the first set of nodes that are going to be integreated 
are globs, which allows a graphic package to be built within a day.

movies, right now would be really boring, since all that is being 
done, is editing text... but with liquid-vid, and the interactive 
editoe, this will change.

I LIKE the name.

I would abbreviate liquid-vid to just liqvid :-)

Re: Pipe Servers.  I know I'm going to need one, I was just trying 
to combine agregating the font values and serving them.  I need two 
separate nodes for that...

exactly.

all the entry points can be pipes, which are combined into a singular 
node.

I now have the object constructor working well.  I just need to figure 
out the server.  'Tis rather confusing...

IT'S ALIVE!!!!

No pipe server necisarry...

I can just see you with the lightning bolt crackling in the bg and 
a wild look on your face...  hahahaha

Liquid rocks!  I'm getting very close to my goal here and when I 
run into a bug 90% of the time it's because I didn't plug everything 
together properly.  It's pretty sweet.

happy you are "getting" it   :-) it can be a wee bit unsettling when 
the system starts to be knowledgeable about itself.

That's exactly what I want the system to do. =D

my most common bug, is to forget to put something stainless or to 
ask for a value... hehe

I turn round and round and wonder why nothing is being printed on 
the console...  then after a very long time... hehe I realised I 
never asked it to perform its  task... hahaha

The last one I ran across took me 15+ minutes to find a reference 
to face in a plug that never got set.  I couldn't figure out why 
it did nothing...

Sounds like a special tracing/debugging functionality should be included.

it already is  :-)  its run-time switcheable... and its how I always 
find my stuff.  its even indented

if you try out the little blood.r app on rebol.org you'll see how 
extensive liquid's tracing is, thanks to slim's vprint engine.  :-)

plugs also have the generic stats method, which gives A LOT of info 
about the current state of the node.  links, state, type, serial 
numbers, etc.

rmembr that liquid is the culmination of  5, yess FIVE years of R&D 
 ;-)

so for someone who does plain boring data entry forms .. what can 
it do for me?

screen validation?  calculate results based upon screen entry?

did you try the blood.r on rebol.org?

there are 12 interconnected fields, which all react together.  impossible 
to break by using the gui.

We already have some variations where the buttons get deactivated 
even more precisely.

its a simple download and run... all libs are d/l for you in same 
dir... can't be easier to try out.

not yet ... been busy with my pdf stuff.

waiting for everyone to report their bugs first so that you can fix 
them :)

that's the point of liquid... un breakable.. once it works... it 
just does

the entire gui is reflective.

how much code is it?

in this example... way to much, cause we are basically including 
very basic nodes and a core gui api, but if you remove that, in fact 
there isn't that much left.

with the external libs I am building (actually working on them daily) 
code use will be very small.  since the most complicated part of 
the engine will be wrapped within liquid-vid, and you will have a 
lot of example and reusable liquid classes to start off with.

I mean, we have to use liquified versions of things like min/max/sum/sub/append 
 funcs... there is no going around that.  but its like defining new 
functions... which are just as reusable.

ok, cool . just tried it out

try putting extreme values in ANY field, even non numerical, decimal, 
etc.

is everything MIT now?  Is the GPL gone?

all MIT

what really pushed me was that I realized that with gpl, you can 
even get kicked out of your own code.

its like a sticky fly trap.

beurk

notice how it even updates labels, colors, and buttons become inactive 
when you go out of bounds.