[QUOTE]Originally posted by bira
yeah, it occured to me that some people here may not have .html parsed as php in their httpd.conf :o (which, I must admit, I'm surprised you don't)

btw, you might want to edit the instructions.txt file in the zip in the attachment, to edit the .html into .php (to make it working) - in case people cut and paste from the instructions file instead of from this thread. Will prevent them from coming here and complaining it doesn't work and that they did exactly what the instructions say - the instructions are kinda wrong now. :)

server load doesn't change one bit. If you parse html via php and there's not a single php code in that file, it will just output it and that's that. There's nothing to execute, hence there's no memory needed.

But I get your point about shared servers. In any event, it was a complete oversight on my part and I apologise. What surprises me is that none of you got a javascript error! getting a <?php echo $something ?> smack in the middle of a javascript should have immediately triggered a javascript syntax error for you. You probably have the option to disable all errors in your browser selected. Shame on you, developers! :D

[QUOTE]Originally posted by KuraFire
btw, you might want to edit the instructions.txt file in the zip in the attachment, to edit the .html into .php (to make it working) - in case people cut and paste from the instructions file instead of from this thread. Will prevent them from coming here and complaining it doesn't work and that they did exactly what the instructions say - the instructions are kinda wrong now. :)

At a friend's request, I also made an alternative colours chart:

http://www.atlasf1.com/personal/bira...ive-picker.gif

If you rather use this one than the original one included in the hack (first post), then please:

1) download the attached file, rename it to picker.php

2) in style.php, instead of:

use:

I think I'm gonna try something, instead of hard-coding all the colors in the file, maybe you can use a FOR loop to go through all the colors... or maybe half the colors. :)

FireFly, what for? :confused:

[QUOTE]Originally posted by bira
yeah, it occured to me that some people here may not have .html parsed as php in their httpd.conf :o (which, I must admit, I'm surprised you don't)

[QUOTE]Originally posted by bira
server load doesn't change one bit. If you parse html via php and there's not a single php code in that file, it will just output it and that's that. There's nothing to execute, hence there's no memory needed.

But I get your point about shared servers. In any event, it was a complete oversight on my part and I apologise. What surprises me is that none of you got a javascript error! getting a <?php echo $something ?> smack in the middle of a javascript should have immediately triggered a javascript syntax error for you. You probably have the option to disable all errors in your browser selected. Shame on you, developers! :D

Well, if you have <?php echo $something ?> in the middle of the javascript, and that page is not parsed through php, then the <?...?> code is outputted to the client as part of the php/script source. And, when java parses the script, it stubles on illegal elements that shouldn't be there.


[QUOTE]Originally posted by KuraFire

Also: if a server parses .html files, doesn't that mean it Checks the entire .html file to see if there is any PHP code inside it, anywhere? I do believe that that's what parsing is.. :/

And if so, it _would_ provide some extra server loads if you do it on a large scale (100+ visits per minute) - all those php, asp, etc. tutorials speak about how you shouldn't use .php extensions if you don't have any PHP in the file, to prevent needless server parsing, i.e. server loads.