Hi, Bob! >On Fri, Oct 22, 2010 at 1:46 AM, Bob Schellink <[email protected]> wrote: > Hi Gilberto, > > Each page and control has a headElements List variable where JS and CSS can > be added to. > > At runtime the ClickServlet creates a PageImports instance and invokes it's > populateTemplateModel > method. This method adds the page headElements and then iterates over every > page control (and their > children, recursively) and gathers their headElements into a single List > which is made available to > Velocity using the variable, $headElements. > > If you debug the Page#hedElements, it will be empty, unless that page is > adding its own head > elements to the page. If you debug menu.headElements, you'll see the menu JS > and CSS it needs to > render correctly. So each control is responsible for it's own resources. > > If you are interested in how Click works, I highly recommend looking at > ClickServlet source code. It > It is a fairly large class but straightforward and defines exactly how the > Click runtime operates. > > Does this answer your question? > Yes, thanks a lot!
I was trying to help dukedosa (I don't know his name), he used the nabble[1] forum to make that question. Regards, [1]http://click.1134972.n2.nabble.com/
