Thanks, for the quick reply -
I actually read your article earlier on thanks.
Hmm, now lets see if I am getting this right.
When I write somthing in the RJS file the page object takes my DLD and
browser which then does the rendering it has been asked for.
I hope I got that bit right?
it to get me a value of a DOM back, then I ask by self why this request
The only logical explination to me is that asking the browser and
telling the browser are 2 completely different things.
handle all the "tell stuff" - but it can't handle the "ask stuff" i.e.
that engine is probably missing.
Could it be that the underlying problem is that the messaging
(responder, initiator sequence) is entirely differnt depending on what
is being done (asking or telling).
access to all the state of the browser. There isn't any messaging
either, just code generation.
There's some clever stuff going on with RJS, but that's mostly to make
things flow nicely, so that you can write
page[:foo].hide or page[:foo].show
rather than something like
hideElement('foo') or callElementFunction('foo', 'hide')
The trick here is that page[:foo] is not the dom element with id foo.
It's a magic proxy object that knows that when you call hide on it it
should generate $('foo').hide
post back a result, but obviously incurs a server round-trip and would
be completely inappropriate for this (not to mention the fact that
that request would be handled by another mongrel etc...)