That's a nice idea. Consistent with the way other plugins (like custom directives) are handled as well, i.e. in the Velocity properties file.
WILL ----- Original Message ----- From: "Geir Magnusson Jr." <[EMAIL PROTECTED]> To: "Velocity Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, October 28, 2003 8:49 AM Subject: Re: input event cartridge > > On Tuesday, October 28, 2003, at 09:05 AM, Will Glass-Husain wrote: > > > Yay! I've been using this patch on my private build for some time > > now, and > > find it quite useful. > > > > What are you thinking regarding your comment on configuring an event > > cartridge? Do you mean that there should be a "relativeload" event > > cartridge that can be used at the developer's discretion? > > Well, right now, if you want to use the event handling stuff, you have > to add an event cartridge in the code, which doesn't work if it isn't > your code. It might be nice to configure an event cartridge via > properties rather than code, so that you could add a input handler that > does what claude wants, for example... > > > > > WILL > > > > > > ----- Original Message ----- > > From: "Geir Magnusson Jr." <[EMAIL PROTECTED]> > > To: "Velocity Developers List" <[EMAIL PROTECTED]> > > Sent: Tuesday, October 28, 2003 3:51 AM > > Subject: Re: patch requests > > > > > >> > >> On Sunday, October 26, 2003, at 12:33 AM, Will Glass-Husain wrote: > >> > >>> > >>> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20342 > >>> new event handler for input directives (#parse, #include) > >> > >> I love this idea, and there is a related suggestion : > >> > >> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18072 > >> > >> which I am less of a fan of the solution, because I think you'd run > >> into serious confusion especially w/ things invoked from VMs. > >> > >> However, I think we can combine the two ideas because the former > >> covers > >> the latter. The event handler method is natural now. In order to > >> make > >> it automatic, as Claude wants, we can look at being able to configure > >> an event cartridge rather than only be able to do in code. That way > >> you can modify behavior through configuration. > >> > >> Does that sound right? > >> > >> I'll start with Will's patch. > >> > >> -- > >> Geir Magnusson Jr 203-247-1713(m) > >> [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] > > > > > -- > Geir Magnusson Jr 203-247-1713(m) > [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]
