My image idea......

It was a tremendous flop......It produced a file of immense
sizes......Totally non-bandwidth freindly......

I did my first test to see how feasible the whole idea would be before
firing up visual basic to automate it, but alas, I fell at the first
hurdle......

My idea was to 'hard-code' the image into the HTML rather than have it as an
imported item.....However, the resulting 50x50 pixel ized image produced a
file size of 195kb......Damn and damnation.....

So here was my idea......

Take a table......Split it up into say 50 cells by 50 cells.....make each of
these cells 1 pixel by 1 pixel and assign a unique background colour to each
of them......

Admittedly, this does create an image within a webpage without the need for
an image file, as this link proves
http://www.fatwasam.com/ideas/test.htm
But the resulting HTML file is ridiculously huge, and as the image
proportions get bigger, the file size will increase exponentially........

If it had been a viable solution, I had planned a simple application that
would import an image, resize it to the required output dimensions, then
scan it pixel by pixel, and assign the nearest web-safe pallete colour to
that pixel as the background in the corresponding table cell......It would
then output a simple text window containing the resulting code which could
be copied and pasted into a webpage......

Unfortunately, I hadn't anticipated the sheer volume of coding required to
make a 50x50 table, let alone a bigger one.....

Oh well.....Fame will have to wait for a better idea I guess......

"Fatwa Sam" <sam DeleteThis @samandjanet.fswolrd.co.uk> wrote in message
news:bdv77a$2ft$1@newsg1.svr.pol.co.uk...
 > It was a tremendous flop......It produced a file of immense
 > sizes......Totally non-bandwidth freindly......
 >
 > I did my first test to see how feasible the whole idea would be before
 > firing up visual basic to automate it, but alas, I fell at the first
 > hurdle......
 >
 > My idea was to 'hard-code' the image into the HTML rather than have it as
an
 > imported item.....However, the resulting 50x50 pixel ized image produced a
 > file size of 195kb......Damn and damnation.....
 >
 > So here was my idea......
 >
 > Take a table......Split it up into say 50 cells by 50 cells.....make each
of
 > these cells 1 pixel by 1 pixel and assign a unique background colour to
each
 > of them......
 >
 > Admittedly, this does create an image within a webpage without the need
for
 > an image file, as this link proves
<font color=purple> > <a style='text-decoration: underline;' href="http://www.fatwasam.com/ideas/test.htm</font" target="_blank">http://www.fatwasam.com/ideas/test.htm</font</a>>
 > But the resulting HTML file is ridiculously huge, and as the image
 > proportions get bigger, the file size will increase exponentially........
 >
 > If it had been a viable solution, I had planned a simple application that
 > would import an image, resize it to the required output dimensions, then
 > scan it pixel by pixel, and assign the nearest web-safe pallete colour to
 > that pixel as the background in the corresponding table cell......It would
 > then output a simple text window containing the resulting code which could
 > be copied and pasted into a webpage......
 >
 > Unfortunately, I hadn't anticipated the sheer volume of coding required to
 > make a 50x50 table, let alone a bigger one.....
 >
 > Oh well.....Fame will have to wait for a better idea I guess......

Great idea all the same.

I was thinking (loosely) along the same lines about PHPs image functions
(imagesetpixel() draws a pixel) which to my mind are very under-used.

The memory thing will get better with time, look how memory and
communications have advanced over the past few years.

Anyway, you're already famous, you've been on telly!
--
Charles Sweeney
<a style='text-decoration: underline;' href="http://www.CharlesSweeney.com" target="_blank">www.CharlesSweeney.com</a><!-- ~MESSAGE_AFTER~ -->