This could be achieved by having a boolean variable in the loadJS tag that adds them to request.inFooter. (This param should have information that the developer need to manually add a <skin> or <core> tag to output the script-tags. where they want.)
If we rename jsInHead.cfm to jsLoad.cfm we could call it with a boolean variable that does a <cfoutput> insted of <cfhtmlhead>. Or we could just make a copy of the jsInHead.cfm and call it jsInFooter.cfm. kl. 14:06:57 UTC+2 onsdag 20. juni 2012 skrev Geoff Bowers følgende: > > On 20 June 2012 19:51, Phillip R <[email protected] <javascript:>> > wrote: > > Because javascript is a load blocker, best practice is to put the bulk > of it > > at the end of the page. I've always been a bit uncomfortable with all > those > > js files being loaded in the head so though I'd just ask the question. > It > > was really about managing scripts loaded from tags. > > If you have a single loadjs then you will have a single, combined, > compressed and cacheable JS file which is the best thing you can do to > combat load blocking. Sometimes this is not possible to get them all, > but you can certainly make it respectable up there in the HEAD. Do > the same for loadcss and you can really improve front end performance > ;) > > -- geoff > http://www.daemon.com.au/ > skype. gb.daemon > twitter. @modius > -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry --- You received this message because you are subscribed to the Google Groups "farcry-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
