> -----Original Message-----
> From: Ingo Hohmann [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 17, 2003 3:01 PM
> To: [EMAIL PROTECTED]
> Subject: [REBOL] Re: Liquid Project : connection with datas...
> 
> 
> 
> Hi Gregg, and all,
> 
> Gregg Irwin wrote:
> > Hi Robert,
> > 
>  From WordNet (r) 2.0 [wn]:
> 
>    valve
>         n 1: a structure in a hollow organ (like the heart) 
> with a flap
>              to insure one-way flow of fluid through it
>         2: device in a brass wind instrument for varying the length of
>            the air column to alter the pitch of a tone
>         3: control consisting of a mechanical device for controlling
>            the flow of a fluid

LOL,

yep, the third is Exactly the meaning  

DAMN, I should have called it fluid ... not liquid...  now I know why everyone is 
mislead(strangely that was almost the case).


thanks for the support Ingo ;-)


No, really, liquid stems its name from the term "data flow"... I wanted to make it 
have its own language so that once assimilated, when following a discussion or 
especially writting about the relationship a liquid object (or valve) has with the 
rest of the code, it is clear.

when you say "the valve is connected to your object" there is absolutely no ambiguity. 
 One is live, the other isn't.

It also stems from the fact that in previous versions of liquid.r there was a base 
object called container.  

consider the next phrase:

 "filling liquid into a container through a pipe", this makes a lot of sense and 
deftly resumes exactly what is happening.   

you can thus continue by "if a valve is open, it spills liquid" 

This being the actual event (or action), depending on what is connected to the valve, 
will either splash data to the user or silently put it in the container (an object's 
attribute?), for later reference.

I'm sorry this means the methods and attributes have their own "world" but if you 
think of it, many other programming things have borrowed names from real world 
items... 

By looking at the liquid-vid tutorials, 
http://www.rebol.it/~steel/liquid-vid/tutorials.html

Most things about liquid are explained in enough detail, I hope.  I have not received 
one comment on them.  either no one went, or those that did, found it clear enough for 
their understanding (I hope its the later ;-).

I understand Robert and Gregg, and I sympathise, but sooo much tought went into it 
(including other things not yet available) that I feel, its too late.

Once you use it a little, you'll see that there isn't alot of words to actually learn 
and even then, they really are obvious.  On top of that, within a liquid-vid block, 
pretty much only the connect and attach words are needed.

I hope that the naming won't keep people from trying it out and understanding the 
concept.

I'm hard at word every other night, hacking away at code that eventually, I hope, 
you'll all benefit from, much like vanilla, rugby, and make-doc-pro and all the others 
cool tools.  I can't wait for all my tools to be v1.0 but there is soooo much to do.

Right now, I am working on the v1.0 of open-library which allows of us to package our 
code as shared modules.  Much like python has a standard code sharing system.

Soooooo stay tuned, it won't be long before I submit it for all of us to tear at, 
bitch about, improve, and eventually adopt.



have fun!


-MAx

-------------
Steel project coordinator
http://www.rebol.it/~steel
------------- 

-- 
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.

Reply via email to