Re: [Reactor For CF] getXyzRecord() - alternative proposal

[Jared Rypka-Hauer]

Seldom. :) Seriously, though, this is the best proposal, I think... it's like the Reactor version of XForms in that it allows you to customize the output per-item (form, project, style name, whatever) and fixes the problem at the root level. I also appreciate the differentiation between advanced users of Reactor and less-advanced users of Reactor. I think that for advanced users there are going to be some things that don't get a lot of press, that can be confusing and hard to understand, but that are still essential to the usability of the framework. I think of it like "the Reactor Developer SDK" that gives people that want/need it the ability to extend or alter the default behaviors of Reactor to get the most out if it *in the context of their daily work.* That's what's critical for Shannon and Kurt right now... at the moment they can either hack the framework or their apps, but there's no happy solution to the problem without one or the other. Since Reactor seems to be a tool that spans all experience levels, it's going to have to accommodate both total newbies and advanced power-users... being able to specify the XSL sheet that controls the CFML emitters is probably the very best bet and a solution that could fix the problem for everyone. Laterz, J ------------------------------------------------ Jared C. Rypka-Hauer Continuum Media Group LLC http://www.web-relevant.com Member, Team Macromedia - ColdFusion "That which does not kill me makes me stranger." - Yonah Schmeidler On Mar 24, 2006, at 12:23 PM, Sean Corfield wrote: <snippage /> Thoughts? -- Sean A Corfield -- http://corfield.org/ Got frameworks? "If you're not annoying somebody, you're not really alive." -- Margaret Atwood