Vadim Gritsenko wrote:
Marc Portier wrote:
snip/
There's already a parameters property in the cocoon object.
We can have :
function whatever() {
doSomething(cocoon.parameters.x, cocoon.parameters.y);
}
And nobody still answered the question: why passing of parameters into
the function
Marc Portier wrote:
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
snip /
If we match by variable name rather than by position, it would work
anyway.
... but I have the feeling I'm missing a big point here.
Yeah : the point is that parameters are passed as Object[] to a JS
function. The
Sylvain Wallez wrote:
Marc Portier wrote:
Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
snip /
If we match by variable name rather than by position, it would work
anyway.
... but I have the feeling I'm missing a big point here.
Yeah : the point is that parameters are passed as
Marc Portier wrote:
snip/
There's already a parameters property in the cocoon object.
We can have :
function whatever() {
doSomething(cocoon.parameters.x, cocoon.parameters.y);
}
And nobody still answered the question: why passing of parameters into
the function
function whatever(x, y, z)
On Wednesday, Aug 20, 2003, at 11:27 Europe/Rome, Sylvain Wallez wrote:
Stefano Mazzocchi wrote:
On Friday, Aug 15, 2003, at 23:49 Europe/Rome, Sylvain Wallez wrote:
snip/
And this really demonstrates how dangerous can be this translation
to positional parameter ;-)
why don't we fix this,
Stefano Mazzocchi wrote:
On Friday, Aug 15, 2003, at 23:49 Europe/Rome, Sylvain Wallez wrote:
snip/
And this really demonstrates how dangerous can be this translation to
positional parameter ;-)
why don't we fix this, then?
Well, positional parameters have been there since day one in
On Friday, Aug 15, 2003, at 23:49 Europe/Rome, Sylvain Wallez wrote:
Andreas Hartmann wrote:
Sylvain Wallez wrote:
[...]
map:call function=foo
map:parameter name=bar value=baz/
/map:call
function foo(bar) {
...
}
This syntax turns named parameters in the sitemap into positional
Hi all,
I guess the title says about all. ;-)
I want to dynamically load a Woody form definition, its name being based
on the URI invoking the flow function. What's the easiest way to do
this? I saw some very similar questions pass by, but I fail to find out
whether this is already
Steven Noels wrote:
Hi all,
I guess the title says about all. ;-)
I want to dynamically load a Woody form definition, its name being
based on the URI invoking the flow function. What's the easiest way to
do this? I saw some very similar questions pass by, but I fail to find
out whether this
Sylvain Wallez wrote:
var x = cocoon.parameters[baz];
Ooops. Should be var x = cocoon.parameters[bar]; of course.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon,
Sylvain Wallez wrote:
map:call function=foo
map:parameter name=bar value=baz/
/map:call
and
function foo() {
var x = cocoon.parameters[baz];
}
Easy, no ?
Ha. ;-)
Added to the Wiki. :-)
/Steven
--
Steven Noelshttp://outerthought.org/
Outerthought - Open Source,
Sylvain Wallez wrote:
map:call function=foo
map:parameter name=bar value=baz/
/map:call
and
function foo() {
var x = cocoon.parameters[baz];
}
It's even easier:
map:call function=foo
map:parameter name=bar value=baz/
/map:call
function foo(bar) {
...
}
Andreas
Andreas Hartmann wrote:
Sylvain Wallez wrote:
map:call function=foo
map:parameter name=bar value=baz/
/map:call
and
function foo() {
var x = cocoon.parameters[baz];
}
It's even easier:
map:call function=foo
map:parameter name=bar value=baz/
/map:call
function foo(bar) {
...
}
This
13 matches
Mail list logo
