On May 10, 4:57 pm, David Pollak <feeder.of.the.be...@gmail.com>
wrote:
> On Sun, May 10, 2009 at 6:55 AM, marius d. <marius.dan...@gmail.com> wrote:
>
> > People can choose to "smash" multiple js/css files into a single one,
> > in fact it is a common practice. However for scripts that can be
> > deferred putting them at the bottom of the page can improve rendering.
>
> Okay.. so we're not actually putting the scripts on the page, we're just
> putting them right about the </body> tag?
Yes ... for instance:
<lift:tail>
<script src="app.js" />
<lift:tail>
would yield:
<html>
....
<body>
....
<script src="app.js" />
</body>
</html>
At least this is what I'm referring to.
>
>
>
>
>
> > Br's,
> > Marius
>
> > On May 10, 4:42 pm, David Pollak <feeder.of.the.be...@gmail.com>
> > wrote:
> > > On Fri, May 8, 2009 at 5:26 PM, Timothy Perrett <timo...@getintheloop.eu
> > >wrote:
>
> > > > Sounds like this could be a neat addition. Looking forward to see what
> > you
> > > > come up with :-)
>
> > > I'm not 100% keen on it. Loading a ton of stuff into the HTML page
> > (rather
> > > than having stuff cached by the browser) makes for larger page sizes.
> > I'd
> > > much rather see a tool that would analyze the scripts and css that was
> > > included across lots of pages and recommending to the developer to make
> > 10
> > > CSS files or 20 script files into 1. But that's just me.
>
> > > > Cheers, Tim
>
> > > > On 08/05/2009 20:19, "marius d." <marius.dan...@gmail.com> wrote:
>
> > > > > A <lift:tail> built in snippet might me a good addition. I could
> > > > > probably allocate some time to noodle on it.
>
> > > > > Br's,
> > > > > Marius
>
> > > > > On May 8, 5:05 pm, KWright <kev.lee.wri...@googlemail.com> wrote:
> > > > >> It's becoming an established best practice that scripts should be
> > put
> > > > >> at the END of a page, where possible, in order to speed up download
> > > > >> times
>
> > > > >> Good article here:http://developer.yahoo.com/performance/rules.html
>
> > > > >> It would be nice if Lift could help encourage and support this by
> > > > >> allowing a <tail> (or <Lift:tail>?) element that could be merged in
> > > > >> the same fashion as the head element, perhaps also removing
> > > > >> duplicates, etc.
>
> > > > >> This element would then disappear and expose only its content when
> > the
> > > > >> page is ultimately sent to the browser.
>
> > > --
> > > Lift, the simply functional web frameworkhttp://liftweb.net
> > > Beginning Scalahttp://www.apress.com/book/view/1430219890
> > > Follow me:http://twitter.com/dpp
> > > Git some:http://github.com/dpp
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
> Follow me:http://twitter.com/dpp
> Git some:http://github.com/dpp
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@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
-~----------~----~----~----~------~----~------~--~---
