forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorsten Scherler <>
Subject Re: Locationmaps and Lenya integration
Date Thu, 26 May 2005 01:49:37 GMT
On Wed, 2005-05-25 at 19:51 -0400, Gregor J. Rothfuss wrote:
> Ross Gardler wrote:
> > I'm going to come back to this after we have submitted the Apachecon 
> > presentation. I'd like to see how Thorstens work integrates with 
> > locationmap as that is the next thing I need in Forrest. It makes using 
> > things like Daisy or Lenya far easier and may be the ideal place for 
> > view configurations like this one. I'll catch up with Thorstens recent 
> > RT's and try and bring the locationmap idea into them.
> hmm, can you explain this a bit more? i haven't followed the list very 
> closely and would appreciate a quick summary as to how this could 
> improve said integration?

I leave this part to ross because I still have to have a closer look on
locationmaps. ;-)

> forgive me my ignorance, but when i see things like
> <forrest:views xmlns:forrest=""
>      xmlns:logic="">
> <logic:filter value="dirCut" parameter="p">
>      <forrest:view format="inx" />
> </logic:filter>
> <logic:filter value="actorCut" parameter="p">
>      <forrest:view format="inx" />
> </logic:filter>
> i am wondering if forrest is moving into a direction of 'programming in 
> xml'. is this the case? 

I do not like this expression 'programming in xml' it is more (like I
stated in other threads) 'configuring components with xml'. 

This code should help *user* easily change the output of forrest. In the
end this code should be produced by tools. 

...and btw I would like to see such clear intuitive configuration and
separation in lenya and not a parameter overkilled framework that allows
user to extend the framework if they *exactly* follow the *not easy* to
understand boundaries and rules of the framework where you can do
everything you want as long it is the lenya way. 

*User* want to have a configuration file (or better (in the future) a
tool where they can create such a file) to alter the behavior of their
application. They do not want to learn cocoon/java to alter the default
behavior. You have worked on PostNuke, you should know that for
yourself, as a user you do not want to learn php. ;-)

> is there a document / discussion / wiki page 
> somewhere that explains the goals behind this?

The goal is that a normal user do not have to understand much of
programming (nor cocoon or java) but rather can configure forrest in an
easy intuitive way to customize it the way they want. The view e.g.
should be created by a webdesigner that have *no* knowledge of
programming at all.

Devs on the other hand want an easy to understand and clear defined
interface where they can plugin new components.

Search the ml for view;view helper;leather;...

...or do you *really* consider 
<logic:filter value="dirCut" parameter="p">
  <forrest:view format="inx" />
<logic:filter value="actorCut" parameter="p">
  <forrest:view format="inx" />
as programming???


> thanks,
> -gregor

"Together we stand, divided we fall!" 
Hey you (Pink Floyd)

View raw message