I originally thought about just parsing the return in jQuery, until I realized what this code was ultimately going to have to do. The items in this list are actually going to wind up having text hyperlinks, form buttons, and maybe even images added to them, so for me it's easier to build it out in CF and just have jQuery display it. Too much JavaScript hurts my head. :)
I'm about to the point I'm ready to ditch jQuery and just do what I need to do without trying to be all "ajaxy" with it. Thanks, Eric Cobb ECAR Technologies, LLC http://www.ecartech.com http://www.cfgears.com Cutter (ColdFusion) wrote: > If Eric is returning a plain string, then there is no need to > SerializeJson() the result, as all he needs is the string. That is why > Eric is getting the additional slashes in his closing tag, because the > SerializeJson() method is automatically escaping the slash characters. > > I'll agree with Michael though. If you did get a Json return, and just > parsed it to add the <li> tags in your doc you'll reduce your > (unnecessary) server-side overhead. Returning the string is easier, but > not necessarily best for you application or your code reusability. > > Steve "Cutter" Blades > Adobe Community Professional - ColdFusion > Adobe Certified Professional > Advanced Macromedia ColdFusion MX 7 Developer > > Co-Author of "Learning Ext JS" > http://www.packtpub.com/learning-ext-js/book > _____________________________ > http://blog.cutterscrossing.com > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:334456 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
