World: r3wp

open source projects which are not funded suffer the same fate, btw.

(many of them, that is)

yes for many, but something like this is very very interesting

that is if it works :)

well everybody will be happy to know that I am releasing it under 
MIT license.

I am hoping that this will help adoptance a bit.

I am quite quiet these days about my stuff because I am working a 
lot on the release itself.  making docs, example codes, completely 
rebuilt the steel site, etc.

but as usual, work comes first, so There is only so many hours to 
put on this stuff... in my free time.

I wanted to release liquid last week... I could have, but would not 
have been able to properly support the release itself and answer 
even basic questions.  so I am preparing more help around it, allowing 
people to get the basics by themselves... (I hope)

Hi Maxim, 
are there liquid pumps?

As an example, imagine a layout with 2 input values, and 2 outputvalues, 
which depend on both inputs, e.g. input 2 numbers, and get  product 
and sum.

Now if I change the value of 1 input field, the new value would flow 
to both output fields. As far as I understood liquid so far, I now 
need another way to notify those 2 output fields, that there are 
new values waiting. And they have to actively get the new data.

Now add a pump, which pumps the data into the system, so that dependent 
!plugs automatically are recalculated.

Is this possible now? What do you think about adding this?

all you do is tell the dependent plugs that they are "Stainless" 
 (setting stainless?: true) and a plug is never left dirty.

this is all done already.

the nice thing is that in the same network, you can have a mix and 
match, since they all are lazy internally,  but the stainless are 
told to request their data right after being set dirty.

Ah, thanks, I should've known you'd already thought about that ...

How do you make the buttons fro your UI, the Aqua look?

Reichart, that would be my fault. It's done with DRAW. I developed 
a prototype, which was then refined by Maxim for practical use. http://www.hmkdesign.dk/rebol/cool/cool-widgets.r

http://www.hmkdesign.dk/rebol/cool/coolwidgets.png

Where did you get the formula for teh Help and close button: http://www.pointillistic.com/open-REBOL/moa/steel/images/regraph/regraph-0-1-4-main.png

that is the look of GLayout's style.  basically, its the button color, 
any color works.

Maxim: can you post the download url''s I wanted to play around possibly 
to see if I can understand what you are getting at.

new release of liquid: 

to download the file:          http://www.rebol.org/cgi-bin/cgiwrap/rebol/download-a-script.r?script-name=liquid.r

for some docs on liquid:   http://www.pointillistic.com/open-REBOL/moa/steel/liquid/index.html

micheal, the !plug quickstart is a good way to begin understanding 
the basics:


http://www.pointillistic.com/open-REBOL/moa/steel/liquid/plug/plug-quickstart.html

the version 0.6 ref document is here: 


http://www.pointillistic.com/open-REBOL/moa/steel/liquid/plug/plug-reference.html

>> do http://www.rebol.org/cgi-bin/cgiwrap/rebol/download-a-script.r?script-name=liquid.r
connecting to: www.rebol.org
Script: "LIQUID - core dataflow programming engine." (4-Feb-2007)
** Script Error: slim has no value
** Near: slim/register [

this is not a bug... liquid is a slim module.  you must have slim 
loaded first

the quickstart explains how ... its VERY easy.  ;-)

Why can't you just do this:
do %slim.r
do %liquid.r
?

Surely that would be more rebolish ?

But the launching of programs is something to be thought about deeply...........

these are managed modules.

slim is not about loading code.  'do does that.

slim is about managing the internals ... both technically and politically. 
 its about providing a unique and consistent code model to allow 
tools to wrap around this.

we could probably wrap the code in the way you specify. but then, 
slim allows you put your code anywhere...

so the above would not work.

so while people have been waiting 5 years for the promise of modules, 
I have been using them.  and when Carl released his spec... I did 
85% of it in exactly the way he suggests.  even in some details like 
'exposing code.

so I don't wait, yet am very "rebolish" ;-)

obviously its not perfect, obviously I can do code protection, but 
then, Im alone, people want to do their own... so they can always 
do so.

Robert tried slim and in 15 minutes adopted it.

Are you saying you can't do that ?

do what?

do %slim.r
slim/open liquid 0.6.4

oops  typed a bit too quickly...	

do %slim.r
slim/open 'liquid 0.6.4

So that's all that's needed ?

A problem with all these different module managers and include systems 
is that there is ignorance of what they actually do. When you post 
code like the above, I have no idea what it's going to do with the 
files, how they are going to be arranged on my harddisk etc., and 
what global words are going to be defined.

My old INCLUDE system and the new one I've been working on also suffer 
from this "gap of understanding".

I think the answer is a GUI option which shows in clear diagrams 
what is going on.

my library engine is fully documented for 3 years now.  a FULL reference.

No, I mean the diagrams form part of the GUI (when a "show GUI" option 
is selected).

Anton, that is the POINT of slim... you control everything !

the library is not allowed to share any information in global space.

Except you don't know how it works except by going to read the documentation 
first.

the module user exposes on demand, and even the context is unnamed, 
you assign it.... the above again misses code... man  its 2AM here 
I am sleepy.

I am saying it's better for us to integrate a clear image / animation 
of what's about to happen, and what's happening, within the user 
interface.