Thorsten Scherler wrote:
On Thu, 2005-04-21 at 21:59 -0400, Gregor J. Rothfuss wrote:
Thorsten Scherler wrote:
A view will be configured by a config file which basically contains the
following tags (it is still evolving):
<forrest:view type="xhtml">
<forrest:css url="default.css"/>
<forrest:contract name="meta"/>
<forrest:hook name="container">
<!--the following tags are not implement yet but will give the idea ;-)-->
<forrest:contract name="deleteUser" nugget="lenya:usecase">
<lenya:usecase name="deleteUser"/>
</forrest:contract>
<!--
In forrest that will invoke a businessHelper that connects a lenya usecase
and stores the result of the usecase (in forrest terms: nugget)
in the presentation model. This part of the presentation model will be
transformed by a forrest:contract (fbit) with the same name.
-->
<forrest:contract name="feedback"/>
</forrest:hook />
</forrest:view>
The view tag's @type determines the final output format. The idea is to
configure different output formats within a forrest:views. That means a
forrest:views can contain n different "forrest:view" configurations for
n different formats.
i am not sure if i like all these config files and formats. looks a bit
like 'programming by config file' to me.
That is not programming! It is a configuration of components.
I like it very much because I want to develop components that I can
easily reuse *without* copy and paste and afterward changing 1 line of
code.
This statement is even more true if these config files are automatically
generated, which will be the case in the vast majority of use cases.
Only power users will want to change default behaviour, and even then a
tool could easily be provided to allow this to be done through form filling.
Ross
