World: r3wp

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.

so just don't do a copy/deep!

whenever one creates a change, that change is performed on the original 
data set, and everyone is made aware of the new data.

cause one data might be a string, another an issue, one a word, and 
still one a tag.

but they all share the same string information.

you could have a decimal range, and have it expressed in other formats, 
like colors, or sliders, progress bars... but they still all reflect 
the same original data.

change the page number in the field, the scroll bar updates by itself. 
 and vice versa.

one list might be filtered by gender, another by age, but add a new 
member to the list, and both will reflect the change... however it 
happened.

the advantage, is that there is no "global" understanding of what 
the data is being used for... each part of an application handles 
its own use of some data and really isn't aware of the rest of the 
application, and doesn't care.

doesn't have to.

vid

yes

normally you have to know that whenever the list changes, you have 
a slew of functions to call, labels to update, what if the cursor 
changes, due to some insertion, deletion, what if the current selection 
is deleted... all examples which have to be handled globally... and 
the more the application grows, the hairier it becomes.

that will be my next personnal project..  I promise.

its easy to do... but right now I am working actually.

so it's not that easy then !

liquid is not about less code... its about unbreakable and long-term 
feature creep indiference.

its not easy, because we have to mix three paradigms into one application.

and dataflow is a management layer, so patching a flaky event engine 
like view's has to be done properly.

really hard, I did blood.r which has 16 interconnected fields, in 
an evening.

most of the time was spent with non liquid related things... like 
vid.

hum... I seem to be getting the reichart syndrome... there is a *NOT* 
missing before "really hard".

which is what I was saying, it's not easy.

easy is a vague term.

I'd rather say VIEW is the problem.  since liquid is pure.

and perfect   ;-)