T5: Did someone mention flow control?

[Ron Piterman <rp...@gmx.net>]

After working with tapestry for quite a while, and since much new is on
the air I wanted to just share a thought: Flow control.

While tapestry supplies excellent solutions of two basic problems of
web-dev: form and state, it seems to me we lack something on the part of
declarative flow control.

I would be most happy to make a suggestion, but unfortunately, out of
ignorance, I can't -

The complementary part would be security. So with the complete rewrite
of the framework, I would find it very nice, (and a knock-out...) if
also completely new features in these two areas were added.

Cheers,
Ron



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

Re: T5: Did someone mention flow control?

[Jesse Kuhnert <jk...@gmail.com>]

I had thought that Mind Bridge had something brewing in this area as well.... ?

On 12/21/06, Rahul Akolkar <ra...@gmail.com> wrote:
> On 12/21/06, Ron Piterman <rp...@gmx.net> wrote:
> > After working with tapestry for quite a while, and since much new is on
> > the air I wanted to just share a thought: Flow control.
> >
> > While tapestry supplies excellent solutions of two basic problems of
> > web-dev: form and state, it seems to me we lack something on the part of
> > declarative flow control.
> >
> <snip/>
>
> We now have State Chart XML from the W3C (currently a WD) and an
> implementation in Commons SCXML [1]. It is something that makes good
> sense to look at when it comes to declarative flow control; or any
> state machine notation for that matter.
>
> The Jakarta Commons implementation is meant to be environment agnostic
> -- it allows for pluggable expression languages [2] and adding domain
> specific XML vocabularies in developer-defined namespaces via the
> 'executable content' [3] within a SCXML document.
>
> The 'who is using it' section at the bottom of the home page
> illustrates its already being used in this space, for Shale dialogs.
>
> -Rahul
>
> [1] http://jakarta.apache.org/commons/scxml/
> [2] http://jakarta.apache.org/commons/scxml/guide/contexts-evaluators.html
> [3] http://jakarta.apache.org/commons/scxml/guide/custom-actions.html
>
>
> > I would be most happy to make a suggestion, but unfortunately, out of
> > ignorance, I can't -
> >
> > The complementary part would be security. So with the complete rewrite
> > of the framework, I would find it very nice, (and a knock-out...) if
> > also completely new features in these two areas were added.
> >
> > Cheers,
> > Ron
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


-- 
Jesse Kuhnert
Tapestry/Dojo team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

Re: T5: Did someone mention flow control?

[Rahul Akolkar <ra...@gmail.com>]

On 12/21/06, Ron Piterman <rp...@gmx.net> wrote:
> After working with tapestry for quite a while, and since much new is on
> the air I wanted to just share a thought: Flow control.
>
> While tapestry supplies excellent solutions of two basic problems of
> web-dev: form and state, it seems to me we lack something on the part of
> declarative flow control.
>
<snip/>

We now have State Chart XML from the W3C (currently a WD) and an
implementation in Commons SCXML [1]. It is something that makes good
sense to look at when it comes to declarative flow control; or any
state machine notation for that matter.

The Jakarta Commons implementation is meant to be environment agnostic
-- it allows for pluggable expression languages [2] and adding domain
specific XML vocabularies in developer-defined namespaces via the
'executable content' [3] within a SCXML document.

The 'who is using it' section at the bottom of the home page
illustrates its already being used in this space, for Shale dialogs.

-Rahul

[1] http://jakarta.apache.org/commons/scxml/
[2] http://jakarta.apache.org/commons/scxml/guide/contexts-evaluators.html
[3] http://jakarta.apache.org/commons/scxml/guide/custom-actions.html


> I would be most happy to make a suggestion, but unfortunately, out of
> ignorance, I can't -
>
> The complementary part would be security. So with the complete rewrite
> of the framework, I would find it very nice, (and a knock-out...) if
> also completely new features in these two areas were added.
>
> Cheers,
> Ron
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org