Need A Better Understanding of XSP Role

2004-12-20 Thread David
I've built a Cocoon site that I'm happy with and now I need to build a completely new and different site, and I'm reading about XSP to see if it could make this new site better. For example, in my first site, I used the Cocoon protocol (cocoon:/ and cocoon://) in conjunction with cinclude to inser

Re: Need A Better Understanding of XSP Role

2004-12-20 Thread Tony Collen
David wrote: I've built a Cocoon site that I'm happy with and now I need to build a completely new and different site, and I'm reading about XSP to see if it could make this new site better. For example, in my first site, I used the Cocoon protocol (cocoon:/ and cocoon://) in conjunction with cinc

RE: Need A Better Understanding of XSP Role

2004-12-20 Thread David
[mailto:[EMAIL PROTECTED] Sent: Monday, December 20, 2004 10:07 PM To: [EMAIL PROTECTED] Subject: Re: Need A Better Understanding of XSP Role David wrote: > I've built a Cocoon site that I'm happy with and now I need to build a > completely new and different site, and I'm readin

Re: Need A Better Understanding of XSP Role

2004-12-20 Thread Tony Collen
David wrote: Thanks, Tony for the helpful response. My applications involve very little if any user input via forms, rather they are more about document publishing with flexible templates -- would the new Flowscript + Cforms approach still apply to me? Hmm, probably not so much of CForms, but tha

Re: Need A Better Understanding of XSP Role

2004-12-20 Thread Bertrand Delacretaz
Hi David, Conversely in my new site I want a more "JSP" kind of architecture in that non-programmers will need to do some page creation and I want to give them some 'tags' they can use to insert dynamic code into their pages, and I'm wondering if XSP could give me the ability to create this

Re: Need A Better Understanding of XSP Role

2004-12-21 Thread Derek Hohls
I think there have already been some good replies to this; my 2c would be to look carefully at what dynamic aspects are required by your users. Remember in Cocoon the aim is the "separation of concerns". The main reason that Cocoon is not just another "templating" framework is to avoid mixing up