Sean, Thanks for pointing that out. It certainly is a problem in the documentation.
Those "convolutions" actually have nothing to do with white-space at all (nor do they impact it). It is just a syntax that I personally preferred as it makes it easy to ignore the CFML and look only at the HTML code - I like having all of my code for one layout in one easy to read file. Even at that, I have started trending the other way as it turns out that it is pretty easy to ignore the CFML either way. I should change the examples to have space between the cffunction tags. The opening space between cfcomponent and cffunction also doesn't impact space. In fact, I have a <cfcontent reset="yes"> which works in every CFML engine I have tested to do nothing but ensure that the doctype declaration is the first line sent to the output buffer regardless of what has happened before that point. I absolutely think it is the best of both worlds and I have tried custom tags and plain old includes. Layout Components can be used separately from Neptune and have their own documentation. http://www.bryantwebconsulting.com/docs/layout/ I compare to other approaches here: http://www.bryantwebconsulting.com/docs/layout/comparisons.cfm Just to illustrate one of the advantages of this approach, here is a code example of a very simple page: <cf_layout title="Congratulations!"> <script src="/my.js" type="text/javascript"></script> <cf_layout showTitle="true"> <p>Welcome to Neptune!</p> <cf_layout> The "script" tag here is output in the HEAD of the document. No flushing or cfsavecontent trickery is used so it incurs no restrictions on tag use at all. Thanks, Steve > I notice that layouts are provided through CFCs that output HTML. The > example shows the convolutions needed to avoid extraneous whitespace, > such as running functions together: > ... > > </cffunction><cffunction name="body" access="public" output="yes"> ... > > > (and I believe your example still generates unwanted whitespace since > you have a blank line between your opening <cfcomponent> tag and the > first <cffunction> tag?). > > This seems to be worst of both worlds to me. Have you considered > using > custom tags or plain old include files for the elements of the layout > instead? > -- > Sean A Corfield -- (904) 302-SEAN > Railo Technologies, Inc. -- http://getrailo.com/ > An Architect's View -- http://corfield.org/ > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:340457 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
