What do you think of this vap banner

[jexmex]

Some opinions on what you guys think of this banner:

http://jexlabs.com/michigan-vapor.info/dynaBanner/

Its my current project. I think the banner is a little generic, but at least I am making progress on the functionality.

Sorry if this is wrong thread.

 

[larktdl]

Looks alright, I like the juice counter. Cool.

 

[optsmk]

Very cool if you ask me.

 

[Wireguy]

I like the look and the juice bit. YOu might want to use a lighter color on the smaller print. My old eyes can't read them all.

 

[WingIt]

Yeh a little hard to read the dark blue on the black but other then that it looks pretty good.

 

[jruss91]

Looks good but the blue is to hard on the eyes and can't read well.

 

[jexmex]

Thanks for the comments guys (and gals(?)). I have functionality done I think, and just need to add a setup form, and upload it to a good location.

I am going to do some modifications to the banner, to make it easier to read, and i think I am going to add a small amount of vapor to it as well.

 

[jexmex]

Ok this is what I ended up with:

*SNIP* LOOK IN SIG!!!

All seems to be working fine. Any more comments are welcome.

 

[jexmex]

I dont know why, but my brain was not working right last night, I kept spelling vape as vap, lol.

 

[MercyPoetic]

What about adding a "money saved" counted thing on it? I love seeing how much people are saving by not smoking

But it looks awesome, go you!

 

[jexmex]

I have in the database a spot for cost per ml and cost per pack, which I could use to add the savings thing, I just did not want to clutter the banner, but I thought the same thing

 

[jexmex]

Ok all thats completed. If anybody wants one, just click on my sig banner

 

[Heracleum]

Nice work with the colours now, I've tested it with my actual details but it looks like I am forced to vape at least 1ml per day:
I vape actually 0.3ml per day, ok I know it's below the average, but since it's an average one should also want to put 1.5 and so on...
it gives me this error message:
"mL per day and smokes per day must be numbers only"
Now, since 0.3 is actually a valid number expression
I suggest you to use the is_numeric() function instead of just checking whether the submitted value has digits 0-9.

 

[jexmex]

heh, I am actually using a ctype_digit check, and its stored as whole numbers in the database, but maybe I should change it.

 

[jexmex]

Ok I fixed that. Should be ok for you to enter xx.xx now

 

[czycoot1318]

looks pretty cool

 

[czycoot1318]

looks pretty cool

 

[Heracleum]

I guess it would be more accurate.

Oh database you said, so one more suggestion (maybe later when a lot of people will use the sig) is to make a sort of "daily caching" of the image, I explain:
if you're planning to show only data that will not change in 24hrs, making a select on db for every single request the banner receives (and in forums like this one it's easy to get thousands) would be hard work for the db table, and in some way useless since it's not changing anything, the image displays always the same data for each id.
So I could suggest to render with GD functions the image-per-id only ONCE per day, and save it phisically in your webspace in a subfolder (you call the file "img$id.png"), so the following thousands of requests will be just redirected to the data contained in that cached png, instead of querying the db and gd-rendering the image every single time. Clean rudely all cached pngs in the subfolder every day (chronjob) or simply check the single img-id for date.
To output the data of existing image you can use fpassthru() function. Works pretty cool and saves db and script work!

Hope it's understandable!

 

[jexmex]

I guess it would be more accurate.

Oh database you said, so one more suggestion (maybe later when a lot of people will use the sig) is to make a sort of "daily caching" of the image, I explain:
if you're planning to show only data that will not change in 24hrs, making a select on db for every single request the banner receives (and in forums like this one it's easy to get thousands) would be hard work for the db table, and in some way useless since it's not changing anything, the image displays always the same data for each id.
So I could suggest to render with GD functions the image-per-id only ONCE per day, and save it phisically in your webspace in a subfolder (you call the file "img$id.png"), so the following thousands of requests will be just redirected to the data contained in that cached png, instead of querying the db and gd-rendering the image every single time. Clean rudely all cached pngs in the subfolder every day (chronjob) or simply check the single img-id for date.
To output the data of existing image you can use fpassthru() function. Works pretty cool and saves db and script work!

Hope it's understandable!

Actually I was figuring in the future caching it hourly (cause the calculations are based hourly). The other feature I am going to add is choosing your banner. Right now, this is a pre v1, and its kinda a side thing, so I am going to add those features in my free time in the near future.