Or try this simple question:
How do I execute some javascript in the render phase of a component
which creates an object and then refer to that object when handling an
async event for the same component?
Please excuse me if this is documented somewhere, I cannot find it.
On 13/11/2014 7:41 AM, Paul Stanton wrote:
Hi Thiago,
Firstly thanks for the reply.
Do you think you could put aside the dissection of my question and
defence of position and just answer the question to be helpful?
I am not trying to start an idealogical conversation or criticise
anyone or any way of thinking but would love for you to show me what
the simple recommended TAPESTRY RELATED usage is.
Thanks, p.
On 12/11/2014 11:44 PM, Thiago H de Paula Figueiredo wrote:
On Wed, 12 Nov 2014 09:13:43 -0200, Paul Stanton
<pa...@mapshed.com.au> wrote:
Hi,
Hi!
so like many developers (i'm guessing) I'm not quite up to speed
with all these new javascript frameworks: requirejs, closure, etc etc
Require.js is actually used by Tapestry 5.4. I'm not sure what you
mean by Closure (the JavaScript concept or some JS framework?) nor
the etc part. If you want to learn about Require.js, read its
documentation. :)
and to be honest I really didn't see a problem with the namespace
model of the past.
It didn't work well (or at all) when, in a zone update, the response
has JavaScript to be invoked. That's only one reason.
I'm not open to learning but it seems like a paradigm far removed
from what i'm used to. it doesn't seem object oriented at all for
example.
Yes, it is object-oriented, specially because it doesn't leak
variables and functions from one piece of code to another, placing
that aside, can someone please point me (and other readers) to some
basic examples to get us started in this brave new world. the first
thing I would like to achieve is to be able to call some page or
component specific marshalling code with page/component context
parameters.
What has your question has to do with Require.js and namespaces? I
can't see, I'm sorry.
What do you mean by marshalling? Don't you know that, for JavaScript
to page or component communication in Tapestry, you're much better
off using query parameters than the context?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
