aliasing, yeah. that's what I meant. But you think it looks ok that way? okay, I guess.
if the font rendering function supports anti-aliasing, I'd use it. However, the font itself may not support it all that well. If you're feeling a bit eager to learn some graphics stuff, you can search the net for an edge based anti-aliasing routine and attempt to convert it to php. Unless there's a function in the image's I'm not especially aware of. You can have the image functions resample the image, by making it 2 or more times larger, then resample it, which should partly anti-alias it down a bit.
when you say I can store the information in fields, .. well... so what's a field? ^^;
fields = columns. Seperated types, for example, a datetime or int for the date, a varchar for the text to actually drop
"form processor...." yeah, I knew I had to do something like that, I just don't know how to do any of it. How would I validate it?
we've had the pleasure of talking about form validation about 20,000 times. [devnet]+form +valid*[/devnet]
And when you say validate, you do mean to make sure I'm the only one submitting, etc, right?
That's a piece of it. The validation is more to verify that the data being submitted is correct for your set up.
How would I have a script create an image that isn't recreated when it's viewed? You mean like I could make a completely separate png that, after created, would function completely separate from the script?
you save the image to the server's file system, so you can just link to it normally. You may need to have the proper cache settings though. But it does save your server from having to render it for every page query. ... something to think about.