You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Rolf Kulemann <ma...@rolf-kulemann.com> on 2004/01/13 22:01:32 UTC
Re: Flow or actions?
On Tue, 2004-01-13 at 21:46, H.vanderLinden@MI.unimaas.nl wrote:
> Hi,
>
> >From numerous answers to questions I get the impression that "flow is the
> way to go", but on the other hand, there are also actions. I have an idea
> how they work, but I cannot figure out whether I should use only flow or
> only actions or a mix of both.
> Can someone explain when to use the one and when to use the other? Or are
> you planning on replacing actions with flow?
Good question. I have the same problem (I'm quite new to cocoon).
Another question is, which one - flow or action - is better to debug?
AFAIK people like flow, because you do not need to recompile (anything)
when updating flow script.
--
Regards,
Rolf Kulemann
Re: Flow or actions?
Posted by Leszek Gawron <ou...@wlkp.org>.
Just some my comments:
On Wed, Jan 14, 2004 at 02:26:07AM +0100, Joerg Heinicke wrote:
> 1. Both actions and flow scripts were designed for the controller part.
Actions can be also used for business logic.
> 2. Actions were often misused, so a new concept was searched for.
> 3. Interpreting (flow script) vs. compiling (actions).
It is easier to develop with flow as you have to restart the container each
time you change your actions code.
There is a compromise: use XSP actions.
> 4. Procedural style of the flow scripts is nearer to flow control.
> 5. Support of continuations with flow scripts.
> 6. Less delivered code for flow scripts while there are many actions
> available.
Not really as it is not elegant to include buisness logic in flowscript. One
should write appropriate classes. They should be avalon components as in new
FOM you cannot issue actions from flow (I think this would be very nice if SoC
was maintained)
> 7. Better separating of concerns for flow scripts.
> 8. Therefore less sitemap readibility (the sitemap flow is not that
> obvious, because parts of the logic is in the flow script).
For me sitemap is much MORE readable. A sitemap is not a good place for coding
a complicated app. If you use flow sitemap just contains view rendering
definitions and the control is in one place - the flow.
ouzo
--
__
| / \ | Leszek Gawron // \\
\_\\ //_/ ouzo@wlkp.org _\\()//_
.'/()\'. Phone: +48(501)720812 / // \\ \
\\ // recursive: adj; see recursive | \__/ |
Re: Flow or actions?
Posted by Joerg Heinicke <jo...@gmx.de>.
On 13.01.2004 22:01, Rolf Kulemann wrote:
> On Tue, 2004-01-13 at 21:46, H.vanderLinden@MI.unimaas.nl wrote:
>
>>Hi,
>>
>>>>From numerous answers to questions I get the impression that "flow is the
>>way to go", but on the other hand, there are also actions. I have an idea
>>how they work, but I cannot figure out whether I should use only flow or
>>only actions or a mix of both.
>>Can someone explain when to use the one and when to use the other? Or are
>>you planning on replacing actions with flow?
>
>
> Good question. I have the same problem (I'm quite new to cocoon).
> Another question is, which one - flow or action - is better to debug?
> AFAIK people like flow, because you do not need to recompile (anything)
> when updating flow script.
I don't know if I get all arguments but at least some:
1. Both actions and flow scripts were designed for the controller part.
2. Actions were often misused, so a new concept was searched for.
3. Interpreting (flow script) vs. compiling (actions).
4. Procedural style of the flow scripts is nearer to flow control.
5. Support of continuations with flow scripts.
6. Less delivered code for flow scripts while there are many actions
available.
7. Better separating of concerns for flow scripts.
8. Therefore less sitemap readibility (the sitemap flow is not that
obvious, because parts of the logic is in the flow script).
Joerg
Re: Flow or actions?
Posted by Tony Collen <co...@umn.edu>.
Andreas Hartmann wrote:
> Rolf Kulemann wrote:
>
> [...]
>
>> AFAIK people like flow, because you do not need to recompile (anything)
>> when updating flow script.
>
>
> But on the other hand (AFAIK) there's no IDE support
> for auto completion etc. in the javascript. This is a
> big drawback. Any ideas how to improve this?
YES! There was a mail message from someone as S&N asking for
suggestions for future releases of sunBow. If you dig into the archives
you should easily find out the address to email the suggestion to.
Flowscript autocomplete would be very nice. :)
>
> -- Andreas
>
Tony
Re: Flow or actions?
Posted by Stefano Mazzocchi <st...@apache.org>.
On 14 Jan 2004, at 14:14, Andreas Hartmann wrote:
> Rolf Kulemann wrote:
>
> [...]
>
>> AFAIK people like flow, because you do not need to recompile
>> (anything)
>> when updating flow script.
>
> But on the other hand (AFAIK) there's no IDE support
> for auto completion etc. in the javascript. This is a
> big drawback. Any ideas how to improve this?
Yes, write everything you can in java and use Chris' wonderful
compilingclassloader.
That gives you:
1) the SoC of sitemap/flow
2) the power of continuations
3) the execution speed of java
4) the IDE help for your complicated code
5) the try/modify/retry rountrip speed of scripting
I really find it hard to imagine a more powerful environment to write
my web applications with and you flow should, in theory remain a bunch
of variable declarations, objects instantations, conditional constructs
and cocoon.* calls.... that don't really need that much code completion
anyway.
Of course, if someone wrote a flowscript editor for eclipse, I would
totally use it ;-)
--
Stefano.
Re: Flow or actions?
Posted by Andreas Hartmann <an...@apache.org>.
Rolf Kulemann wrote:
[...]
> AFAIK people like flow, because you do not need to recompile (anything)
> when updating flow script.
But on the other hand (AFAIK) there's no IDE support
for auto completion etc. in the javascript. This is a
big drawback. Any ideas how to improve this?
-- Andreas