On Fri, 2005-04-22 at 11:09 +0100, Ross Gardler wrote: > Thorsten Scherler wrote: > > On Thu, 2005-04-21 at 21:59 -0400, Gregor J. Rothfuss wrote: > > ... > >>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.
:) I notice that you *really* understand what I am trying to do. ;-) The tool (for views) you are referring to has the code name "corium". ;-) Actually in old mails I referred to corium as what now is the view/viewHelper plugin combination. Freely create a html-skeleton and imitate e.g. css-zen-garden skeleton. Anyway, corium should become a tool to create/manipulate views via a web-interface. In my head there is the idea to create a flow that will get the default.fv or the page specific view and then manipulate this view via cforms and save it again. It should be very easy because forrest is working copyless (praise the inventor of it). ;-) Before we actually can start the work on it we need to finish the view concept after the 0.7 release. The mayor missing part are the business helper. I am still thinking of an abstract way to allow any business service to connect. To consulate the forrest business service is not a problem but it has to go beyond that. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
