Comments on: Using the new HTMLHelperProperty in MachII 1.8 http://www.tntechnohermit.com/2009/06/27/using-the-new-htmlhelperproperty-in-machii-1-8/ Random Thoughts of a Techno-Hermit Mon, 30 Jan 2012 21:07:54 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Dan Skaggs http://www.tntechnohermit.com/2009/06/27/using-the-new-htmlhelperproperty-in-machii-1-8/comment-page-1/#comment-340 Dan Skaggs Tue, 14 Jul 2009 02:58:14 +0000 http://dan.skaggsfamily.ws/?p=251#comment-340 Thanks Peter...I'll keep that in mind. We're not using any caching at the moment but that will be something good to remember when we get to that point. Thanks Peter…I’ll keep that in mind. We’re not using any caching at the moment but that will be something good to remember when we get to that point.

]]> By: Peter J. Farrell http://www.tntechnohermit.com/2009/06/27/using-the-new-htmlhelperproperty-in-machii-1-8/comment-page-1/#comment-339 Peter J. Farrell Tue, 14 Jul 2009 01:55:15 +0000 http://dan.skaggsfamily.ws/?p=251#comment-339 Dan, FYI don't use cfhtmlhead if you are ever going to use Mach-II caching as the cfhtmlhead tags won't get replayed when an item is gotten from the cache. Use the addHtmlHeadElement() method available in the ViewContext to add an element to the head. The CacheHandler uses this as an observer point so they can get replayed when using cached data. We do the same for cfheader tag -- use addHTTPHeader() method instead. Probably should highlight this more in the docs. Dan, FYI don’t use cfhtmlhead if you are ever going to use Mach-II caching as the cfhtmlhead tags won’t get replayed when an item is gotten from the cache. Use the addHtmlHeadElement() method available in the ViewContext to add an element to the head. The CacheHandler uses this as an observer point so they can get replayed when using cached data. We do the same for cfheader tag — use addHTTPHeader() method instead. Probably should highlight this more in the docs.

]]> By: Peter J. Farrell http://www.tntechnohermit.com/2009/06/27/using-the-new-htmlhelperproperty-in-machii-1-8/comment-page-1/#comment-322 Peter J. Farrell Mon, 29 Jun 2009 07:19:05 +0000 http://dan.skaggsfamily.ws/?p=251#comment-322 Dan, yeah we thought about combining all ad-hoc code into one script tag however it gets pretty complicated when you mix in M2 caching and subroutines. We weren't ready to tackle this in 1.8 and something I'm sure we'll think about for 1.9. Dan, yeah we thought about combining all ad-hoc code into one script tag however it gets pretty complicated when you mix in M2 caching and subroutines. We weren’t ready to tackle this in 1.8 and something I’m sure we’ll think about for 1.9.

]]> By: Dan Skaggs http://www.tntechnohermit.com/2009/06/27/using-the-new-htmlhelperproperty-in-machii-1-8/comment-page-1/#comment-320 Dan Skaggs Sun, 28 Jun 2009 14:34:15 +0000 http://dan.skaggsfamily.ws/?p=251#comment-320 <a href="#comment-318" rel="nofollow">@Peter J. Farrell </a> Thanks for the feedback Peter...always nice to know someone is reading this. I took a look at the script tag you mentioned. That's a much nicer solution than having your scripts sprinkled through the body of the rendered HTML document and for someone that's not using the HTMLHelperProperty in their application, that would be the way to go. However, I still feel like there would be some benefit to allowing the HTMLHelperProperty to do something similar, but combine all the ad-hoc scripts that are set into it through the request into one <script> tag in the <head> section of the HTML document. With the current M2 script view, you'll wind up with separate <script> tags in the header for each time you call the tag. Some would say that this is nitpicky and I'd probably agree, but the functionality is so close to being there as it is. For those using the HTMLHelperProperty in their applications, it would be nice to do everything in one place rather than using 2 different mechanisms. @Peter J. Farrell
Thanks for the feedback Peter…always nice to know someone is reading this.

I took a look at the script tag you mentioned. That’s a much nicer solution than having your scripts sprinkled through the body of the rendered HTML document and for someone that’s not using the HTMLHelperProperty in their application, that would be the way to go.

However, I still feel like there would be some benefit to allowing the HTMLHelperProperty to do something similar, but combine all the ad-hoc scripts that are set into it through the request into one <script> tag in the <head> section of the HTML document.

With the current M2 script view, you’ll wind up with separate <script> tags in the header for each time you call the tag. Some would say that this is nitpicky and I’d probably agree, but the functionality is so close to being there as it is. For those using the HTMLHelperProperty in their applications, it would be nice to do everything in one place rather than using 2 different mechanisms.

]]> By: Peter J. Farrell http://www.tntechnohermit.com/2009/06/27/using-the-new-htmlhelperproperty-in-machii-1-8/comment-page-1/#comment-318 Peter J. Farrell Sat, 27 Jun 2009 19:45:11 +0000 http://dan.skaggsfamily.ws/?p=251#comment-318 Great post Dan! Glad you like everything, let us know if the leaving off the .js extensions is a bug of ours. It works on Adobe CF8 and OpenBD just fine so I think there might be a little buglet in Railo maybe. For things that use multiple libraries of JS / CSS (one example is Lightwindow or Lightbox on Prototype that uses prototype / scriptaculous / css files) is to use the asset packages which you say all the files you need for that asset package as metadata package and use addAsset("nameOfPackage"). Any js files you that have already been included in the head won't be added twice. Also, it makes it easier because you change versions of a library (and the file name changes), you make the change in one place versus in multiple view files. This would be great for your example that uses jquery, datatables and fancybox. For ad-hoc js code, take a peek at the script tag in the View library: ad-hoc code here By default the script tag in the view custom tag library puts stuff in the HTML head area just like the HTMLHelper. There is also a "style" tag that does similar stuff. I don't know your blog accepts links, but here is the link to the doco: http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/wiki/MachII1.8SpecificationViewTagLib#ThescriptTag Great post Dan! Glad you like everything, let us know if the leaving off the .js extensions is a bug of ours. It works on Adobe CF8 and OpenBD just fine so I think there might be a little buglet in Railo maybe. For things that use multiple libraries of JS / CSS (one example is Lightwindow or Lightbox on Prototype that uses prototype / scriptaculous / css files) is to use the asset packages which you say all the files you need for that asset package as metadata package and use addAsset(“nameOfPackage”). Any js files you that have already been included in the head won’t be added twice. Also, it makes it easier because you change versions of a library (and the file name changes), you make the change in one place versus in multiple view files. This would be great for your example that uses jquery, datatables and fancybox.

For ad-hoc js code, take a peek at the script tag in the View library:

ad-hoc code here

By default the script tag in the view custom tag library puts stuff in the HTML head area just like the HTMLHelper. There is also a “style” tag that does similar stuff. I don’t know your blog accepts links, but here is the link to the doco:
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/wiki/MachII1.8SpecificationViewTagLib#ThescriptTag

]]>