Re: PROPOSAL: Template Editor Enhancements

2007-03-23 Thread Allen Gilliland
Now that I've looked at this a bit I have a couple more things that I would like to suggest ... 1. If the template is required (or tied to a specific action in the upcoming code) then we don't show the Name, Link, and Description elements as form fields. Instead we just provide targeted help

Re: PROPOSAL: Template Editor Enhancements

2007-03-23 Thread Dave
On 3/23/07, Allen Gilliland [EMAIL PROTECTED] wrote: Now that I've looked at this a bit I have a couple more things that I would like to suggest ... 1. If the template is required (or tied to a specific action in the upcoming code) then we don't show the Name, Link, and Description elements as

Re: PROPOSAL: Template Editor Enhancements

2007-03-21 Thread Allen Gilliland
Dave wrote: On 3/19/07, Allen Gilliland [EMAIL PROTECTED] wrote: 4. I think the content-type control should work differently than you described. I think the only 2 options should be automatic and manual. So for automatic content-type it would work exactly how it does now where we ask the

Re: PROPOSAL: Template Editor Enhancements

2007-03-19 Thread Allen Gilliland
I agree with most of these changes, but here's a few things I don't really like ... 1. On the templates list page I don't think we need the column for the content-type. The overwhelming majority of users don't care about manually managing the content type for their templates so I think we

Re: PROPOSAL: Template Editor Enhancements

2007-03-19 Thread Dave
On 3/19/07, Allen Gilliland [EMAIL PROTECTED] wrote: I agree with most of these changes, but here's a few things I don't really like ... Good feedback. I agree with all of these changes. Anybody else have feedback on this? - Dave 1. On the templates list page I don't think we need the

Re: PROPOSAL: Template Editor Enhancements

2007-03-19 Thread Elias Torres
Does this work depend on groovy, ruby, etc? -Elias Allen Gilliland wrote: I agree with most of these changes, but here's a few things I don't really like ... 1. On the templates list page I don't think we need the column for the content-type. The overwhelming majority of users don't care

Re: PROPOSAL: Template Editor Enhancements

2007-03-19 Thread Dave
On 3/19/07, Elias Torres [EMAIL PROTECTED] wrote: Does this work depend on groovy, ruby, etc? No. Apart from the UI tweaks, all I'm doing is adding a way for users to specify for each Template: 1) the template language used by the page and 2) the content-type generated by a template. Roller

Re: PROPOSAL: Template Editor Enhancements

2007-03-19 Thread James M Snell
One additional point that I would definitely like to see covered are template pages that require user authentication. - James Dave wrote: On 3/19/07, Elias Torres [EMAIL PROTECTED] wrote: Does this work depend on groovy, ruby, etc? No. Apart from the UI tweaks, all I'm doing is adding a

Re: PROPOSAL: Template Editor Enhancements

2007-03-19 Thread Dave
On 3/19/07, Allen Gilliland [EMAIL PROTECTED] wrote: 4. I think the content-type control should work differently than you described. I think the only 2 options should be automatic and manual. So for automatic content-type it would work exactly how it does now where we ask the appserver for the