On Fri, 09 Jan 2015 14:49:22 -0200, nhhockeyplayer nashua
<nhhockeypla...@hotmail.com> wrote:
Good question Thiago,
I dont know what your definition of import is.
There's only one: importing CSS, JavaScript or mudules using
JavaScriptSupport's import*() methods directly or indirectly through
@Import(stacks="yourStackId").
My scripts are the ones from the bower path, mixins and top of path.
So this is obviously the JavaScriptStack interface in action. Isnt this
the import ?
Apparently, yes.
Import meaning you specify the module with script tag, type, src in the
head section.
Nope. See definition above. Don't use the script tag directly in
templates. Let Tapestry handle this for you.
All I am thinking is a JavaScriptStack class exists for me to implement
and that it should do it all ?
Absolutely not. See above.
Thats why I am sifting thru the markup generated.
That's actually a very good thing to do. :)
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
