panamerica334 at gmx.net (panamerica334 at gmx.net) wrote: > i made up a new fproxy theme, that is, the aqua theme will be replaced by > this one.
It looks pretty good. Not as pretty as the aqua theme, but reasonably attractive given its sparseness. > "how to install?" I used the alternative: cd /usr/src/freenet/freenet # may differ for you cvs -z3 update -dP (Repeat previous step until sourceforge decides to work. Took about 10 tries for me.) cd src/freenet/node/http/templates unzip ~/templates.zip cd - ant clean && ant I noticed something that's relevant to the earlier discussion about caching images and so forth. It appears that even when mozilla caches the images, it doesn't *use* the cache if all the connections are used up. 20:48 greycat> Meanwhile, someone please explain THIS!: http://wooledge.org/~greg/cachedimages.png 20:48 greycat> that logo *still* isn't loaded 20:49 toad_> greycat: explain what? 20:49 greycat> why isn't the imge loaded? 20:49 greycat> that key has already DNFed about 8 times 20:49 toad_> the rabbit icon? 20:50 greycat> yes 20:50 toad_> what happens when you right click open in new tab? 20:50 greycat> the rabbit isn't DNF'ing. The CHK@ is DNF'ing, the rabbit is supposed to be there already. 20:50 silent-fish> hrm 20:50 greycat> This relates to the mailing list discussions where you swore up and down that all these images are supposed to be cached by the browser 20:50 silent-fish> that's the new error page that got sent to devl, right? 20:50 greycat> yes 20:51 toad_> but the rabbit isn't loadinbg 20:51 silent-fish> hrm 20:51 toad_> why isn't the rabbit loading? 20:51 greycat> and even with *one* image on it, it still sometimes fails to load the images immediately 20:51 silent-fish> shouldn't the image icon be a broken image if it wasn't there? 20:51 greycat> the rabbit loads very quickly once I stop TFE in the other tab 20:51 toad_> good point - it's still loading it? 20:51 toad_> greycat: DUHH! 20:52 toad_> so what are you complaining about? 20:52 greycat> why didn't mozilla load the image from its cache? why did it have to wait for a connection to the node to become available? 20:53 toad_> I don't know 20:53 toad_> have you disabled caching? 20:53 greycat> no 20:53 toad_> they SHOULD be cached... 20:53 toad_> we set an expiry date of 24 hours 20:53 greycat> now, the point is, multiply that by a hundred little tiny images for the normal error page 20:53 toad_> no, that's BS 20:53 toad_> the image will be cached 20:54 greycat> and yes, I checked the headers the other day, the image/png is sending out proper-looking headers 20:54 toad_> if the image is not cached, THAT is the problem 20:54 silent-fish> greycat: iirc, mozilla reads the cache in the network retrieve part of the code, not in the part which calls the network retreive part. the network retrieve part only gets called n times per host etc etc etc 20:54 toad_> silent-fish: hrmm 20:54 greycat> in other words, cache lookups block waiting on network lookups. Brilliant. -- Greg Wooledge | "Truth belongs to everybody." greg at wooledge.org | - The Red Hot Chili Peppers http://wooledge.org/~greg/ | -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20030515/1e15ebb0/attachment.pgp>
