World: r3wp

I have spoken with Carl in the past about liquid, he REALLY likes 
the concept, he was mezmerized when I did a quick demo of it at Paris 
devcon.


But at that time, I wasn't trying to convince him because I didn't 
have enough real-world experience using it, and still had a few reserves 
about it myself.

Adding liquid to R3 is actually something Carl looks forward to, 
we chatted about it.

A lot more world experience is needed before something unknown is 
added to the GUI

The nice thing about liquid is that its an API more than anything 
and you can model it to do alot of different things, by just changing 
a few properties and implementing one or two functions.


All the nitty gritty is already taken care of and you don't have 
to play around in that unless you really want to create special and 
ultra-optimized nodes whih I very rarely need to do myself.

Especially something that is hard to understand

Remember that Carl rewrote vid as he found Gab's vid too hard to 
use

yep.

Although easy to use as a design aim contradicts his new stance that 
Rebol is not for everyone!

the trick with adding Liquid to R3 VID is to integrate liquid INTO 
VID and not the other way around.  in the VID dialect, or as a few 
function calls which just basically create a predefined node type, 
and links it up.

Graham, i try some idea on my own GUI currently

Your own GUI?

in my soon to be released application, the dataflow aspect of the 
code is less than 20% of the time spent, yet it represents at least 
80% of the actual usefull software capabilities.  


most of it was fixing View and VID themselves... the styles, the 
event mechanism and bugs, AGG bugs, enhancing http, etc.

i made some in the past, but they all died before adulthood

so genetic defects?

probably ;-)

all of these guis and none of them complete ..

an example of a very complex system which was made 100% robust is 
this:

-an image is used as a background, cropped , transformed and displayed 
within AGG

-we need to overlay an text area over the canvas, but its all AGG 
and its contained within a graphic element.

-we create a face which is a text-area, LINK it to the coordinates 
of the graphic element.

-the face is then converted to an image on the fly everytime the 
coordinates change (even rebuilding the text wrapping interactively)

-this image is added at the proper position with the AGG draw block 
as an image with coordinates.

Currenlty, i try a new way.

No VID engine, just an event handler and Gobs as agents talking with 
their environment.

focusing on the text area reveals the text-editor face
unfocusing, renders the face as described above.


but because everything is linked, the text-area face even resizes 
& moves automatically when we resize the graphic element without 
needing to unfocus it.

had I tried to build this system without Liquid... 
  -I'd probably have a very brittle textbox.
  -one that is VERY hard to improve.
  -it would lack a lot of the interactive aspects about it.

i decided to throw away any speed constraint to promote dynamic arrangement

it's slow?

i will be at first

each gob having a lot of methods and properties

each gob having a lot of methods and properties

but then, I will build agents to optimize arrangements dynamicly

so object oriented gui?

If it's slow .. just get a faster cpu

yep

or use liquid to optimise it.  ;-)

it's what i think now

steeve, I think you'd like

.. you'd like my glob engine (only R2 for now).

the opposite principle has been tested with area-tc. Cul de sac.
(i mean, having a fast engine (but huge and hard to maintain)

The guis that work are object oriented ...

It's just too hard otherwise ...

@ jocko on rebol.org there is a working version of liquid and a small 
demo of how it can be merged right into VID called blood.r

it creates relationships between MANY text fields, which become integer 
fields because of the data types of the basic liquid values.

and i don't like the need of  a phase to construct graphical objects 
from read-only specs.
All the GUI we had so far, act such.
It's an bad...

bad concept

its why I'm pushing for graphic element as a lower-level api for 
AGG right into view.

to my mind there should not be difference of design between a style 
and a face.

A face is an instantiated style (copied and just showed) , tha't 
enough.

at best it only works for very simple layouts

just copy/deep the style :-)

so where are you at now?  1% complete ?  :)

something like that, i only made tests :(

But it works fine in my brain :)

copy/deep Steeve/brain

== ERROR: stack overflow,  reason: brain too deep

if only