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
Marius,
I love the simplicity of your proposal but I think that's also its
problem. Let's say I have something with several dependencies:
lift:MySnipet.work
lift:dependencies
script src=dep1.js/
script src=dep2.js/
script src=myLib.js/
// you got the idea
/lift:dependencies
On Mar 8, 11:02 am, Peter Robinett pe...@bubblefoundry.com wrote:
Marius,
I love the simplicity of your proposal but I think that's also its
problem. Let's say I have something with several dependencies:
lift:MySnipet.work
lift:dependencies
script src=dep1.js/
script
Hi guys,
Sorry I'm only coming back to this discussion now. I think what you're
both proposing are the two parts of what should be the complete use-
case. Yes, dependencies _exist_ per page and, yes, you want to
_declare_ them per snippet or CometActor. The last (and only) commit
on my
On Mar 6, 9:14 pm, Peter Robinett pe...@bubblefoundry.com wrote:
Hi guys,
Sorry I'm only coming back to this discussion now. I think what you're
both proposing are the two parts of what should be the complete use-
case. Yes, dependencies _exist_ per page and, yes, you want to
_declare_
Yes I believe this needs a bit more thinking. I didn;t spend too much
time into this but perhaps add a LiftRules function to describe the
dependency tree per page:
i.e.
var jsDependencies : (Req) = JsDependencyTree
where
case class JsDependencyTree (url: String, dependencies:
JsDependencyTree
On Mar 1, 1:50 pm, Jeppe Nejsum Madsen je...@ingolfs.dk wrote:
Marius marius.dan...@gmail.com writes:
Yes I believe this needs a bit more thinking. I didn;t spend too much
time into this but perhaps add a LiftRules function to describe the
dependency tree per page:
i.e.
var
Marius marius.dan...@gmail.com writes:
[...]
I'm not sure that doing this per snippet is the right approach.
Maybe we differ in our thinking then :-) I'm thinking more in a
component oriented approach where I would like to put a widget on a
page. I'll just add the correct snippet tags to my
Yes we do have different perspectives. I'm saying for page X here
these are the JS dependencies whether you seem to say here is a
snippet, and it needs these dependencies
I'd still prefer my paradigm (not because of my ego) because it'd be
easier to manage redundancies, it applies generically for
Marius marius.dan...@gmail.com writes:
Yes we do have different perspectives. I'm saying for page X here
these are the JS dependencies whether you seem to say here is a
snippet, and it needs these dependencies
Yes
I'd still prefer my paradigm (not because of my ego) because it'd be
easier
Issue 281 is not going to make it into M3. The specific issue that
needs to be solved first is how to manage dependencies across multiple
snippets on one page. See the Assembla page for more information:
http://www.assembla.com/spaces/liftweb/tickets/281
Peter
On Feb 26, 5:14 pm, Peter Robinett
Mads, thanks for bringing ticket 281 to my attention, I'll address it
in my patch.
Jeppe, that's how I plan on using it with Flot: having Flot.init
register the plugins and in the charts call toHTML as needed.
Should have everything up on my pr1001_issue_322 branch by tomorrow.
Peter
On Feb
12 matches
Mail list logo
