Re: Should the template system try to be a bit smarter about TypeError?

2006-05-07 Thread Kieran Holland
I don't understand why the TypeError needs to be caught at all. If the wrong number of arguments are passed then it seems to me that something is genuinely broken - is there some reason to mask it? FWIW I removed that catch as part of #1400 and haven't missed it. Kieran --~--~-~--~---

Re: proposal: endif, endfor etc assume whatever follows in tag is comment

2006-03-14 Thread Kieran Holland
On 3/14/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > On 3/13/06, Jonathan Daugherty <[EMAIL PROTECTED]> wrote: > > Maybe implement generic support for /* .. */ in template tags? > A definite no on that one -- it's too programmerish. hugo wrote: > >{% endif %}{# endif start_process #} > > Ug

Re: proposal: endif, endfor etc assume whatever follows in tag is comment

2006-03-13 Thread Kieran Holland
Tom Tobin wrote: > On 3/14/06, Eugene Lazutkin <[EMAIL PROTECTED]> wrote: > > > > Kieran Holland wrote: > > >>> > > >>> {% endif %}{# endif start_process #} > > >> I think that original idea is cleaner: {% endif start_process %}. &

Re: proposal: endif, endfor etc assume whatever follows in tag is comment

2006-03-13 Thread Kieran Holland
Eugene Lazutkin wrote: > Kieran Holland wrote: > > > > I don't like the idea of arbitrary content in template tags either but > > does your "definite no" also apply to this old idea: > > > > {% endif %}{# endif start_process #} > > I think

Re: proposal: endif, endfor etc assume whatever follows in tag is comment

2006-03-13 Thread Kieran Holland
On 3/14/06, Adrian Holovaty <[EMAIL PROTECTED] > wrote: On 3/13/06, Jonathan Daugherty <[EMAIL PROTECTED]> wrote:> Maybe implement generic support for /* .. */ in template tags? A definite no on that one -- it's too programmerish. I don't like the idea of arbitrary content in template tags either b

Re: Arguing for convention over configuration

2005-09-07 Thread Kieran Holland
On 08/09/05, mrelectron <[EMAIL PROTECTED]> wrote: > totally plus 1 with all of this, i would be more than happy to do the > documention. the simple conventions and guidance which RoR gives for > application and project architecture has helped a great deal in getting > it accepted. Cool. The exi

Re: Arguing for convention over configuration

2005-09-04 Thread Kieran Holland
> On 04/09/05, Eugene Lazutkin > <[EMAIL PROTECTED]> wrote: > > > 1) Currently app's name should be unique within a project. I want to be > > able > > to reuse the same app several times. Example: categories. I may have > > different categories for my blog, for my bookmarks, and for my articles.

Re: Arguing for convention over configuration

2005-09-04 Thread Kieran Holland
Thanks for your ideas, I hope that others - especially those with Ruby experience - may be able to offer some informed solutions. In the case of points (1) and (6) I wonder if the following would help: On 04/09/05, Eugene Lazutkin <[EMAIL PROTECTED]> wrote: > 1) Currently app's name should be