You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Brian M Dube <bd...@apache.org> on 2009/11/04 06:31:39 UTC
Re: [Important] Status and future direction
On Sat, Oct 24, 2009 at 10:37:48AM +1100, David Crossley wrote:
> Rather than try to find one specific direction at this stage, or
> creating new wish lists, we need to find a definite way forward.
> Let solutions evolve.
>
> Here is one proposal.
>
> *) Current trunk continues as-is, based on Cocoon-2.1
>
> *) Create an SVN area for each group who want to try
> to develop something new. A completely empty space for
> each group of people to start from scratch.
One could say we already have that space in the whiteboard, but I've
never thought of it this way. It can't hurt to get some (more)
experiments going. Surely some ideas would show up in experiments
which prove useful in current Forrest, but it also doesn't hurt if
that's not the case.
> *) Assign each a simple code name (so as not to descend
> into naming wars or set false impressions about what will
> be next), e.g. ForA, ForB, ForC.
Yes, good idea. No need to get hung up on names at this stage.
I've joined the thread late, so now I'm no longer sure where the rest
of my comments should go. I'll just continue here.
I fall into the same group as several others in the thread. And that
is that my current needs have shifted from Forrest to something very
Forrest-like. Right now I need a full web application, not just
dynamic mode Forrest. But there is a need for Forrest's transformation
capabilities as part of the system. Making that all work together
should leave an interesting use case scenario to document, as well as
get me back up to speed.
Brian
Re: [Important] Status and future direction
Posted by Brian M Dube <bd...@apache.org>.
On Wed, Nov 11, 2009 at 04:29:34PM +1100, David Crossley wrote:
> Brian M Dube wrote:
> >
> > I fall into the same group as several others in the thread. And that
> > is that my current needs have shifted from Forrest to something very
> > Forrest-like. Right now I need a full web application, not just
> > dynamic mode Forrest.
>
> Would you please explain a little more. You need something more
> than 'forrest war' and putting that behind a full Tomcat/Jetty/etc. ?
That was way too hurried. Reading again what I wrote, I can see why it
didn't make sense. I was trying to say too many things at once.
The details left out of the first part: when a use case for Forrest
comes up, it's easier for me to hack something together and just get
it done than it is to get something set up in Forrest. I'm out of
practice, yes, but I get stuck thinking about a lighter, more focused
core instead of working through the use case. The core of Forrest is
extremely light; I mean the Cocoon base here. I hope to work on some
concepts in the proposed experimental space.
All I meant in the second part is that the needs of my current project
fall beyond the scope of Forrest, even in dynamic mode.
Brian
Re: [Important] Status and future direction
Posted by David Crossley <cr...@apache.org>.
Brian M Dube wrote:
>
> I fall into the same group as several others in the thread. And that
> is that my current needs have shifted from Forrest to something very
> Forrest-like. Right now I need a full web application, not just
> dynamic mode Forrest.
Would you please explain a little more. You need something more
than 'forrest war' and putting that behind a full Tomcat/Jetty/etc. ?
-David
> But there is a need for Forrest's transformation
> capabilities as part of the system. Making that all work together
> should leave an interesting use case scenario to document, as well as
> get me back up to speed.
>
> Brian