Ah, that makes sense now..... when i did my site's iPhone version I time and time again was reading of the limits of Safari's cache..... i didn't fight or test those limits and my site loads/runs just fine (http://iphone.team-integra.net)... (any huge delays in loading a page are from me on the server site loading remote images, resizing them to a phone-friendly size, and replacing the HTML with this new image)
There was talk at the jQuery conference in September of the code getting a mobile-specific offshoot..... i'm not sure if that was planned on the 1.4 release (which is now just 30 mins away) On Jan 14, 10:30 am, Peter Edwards <p...@bjorsq.net> wrote: > The cache limit is for individual files, so you get jquery down under 25K, > then use CSS sprites (with images less than 25K) for backgrounds - the total > cache size is 475K (a maximum of 19 components can be cached). Gzipping > doesn't count (the limit applies to uncompressed code) but minifying is a > must I guess. > > On Thu, Jan 14, 2010 at 3:13 PM, MorningZ <morni...@gmail.com> wrote: > > but what would be the point? > > > say you got jQuery down to 10k in size.... that leaves 15k left for > > images and HTML and etc, it's just going to hit that limit and purge > > the cache anyways..... but just a few requests sooner > > > keep with the minified and gzipped version to keep the data sent > > across the connection to a minimum... ripping apart the library > > just doesn't seem worth the payoff, which isn't much anyways.... > > > On Jan 14, 10:08 am, Peter Edwards <p...@bjorsq.net> wrote: > > > There is an interesting article about optimising YUI for Safari/iPhone > > at: > > > >http://tinyurl.com/y97karc > > > (there was a problem with the blog's database connection, so this links > > to a > > > cached version) > > > > With the following in it: > > > > Some examples of the kinds of things an iPhone-specific site doesn’t > > need: > > > > > * Keyboard navigation and shortcuts: The iPhone doesn’t have arrow > > keys > > > > and the keyboard only appears when a text input element has focus, so > > code > > > > that handles keyboard shortcuts and navigation events is unnecessary. > > > > * Hover states and mouse movement handlers: Since the iPhone is a > > > > touchscreen device, there’s no mouse cursor and thus no way for the > > user to > > > > hover over an element. Mobile Safari fires the mousemove and mouseover > > > > events just before the mousedown, mouseup, and click events, and it > > fires > > > > the mouseout event when an element loses focus. > > > > * Context menus: There’s no way to right-click or control-click on > > the > > > > iPhone, so the contextmenu event cannot be triggered. > > > > * Text selection and clipboard handlers: Sadly, the iPhone does not > > > > provide clipboard functionality or a way to select text in an input > > element, > > > > so these handlers are useless. > > > > I guess you could edit all these parts out of the uncompressed jQuery > > > source, and then compress it all down to less than 25Kb - has anyone done > > > this? > > > > On Thu, Jan 14, 2010 at 9:30 AM, m-schmidt <micha_schm...@me.com> wrote: > > > > Hi, > > > > > the iPhone has a cache limit of 25KB, so the jquery script file will > > > > never be cached. Is it possible to split the jquery file in 5-10 > > > > smaller files for the iPhone? > > > > > thanks, > > > > Micha
