World: r3wp

grids are much easier (actually quite easy) to build with liquid, 
and in any case, its still faces... so importing a gadget is dooable, 
if rebgui doesn't depend on too much out of widget infrastructure.

skining will be dynamic (I mean you plug a color gadget and the whole 
ui interacts as you set the scheme).

btw, the reason liquid-vid is taking some time, is that the whole 
layout is built using dataflow !  :-)

I've been re-designing the wrapper around the system for a week... 
trying to find a sweetspot between flexibility and styleability.

Max, would your engine be good fit for a spreadsheet calculation 
engine? Steve Shireman wrote this nice tiny spreadsheet widget (http://www.efishantsea.com/nano-sheets.zip), 
I guess that pluging liquid inside would make a killer demo both 
for liquid and REBOL, don't you think so?

I looked at it a long time ago, but realised that its basically easier 
to start from scratch... cause if you remove the processing aspect 
of nano-sheets... there's not much left.

:-)

but once liquid-vid is released... really its going to be very easy 
to build up grids and a little equation builder.

Max, you should try to find a route to attach liquid to existing 
GUI like VID or RebGUI. By a dynamic hook or so.

Otherwise it's a all-or-nothing thing which makes it hard to bring 
liquid step-by-step into an existing app.

Overall, it still sounds like a multi-path constraint solver to me.

robert  liquid-VID  ;-)

someone could most probably use the same core system and adapt it 
to rebgui's dialect.

I myself am building it with faces directly.  so its just going to 
be a quick integration to VID, use of a few facet words and voila.

liquid v0.8.1 released:
changes in this release (from last public release)

	v0.7.2 - 8-Mar-2009/21:25:55(MOA)

  -officially deprecated and REMOVED SHARED-STATES from the whole module
		-ON-LINK() 
	
	v0.8.0 - 15-Mar-2009/00:00:00(MOA)

  -adding stream engine for propagation-style inter-node messaging.

  -STREAM() added for look-ahead messaging (ask observers to react 
  to us)

  -ON-STREAM() added to support callbacks when a stream message arrives 
  at a plug.
		
	v0.8.1 - 28-Mar-2009/00:00:00(MOA)

  -PROPAGATE?() added to valve - allows us to optimise lazyness in 
  some advanced plugs

  -LINK?() regression found and fixed... cycle?() was not being used 
  anymore!

liquid state of affairs:

-GLASS v1 is going through intense development.

-GLUE - foundation plugs,  although not yet released is getting packed 
with fully documented plugs weekly.  there is more documentation 
text than actual code in the lib!

   *currently working on highly optimised finite state machine systems. 
   (optimised in how they prevent useless processing and messaging).

also, liquid-vid project has been dropped, officialy, in favor of 
putting time on GLASS and GLOB v2 instead.

Liquid has been tested under R3 and crashes it outright.  so R3 support 
for liquid will wait until R3 is a bit more stable, unfortunately. 
 I have enough stuff to debug without having to wonder if its the 
platform that's causing the bugs in the first place.

liquid links?

http://www.rebol.org/view-script.r?script=liquid.r

Maxim - I have sent you a note on my intent to add to my piece on 
"slim Liquid Rebol" at eclectic-pencil -  I will pen that note in 
blood ...  piping can be so much more feral that ducts ; - )

Robert, there are some (old, yet still mostely accurate) docs here:

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

and specific to the plug (less accurate)

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

any question you have, just ask here and will help as much as I can. 
 I've tutored three people so far, and it seemed to be easy enough 
to grasp that within a few hours, they where semi autonomous.

remember that dataflow is not just about using a new library, its 
a paradigm change in how you develop and design an application.  
so most of the difficutly is not in the actual coding of the plugs... 
which is really easy, its understanding what, how and why they are 
doing their stuff.

write it up again so that those of us who didn't get personal tuition 
can understand it too!

it will happen. in a short while, I just had to stop working on personnal 
projects for a week or two... life has a tendency to cut into fun 
stuff... things like lawsuit threats, have a "slight" precedence 
over me hacking away at a keybord for the sheer fun of it   ;-)

which songs have you rippped off?

no, its my neighbor.

playing your guitar too late and loud at night?

actually, I buy all of my digital enternainment.  games, DVDs music, 
etc.  I mean, I (have/do/will) live off of all three mediums... so 
it would be a bit hypocritical for me not to encourage others in 
my own trades

just neighbors complaining, but its ok, I've actually managed to 
make things worse and solve the direct complaint... hahhaha

I've got a relevant question

If I maintain copies of data in different gui aspects ... if I update 
one set at one place, can I automatically update all the other copies?

go.

yep. you pipe whatever relevant data is creating the gui.

change anyone, they all stay in sync.

what about rebgui?

they can even have different data in each... as long as its a two-way 
conversion it would work.

rebgui, not a clue.

you're clueless??

exactly.  I have never had the need to look at or use rebgui, ever.

can you make some deductions

I tried downloading it once and after tortoise svc started fucking 
up and slowing down my computer, I got fed up, and uninstalled it, 
and rebgui wen't along with it ... hehe

I can tell you that its pretty easy to make it work in vid, so it 
should be pretty easy to make it work in rebgui.

afterall, it's Rebol, view and data.

all you need to do is capture the action, send a message to the relevant 
liquid. if each control has a liquid which is responsible to set 
the control, when it receives data, they will update by themselves.

how about a one page example of two text lists upddating each other 
?

in vid?

well actually, you have to understand, that technically they don't 
update each other...  they really are sharing the same data.

by "the same data" I don't mean the same rebol block... but the same 
data in the sense of individuality... they are two different views 
of the same original data set.