cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject [RT] Flow as a block
Date Thu, 13 Mar 2003 08:36:10 GMT
The flow stuff is an "optional" component, which means I can use it
or not. Cocoon started as a web publishing framework and as flow is
not directly a core component for web publishing but for web
applications, I really would like to see flow as an own block
that I can either install or not.
Don't get me wrong, I like flow and I see the use of it, but flow
is an optional component in the same sense that for example the
portal framework is an optional component.

Unfortunately, separating out the flow stuff into an own block is
not that easy, I guess, as the main sitemap engine had to be extended
for it.

I'm thinking since last year about making the sitemap syntax pluggable,
so the basic idea is to install an own block that adds more syntax and
features to the sitemap. With that implemented, it would be easy
to make flow an own block.
I know that making the sitemap pluggable has some dangers, so this
is only a thought.

Anyway, regardless how it is solved, I would like to have the flow
separated into a block.

What do you think?

Carsten 

Carsten Ziegeler 
Open Source Group, S&N AG


Mime
View raw message