forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Williams" <>
Subject Re: direction of forrest
Date Mon, 16 Jul 2007 21:18:08 GMT
On 7/16/07, Thorsten Scherler <> wrote:
> On Mon, 2007-07-16 at 08:16 -0400, Tim Williams wrote:
> > With limited spare time I've been struggling to figure out where/how
> > Forrest concerns me anymore.  I thought its relevance to me is waning.
> >  I thought its relevance in general may also be waning.   I mean, I
> > realize that Forrest has much more to offer, but still, I look at
> > projects like Exhibit[2] and wonder if we're on the wrong path.
> I think I know what you mean but can you explain a wee bit more? I mean
> Exhibit is a firefox/xul application. In the end this means exchange
> cocoon for firefox as underlying framework?

Exhibit is not a firefox application (Maybe you're thinking of
Piggybank?). It's a javascript application and isn't tied to a
specific browser.  It's using standard javascript/dom/ajax that's,
nowadays, fairly cross browser specific.  Anyway, I wasn't pointing to
that as a *better* solution, just a less heavyweight solution to what
is a relatively simple problem.  They are mashing up google
spreadsheets and other source formats and providing multiple
"presentations" of them - not so different from our ultimate goal.

> The one wonderful think that cocoon still is awesome at is that you are
> not bind to ONE browser. Exhibit and similar project of the MIT are
> bound to XUL.

That's not right, they are cross-browser.  Most decent javascript
libraries out there are also cross-browser.  As I said above though, I
wasn't pointing to it as a "solution", more as a different way to
solve problem, has lighter weight, mashup opportunities.  It has
limits too, of course.

> I personally starting to like xul but is cocoon really obsolete?

As I indicate above, those are technically unbound topics, but I think
the answer to the latter is slowly becoming  - yes, for our purposes.

> > There's been a number of emails that make me question whether that's
> > true or not.  We have some interesting code in Forrest2.  We have
> > Thorsten talking[1] about using PoJo/Spring in dispatcher.  We have
> > Ross beginning to integrate some Ajax-y code.
> Actually the good things of both approach is that it will easy to
> integrate, meaning using the standalone dispatcher as presentation
> framework and forrest2 as multi-channel publisher.

Yeah, I'd like to see Forrest2 take even *more* advantage of Spring
personally.  That was the one thing I didn't care for in that
code-base - the implicit piping with unique protocols.  I'd rather we
make locationmap standard beans (e.g. inject the configuration) and
pull them into Spring as well - I can explain later.  Define the whole
thing inside Spring context and take advantage of Spring's list
inheritance, overriding capabilities, etc.  Anyway, probably too
technical, I'm just trying to get a feel for what others think the way
ahead is and if forrest2 was an interesting conversation that's going
nowhere or not.

> > We obviously discussed
> > much of this before the release but it was thought best to just put it
> > on the back-burner until after the release.
> After the release we fall in a comma (like it seems).


> > Unfortunately, after the
> > release, we seemed to focus on JIRA to answer "what's next"[3].
> We tried to brainstorm but the discussion died through general
> statements like the jira review you point out.

Exactly.  Maybe we should have this discussion and capture it as the
roadmap in JIRA to take that off the table?  There's lots of "real"
issues in JIRA right now, but none that I see that provide an
interesting story for our roadmap.

> >  Now,
> > I've got nothing against JIRA, I just think we've got bigger "issues"
> > than those currently captured in JIRA.
> The think we never really decided is which road to go.

As you point out above, the options we have aren't necessarily at
odds.  It's less about which new road to choose I reckon and more
about us making the decision that a new road is indeed in Forrest's
future.  No?

> >
> > So, I ask what's the future of forrest?  Is Forrest2 or some
> > derivative the answer?  Status Quo?
> >
> I for one tend more in forrest2 direction then status quo. IMO cocoon is
> suffering and will more in the future. Meaning projects based on it like
> forrest and lenya are suffering as well.
> I believe the future of forrest lies in "bringing back cocoon 1" and
> make it plugable. I am not sure whether exchanging cocoon for xul will
> solve anything. I do not like program in javascript, I prefer java.

That wasn't what I was suggesting,  as I said above, Exhibit isn't
XUL, but I wasn't suggesting it anyway.  Forrest2 is good enough for
me at this point.

> However the current community is IMO in deep sleep. Our code is quite
> stable which for me indicates the next release should be 1.0 with:
> - build on ivy dependency management
> - make core independent of theming engine (re-factory regarding
> skins-plugin, all code of the core regarding skinning have to go to a
> plugin)
> -- core build target
> -- core sitemaps
> - internal format based on xhtml2
> This brings us a stable branch and the next thing for me would be blueprint planning.
> I mean if we manage to write a "documentation" before we write any code
> we can split task for coding.
> Anyway ATM I am concentrating my spare time on lenya (we have a moment) but like said
> above lenya is facing in the near future the same situation regarding cocoon.
> IMO I guess future development of lenya could very much use something like forrest2.

Thanks for you thoughts.


View raw message