Well, Tapestry offers you to directly create html. You just have to put some jwcid attributes to some of the tags and Tapestry dynamically replaces tags with a jwcid with generated content. See the Tapestry docs for some more infos if interested.
So the designer can focus on designing and changing the html. The developers can focus on implementing application logic. I don't want to persuade anybody to drop cocoon and instead use Tapestry. I just wanted to describe whow things can be done in other frameworks. Anyway in some cases it might be valuable to take a look on Tapestry. If you then need the xml power of cocoon you could try to integrate it. > -----Original Message----- > From: Ilja Smoli [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 16, 2005 10:41 AM > To: [email protected] > Subject: Re: separation of roles > > > Hi > I'll join this conversation cause Im one of developers for > this project... What about coocon? Ain't it offers good > separation concerns? Question is about how developers have to > prepare environment for designers, so they can adjust look&feel etc.. > > > > "Bowe, Bastian" <[EMAIL PROTECTED]> wrote in > message > news:[EMAIL PROTECTED] > .de.astrium.corp... > > If seperation of such roles is a major concern you should > take a look > > at Tapestry (http://jakarta.apache.org/tapestry/). I don't want to > > start a flamewar! It's just my personal onpinnion that one of > > Tapestry's strengths is the speperation of HTML and logic. > > > > > -----Original Message----- > > > From: Vlad Golodov [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, February 16, 2005 10:21 AM > > > To: [email protected] > > > Subject: separation of roles > > > > > > > > > Hello All! > > > > > > we are making a project using cocoon. Our company has > developers who > > > don't know anything about design, and designers, who don't know > > > anything about cocoon. > > > > > > At the moment we have all screens written in XML, and they are > > > transformed through the XSL files. Thus, xsl files have too much > > > html code. Should the html code be removed from there somehow? > > > > > > How developers could write a system, so that designers(which > > > probably know only html) don't deal with the underlying layers? > > > > > > > > > Vlad Golodov _________________________________________________ > > > Tel. + 372 88 11 244 > > > http://www.vladgolodov.com > > > Sun Certified Java Programmer > > > MBCS (Member of British Computer Society) > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
