The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
To keep this thread for URLs only, I'm gonna start another for comments so please post your web addresses only in this one. :-) Hopefully we'll be able to point out mistakes and maybe some of the more experienced of the forum users can offer some guidance as to where sites are going wrong.
I'll start:
www.drinkfosters.co.uk
thats my image testing, pretty sure you'll agree :D
but obviously if your saving your GIFs at 8 colours and thats ok with you then it's all good.
> also, what happens if someone with a bigger resolution than you supply
> turns up? e.g. a Turbonutteer with a ridiculous resolution, does it go
> to the highest one you have? or does it go "how can you see
> anything with that silly resolution, go away" ?
the javascript says >= 1280 (greater than or equal to)
> I always think splash pages are a bit pointless, although I'm not
> averse to using them (www.tacitdesign.co.uk, www.carlpix.co.uk) The
> below stops you having to press a button.
but at the expense of having to use JavaScript redirects. What happens if the user has JavaScript disabled? They'll be stuck on that page...
> Storing the res in a cookie seems wrong too, as it's always available
> to you with screen.width and screen.height. Cookies can be turned
> off. the DOM can't. Using cookies to control presentation seems well
> dodgy to me.
Resolution is only available to you if they have a language enabled which can access it - e.g. JavaScript.
OK then, if you don't want to use cookies to do it, try this:
Use a splash page with JavaScript to work out which page to redirect them to. Use the following script as well: "".
Perhaps the most effective way of doing this would be to have 5 page templates, each optimised for a different resolution. But then, rather than having to create the whole site for each template, just load dynamic content into it.
This is assuming you want sites optimised for different resolutions. How many sites actually do this? By far the best way would be to simply design a site that scales well in all resolutions - from 800*600+
Storing the res in a cookie seems wrong too, as it's always available to you with screen.width and screen.height. Cookies can be turned off. the DOM can't. Using cookies to control presentation seems well dodgy to me.
All said I agree Fog. One site serves all (www.tenuouslinks.co.uk)
Sorry 'bout the shameless site promotion
Mele
Nimco wrote:
> Mele wrote:
>
>
> A better way would be to use a splash page and then set the res in a
> cookie for future pages to use this means you dont have to use a
> redirect.
200x200px
got it down to
2.98Kb in JPEG
13Kb in GIF
just made my nonsense comment from those results :)
> 8 colours?
> if your using Fireworks, try:
>
> type: JPEG
> Sharpen Colour Edge: Tick.
> you'll be able to get the save quality down to about 70-75 before
> loosing any quality and it should save at around 3Kb if not lower,
> especially if your only using 8 colours! :D
You can't set the number of colours in a JPEG! I just tried that with the same screenshot as before:
JPEG Quality 70: 8.64KB
JPEG Quality 60: 7.35KB
JPEG Quality 50: 5.65KB
JPEG Quality 40: 4.67KB
JPEG Quality 30: 2.30KB
GIF 128 Colours: 11.02KB
GIF 64 Colours: 9.12KB
GIF 32 Colours: 7.33KB
GIF 16 Colours: 5.38KB
GIF 8 Colours: 3.82KB (I don't have a clue why its smaller than before!)
The advantage of the JPEG is that it shows all the colours even at Quality 30. However, the GIF will give you a smaller file with crisper edges.
It basically depends what you want - just experiment.
if your using Fireworks, try:
type: JPEG
Sharpen Colour Edge: Tick.
you'll be able to get the save quality down to about 70-75 before loosing any quality and it should save at around 3Kb if not lower, especially if your only using 8 colours! :D