cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <reinh...@apache.org>
Subject Re: svn commit: r189955 - in /cocoon: blocks/scratchpad/trunk/java/org/apache/cocoon/acting/ blocks/scratchpad/trunk/samples/ blocks/scratchpad/trunk/samples/flow-action/ trunk/src/java/org/apache/cocoon/components/treeprocessor/sitemap/
Date Fri, 10 Jun 2005 14:11:44 GMT
Carsten Ziegeler wrote:
> Leszek Gawron wrote:
> 
>>Why do we add it at all? Some time ago we did not require flowscript to 
>>sendPage so people used it for actions. Now we introduce a hackish 
>>FlowAction to do what we've banned ourselves.
>>
>>Or am I wrong?
>>
> 
> Don't know. Currently a sendPage is required in flow if you use the
> map:call function, so you can't use it.
> Actually I want to use flow script for prototyping different things,
> and not just only flow with continuations. The action is only a
> prototype to see what is possible and what is not. As long as we
> provide a clean way to get the interpreter we can remove the action.
> But the action is a proof that accessing the interpreter is
> currently not possible. So we should imho fix that.

yes we need this, especially to make inter block communiction possible:

var x = cocoon.blocks.blockA.myFunc();

> Using a script language enables faster prototyping!

Have you converted to a Javascript fan ;-)
(With the reloading classloader and Eclipse I'm more than satisfied with a usual 
action and Java ;-)

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------

Mime
View raw message