World: r3wp

my next step for liquid (what I was working on During the devcon, 
but wasn't able to get done do to lack of sleep) was the creation 
of liquid net.

basically a connection based TCP i/o interface to any liquid network. 
 you define the ports, the protocol (on either end) and can then 
interface your Dataflow across machines  :-)  it would allow distributed 
processing without any understanding of such concepts.

obviously, the standard issues of machine redundancy will arise, 
but that is a good exercise for the later revisions of the system.

so one (actually several)  machines can be a controler and synchronise 
to others which can also locally change their states... and whatever 
they data can generate can be sent to any other machine, including 
the controlers... so you have ONE kernel to handle all aspects of 
your systems.  and its dead easy... and would interface directly 
within any other liquified systems like liquid GL, elixir, globs, 
or eventually GLASS.

want text ports, just make a liquid which spues out text on the console... 
need that logged, just plug in another node which spues out stuff 
on disk as it comes in... but you don't even have to change anything 
in your systems... and can even easily connect your logger to other 
nodes, so you can track the flow of traffic, or the end effects some 
root events are having on the outputs of the system.  sometimes its 
not obvious to see the real world relation of inputs and output... 


liquid allows you inspect all states at all points in time of you 
system's processing and compare it.

and actually generate other data from it  like diffs or comparison 
reports. :-)

you can figure out that out of 10 systems, one is actually contributing 
to most of the indirect unwanted outputs.

cause in many times when IT changes you get unwanted results out 
of its interaction with other systems.

although that is all very high level speak.  at low level its still 
pretty much the same concept.

Maxim, I don't know if this would be considered simpe, but here is 
a suggestion:
http://www.bliner.com/projectmanagement.html

Ditto: http://fileforum.betanews.com/detail/ConceptDraw_MINDMAP_Professional_for_Mac_OS_X/1118155814/2

Max, on of the best examples would be a Rebol based simple 20x20 
Excel clone. Let people use Rebol code in the cells, and handle the 
reference handling via Liquid. It should be perfect DF applicable.

If this works, I'm adding it into my app ;-)

you could use nano-sheets, no? :-)

It would probably be easy to plug liquid in to nanosheets. I'd like 
to see that too. The current evaluation order is fixed L->R-->Top->Bottom; 
with liquid you might be able to do away with that entirely, and 
let the evaluation drive things.

perfect examples  :-)  I forgot about the spreadsheets  yes, it would 
be pretty simple to wire up  :-)

where Can I find nanosheets?

jean-francois, that would be an integral part of elixir  :-)  so 
wait for it to give you such capabilities within your whole work 
environment

mario, mind maps are very cool... I would like to make an optimised 
tool for quickly creating and organising mind maps in elixir but 
I can say that I hope others will join me in adding toolsets... its 
the whole point of elixir, an open, common framework of integrated 
and live tools.  anything goes into anything, so you can do things 
like share data between, you graphics, mind map and project management... 
why not even use some of it to drive the GUI building for one of 
the panes... I mean, in the end, they are all being used for one 
goal.

robert, If I start from scratch, it will be an n dimension spreadsheet 
with a scale of infinity in each of those dimensions (thus really 
limited by RAM, disk and REBOL types).   why start it up with a limitiation 
which is actually very easy to design correctly for starters... 


especially with GLayout which would just adjust the views as they 
grow.

I think the final nanosheets code went up with the DevX article. 
If not, I have it here.

can you mail it to me?  does it depend on any particular version 
of view?

why is it not on rebol.org?

http://www.devx.com/opensource/Article/27454/0/page/1
http://www.devx.com/opensource/Article/27969

I'll mail it as well. Not on REBOL.org...just time, priorities, and 
lazyness.

ok.  can it be packaged as a library module  ;-)  I'd put it up on 
revault

(just started looking at nanosheets... must have a little fun)

hum... I'm thinking its going to be much easier to make a pico sheets 
 ;-)

I'll pipe in...I've got a modified copy of nanosheets with scroll 
bars so it could support

more cells for financials sheets for the Fire Deparment volunteers...

I've started a simple test... but will start over... the new version 
will handle as much cells as you have RAM  :-)

(or until the GC starts caving in ;-)

:)

basically going to use a HASH of liquid nodes (the nodes themselves 
being already connected) and just asking for cell values, based on 
what cells are visible within the scrollpane.

Maxim, you ever get some more of those demos worked up for liquid?

although it looks like he hasn't been on for a while

I think you can still get his attention on the maillist

and gmail chat

any results?

Max posted this to the mailing list about a month ago:

http://www.rebol.org/cgi-bin/cgiwrap/rebol/ml-display-message.r?m=rmlFGXC

Max lives in a world of his own ... and I don't know the address!

hahahahahahahahaha

Has liquid now solidified?

I've been using liquid in a variety of projects for the better part 
of 2 years now... its ubber stable, fast and quite scalable... in 
fact much better than I had anticipated, for such an un optimised 
piece of code.

So, all the critics were wrong?

what critics  heheheh

There were a number ... I can remind you if you like :)

elixir, for example,  easily allocates 10 000 nodes, creates a several 
thousand line AGG script and actually manages to rebuild the whole 
AGG dialect block faster than view can redraw it.

You should be a salesman

elixir builds a 100% native AGG GUI .   EVERYTHING is built using 
liquid, event the field (control) properties and cursor management.

does it do anything useful?