Marius <marius.dan...@gmail.com> writes: > On Mar 6, 9:14 pm, Peter Robinett <pe...@bubblefoundry.com> wrote:
[...] > Hmmm ... anything that is outputting (x)html. We have snippets, comet > actors, LiftView-s. Any of these can called multiple times but IMHO > registration should happen once. For snippets and comet we could a > nested snippet such as: > > > <lift:MySnipet.work> > <lift:dependencies> > <script src="bla.js"/> > // you got the idea > </lift:dependencies> > // specific tags > </lift:MySnipet.work> I think my use case is slightly different, but can still be handled with the above. Basically, I don't want the dependencies to show up in my markup, but be handled by higher level components (or snippets) In my markup, I'll have a high level snippet: <lift:Chart.render> stuff </lift:Chart.render> The chart snippet will now, depending on a lot of factors, emit a number of dependencies (eg jquery, jqplot & a pie chart render). But I think this should still work given the above. [...] > I'm not sure if we should worry about circular dependencies in this > case and neither for duplicates as lift head merge mechanism detects > duplicates. I agree, lets see if this becomes a problem.... > I think this would cover snippets and comet actors and it should also > work for LiftView-s > Thoughts ? Sounds good. But it seems to leave the dependency management to the user (e.g. in the above scenario, I would have to declare all 3 dependencies, not just the pie chart render, that will then include jqplot that will then include jquery) ?? This is not necessarily a bad thing..... /Jeppe [...] -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
