Comments on: Enabling Implicit Context Variables Resolution in Template Files http://blogs.jetbrains.com/idea/2009/08/enabling-implicit-context-variables-resolution-in-template-files/ tips & tricks, news, how-to's Wed, 16 May 2012 21:16:05 +0000 http://wordpress.org/?v=2.6.5 By: Tom Davies http://blogs.jetbrains.com/idea/2009/08/enabling-implicit-context-variables-resolution-in-template-files/#comment-205731 Tom Davies Fri, 25 Nov 2011 01:18:19 +0000 http://blogs.jetbrains.com/idea/?p=1484#comment-205731 Any way of doing this for macro parameters, i.e. #* @vtlvariable name="page" type="xxx" *# #macro (foo $page) $page.attribute <--- get's a grey squiggly :-( ... Any way of doing this for macro parameters, i.e.

#* @vtlvariable name=”page” type=”xxx” *#
#macro (foo $page)
$page.attribute <— get’s a grey squiggly :-(
…

]]> By: Dave Merrill http://blogs.jetbrains.com/idea/2009/08/enabling-implicit-context-variables-resolution-in-template-files/#comment-139173 Dave Merrill Wed, 28 Jul 2010 14:12:54 +0000 http://blogs.jetbrains.com/idea/?p=1484#comment-139173 Is there any way to do something like this outside of Velocity? I work on a large ColdFusion app with a lot of static functions loaded into server space, and called like this: Server.MyApp.UDF.util.someFunction(); Server.MyApp.UDF.xml.someFunction(); There are thousands of references like this in our code that a) are all flagged as unresolved, and b) don't provide argument hints. The path segments at the 'util' and 'xml' level above correspond to physical cfm or cfc files, and I'd really like some way to tell IDEA on a project- or module-wide basis that to resolve this: Server.MyApp.UDF.xml ...it should look for the function here: /ProjectRoot/udf/util.cfm Is there any way to do something like this outside of Velocity? I work on a large ColdFusion app with a lot of static functions loaded into server space, and called like this:
Server.MyApp.UDF.util.someFunction();
Server.MyApp.UDF.xml.someFunction();
There are thousands of references like this in our code that a) are all flagged as unresolved, and b) don’t provide argument hints.
The path segments at the ‘util’ and ‘xml’ level above correspond to physical cfm or cfc files, and I’d really like some way to tell IDEA on a project- or module-wide basis that to resolve this:
Server.MyApp.UDF.xml
…it should look for the function here:
/ProjectRoot/udf/util.cfm

]]> By: A. Adrian http://blogs.jetbrains.com/idea/2009/08/enabling-implicit-context-variables-resolution-in-template-files/#comment-114126 A. Adrian Sat, 08 Aug 2009 09:11:57 +0000 http://blogs.jetbrains.com/idea/?p=1484#comment-114126 While variable resolution is a must for usable Velocity support, polluting the template files with such comments is not the best idea IMHO. Different frameworks(that use velocity) will use different methods to fill the context with variables (and for many of them the variable "tree" can be huge). I think a much better and general approach would be to let the user set in the Velocity Facet a sort of "template variable provider" class. For this "template variable provider", one approach could be similar to a "JDBC driver" (and would not depend on IntelliJ), that each framework (that needs Velocity) could implement (in a much simpler way than making an IntelliJ plug-in right now). While variable resolution is a must for usable Velocity support, polluting the template files with such comments is not the best idea IMHO.
Different frameworks(that use velocity) will use different methods to fill the context with variables (and for many of them the variable “tree” can be huge).
I think a much better and general approach would be to let the user set in the Velocity Facet a sort of “template variable provider” class.
For this “template variable provider”, one approach could be similar to a “JDBC driver” (and would not depend on IntelliJ), that each framework (that needs Velocity) could implement (in a much simpler way than making an IntelliJ plug-in right now).

]]>