What exactly do you have in mind with the filter attribute? Because I
could think of situations where you might want to import the same file
for different browser versions.
Uli
Howard Lewis Ship schrieb:
I'm afraid its time to go for something a bit more structured:
@ImportJavaScript({
@Import("classpath:foo.js" filter="IE5" combine=false),
@Import("context:bar.js")})
public class MyJSComponent ...
... also the term "import" is much more accurate than "include".
This raises some ambiguities: what if different imports of the same JS
file use different values for filter or combine? I'd say that's an
error.
On Tue, Nov 24, 2009 at 12:38 PM, Thiago H. de Paula Figueiredo
<thiag...@gmail.com> wrote:
Em Tue, 24 Nov 2009 18:25:10 -0200, Howard Lewis Ship <hls...@gmail.com>
escreveu:
I'm picturing this as a new form of the @IncludeJavascript annotation
that allows new options to be included, such as browser type (i.e.,
build that comment thingey around the <script> tag) and combine=false.
Would it be a new annotation or just adding properties to
@IncludeJavascript?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
