<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Determining Template Data Language by a File Extension</title>
	<atom:link href="http://blogs.jetbrains.com/idea/2009/03/determining-template-data-language-by-a-file-extension/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.jetbrains.com/idea/2009/03/determining-template-data-language-by-a-file-extension/</link>
	<description>tips &#38; tricks, news, how-to's</description>
	<pubDate>Wed, 16 May 2012 21:11:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Data Entry Washington</title>
		<link>http://blogs.jetbrains.com/idea/2009/03/determining-template-data-language-by-a-file-extension/#comment-118221</link>
		<dc:creator>Data Entry Washington</dc:creator>
		<pubDate>Fri, 23 Oct 2009 13:48:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/idea/?p=369#comment-118221</guid>
		<description>Thanks for sharing this useful information, especially about the vital codes &#38; templates. :)</description>
		<content:encoded><![CDATA[<p>Thanks for sharing this useful information, especially about the vital codes &amp; templates. <img src='http://blogs.jetbrains.com/idea/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Gromov</title>
		<link>http://blogs.jetbrains.com/idea/2009/03/determining-template-data-language-by-a-file-extension/#comment-101562</link>
		<dc:creator>Peter Gromov</dc:creator>
		<pubDate>Thu, 26 Mar 2009 17:01:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/idea/?p=369#comment-101562</guid>
		<description>Joseph,

That would be great, I agree. A workaround would be to map CSS file extension to Velocity and set CSS as template data language, but then all CSS files would be treated like Velocity's. The problem is that this is not easy to implement. Surely not in 8.1.x. Probably in IntelliJ IDEA 9, but I'm not sure.</description>
		<content:encoded><![CDATA[<p>Joseph,</p>
<p>That would be great, I agree. A workaround would be to map CSS file extension to Velocity and set CSS as template data language, but then all CSS files would be treated like Velocity&#8217;s. The problem is that this is not easy to implement. Surely not in 8.1.x. Probably in IntelliJ IDEA 9, but I&#8217;m not sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph</title>
		<link>http://blogs.jetbrains.com/idea/2009/03/determining-template-data-language-by-a-file-extension/#comment-101527</link>
		<dc:creator>Joseph</dc:creator>
		<pubDate>Thu, 26 Mar 2009 15:59:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.jetbrains.com/idea/?p=369#comment-101527</guid>
		<description>Trying the feature from the "Template Data Languages" I think the behavior should be just the opposite of how it's done now:
Right now the user can select for a file detected as containing velocity/Freemarker by it's extension that it should contain e.g. CSS language too (or the other languages from that drop box).
This is however useless for most cases/framework, because the extension is the very problem (and the double extension trick is not accepted in many projects).

Why not simplify for most use cases and allow to select on a CSS file(with a normal CSS extension) to be "Velocity aware" by having in that drop box (velocity and freemarker only ) ?
This is how most frameworks use Velocity - they keep the original extension (e.g. CSS) but the code contains Velocity code too.</description>
		<content:encoded><![CDATA[<p>Trying the feature from the &#8220;Template Data Languages&#8221; I think the behavior should be just the opposite of how it&#8217;s done now:<br />
Right now the user can select for a file detected as containing velocity/Freemarker by it&#8217;s extension that it should contain e.g. CSS language too (or the other languages from that drop box).<br />
This is however useless for most cases/framework, because the extension is the very problem (and the double extension trick is not accepted in many projects).</p>
<p>Why not simplify for most use cases and allow to select on a CSS file(with a normal CSS extension) to be &#8220;Velocity aware&#8221; by having in that drop box (velocity and freemarker only ) ?<br />
This is how most frameworks use Velocity - they keep the original extension (e.g. CSS) but the code contains Velocity code too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

