Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-12 Thread Alan Kennedy
[Alan Kennedy] Looking at this in an MVC context ... [Phillip J. Eby] As soon as you start talking about what templates should or should not do (as opposed to what they *already* do), you've stopped writing an inclusive spec and have wandered off into evangelizing a particular

Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-07 Thread Jim Fulton
I'm not sure what you're talking about here. Are you talking about WSGI? Or the templating effort? I've tuned out the templating discussion. I think you and others did a fantastic job with WSGI. (Based on my experience I do think it needs more work in the future, but that's beside the point.)

Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-07 Thread Phillip J. Eby
At 09:08 AM 2/7/2006 -0500, Jim Fulton wrote: I'm not sure what you're talking about here. Are you talking about WSGI? Or the templating effort? I've tuned out the templating discussion. Just the templating effort, and that only for the time being. I just don't feel I have enough time to

Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-07 Thread Stephan Richter
On Tuesday 07 February 2006 10:20, Phillip J. Eby wrote: Despite some skepticism about the templating effort, I certainly planned to evaluate it when it settled down. I'm not complaining about you personally tuning out; it's just that I ended up being a sole advocate for stuff I thought Zope

Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-07 Thread Ian Bicking
Phillip J. Eby wrote: Despite some skepticism about the templating effort, I certainly planned to evaluate it when it settled down. I'm not complaining about you personally tuning out; it's just that I ended up being a sole advocate for stuff I thought Zope would need in order to utilize

Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-07 Thread Phillip J. Eby
At 11:12 AM 2/7/2006 -0600, Ian Bicking wrote: Maybe the reason those voices are missing -- I now realize -- is that there aren't many active page frameworks left. All the more reason to encourage an approach that allows migrating existing code written using those systems! :) I think it's

Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-07 Thread Jonathan Ellis
On Tue, 07 Feb 2006 11:12:04 -0600, Ian Bicking [EMAIL PROTECTED] said: Maybe the reason those voices are missing -- I now realize -- is that there aren't many active page frameworks left. Spyce was, but since then I believe a more traditional controller-driven API has been added Yes, but

Re: [Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-07 Thread Jacob Smullyan
On Tue, Feb 07, 2006 at 11:12:04AM -0600, Ian Bicking wrote: Maybe the reason those voices are missing -- I now realize -- is that there aren't many active page frameworks left. Yup. SkunkWeb too, which like Myghty also started out as a port of Mason, now has a controller framework, with

[Web-SIG] Bowing out (was Re: A trivial template API counter-proposal)

2006-02-06 Thread Phillip J. Eby
At 08:02 PM 2/5/2006 +, Alan Kennedy wrote: Looking at this in an MVC context, the application is responsible for populating the Model (user namespace), and selecting which View (template-media-type) is suitable for return to the user. Templates should not vary media types. HTTP headers do