Spudinski

@Cronus: Formulate a URL/I with the PHP API for IE users then, like desktop apps.

Facebook's API supports IE, must be something on his side. I'd like to know as well though.

Well, my workstation(Ubuntu 10.10 x64) was Firefox 10.x until today when I decided that it's just too damn slow. Also, Firefox keeps forgetting my pinned tabs so it's a hassle as well.

The hell, I shut his game down last month for using pirated MCC. Supports it either way.

They're from Australia... so who knows. Anyway, yes, that is bad. Databases aren't meant for "static" data, even less when it's version'd.

Use: $.each(yourVar, function(key, val) { // something });   And PS.: Sending requests within a loop is a VERY bad idea. Also, as a hint, parses is empty... and.... i should have local scope.

Nice work, thank you.

Three letters: F12 Though, I'd suggest optimizing that CSS first: it would make life a lot easier.

@sniko: Yes, your calculations are wrong. The number zero(0) is one bit, it doesn't use 11 bytes(or 11x8=88bits) of memory. But let me make it clear: A memory size of 11 integers could be allocated by that specific column. Also MySQL does not ZEROFILL by default, you have to specify it. Ps. I lol'd on: pow(10) is used when converting bits to digits, aka, printable max(). In which case the answer would have been: 11^10 = 25937424601

I mean event onLoad versus parallel execution.

This. Is correct. But I don't know why one would want to execute Javascript when the DOM isn't fully loaded. Mind shedding light on the subject for me?

I think you missed some very "basic" logic with what you proposed. 1. Creating tables to free up resources and space. Ok, fine. But if you knew MySQL, you'd know a table is much larger on the disk than a column in another table. Also to go along with that: Yes, it is better to create different tables for relevant data, but not if it's only going to hold a few - mostly static - records. 2. Use mysql_free_result. Uhmm..... You said you want to optimize queries to use LESS memory right? I think you misread the term paging(query caching w/ MySQL) somewhere. Another part you missed while reading the PHP docs: I highly doubt that even a 200 column row will yield a large enough set of data to even acquire the status of a "slow query".

L33t SkillZ. http://www.justfuckinggoogleit.com/search.pl?query=create+a+3D+game+engine

Post CSS and HTML. Eric Meyer's Reset script is a very limited edition of other common reset stylesheets.

You shouldn't, you should preferably create a desktop application for FPS. Was just my thoughts with FPS in-browser.

You do not need to use Unity3D or C# for that matter to create a in-browser FPS. I've seen tons of 3D games developed with Javascript, and some other things like WebGL or similar. Ref: http://media.tojicode.com/q3bsp/?tesselate=2 Even though it's very old, '06, it's still valid: http://www.benjoffe.com/code/demos/canvascape/

Anyway... Chrome is my choice. It's the fastest, and the most powerful when it comes to Javascript. It's got a V8, haha. Mainly, yes the blazing fast Javascript engine. But also, WebKit. Something I can not afford to be without, ever. My backup is lynx though. Does everything I want it to.

Post an add mentioning your looking from someone who "has something from EC Council". Real whitehats will know what it is.

You are correct for most parts. It should alert undefined, and depending from browser it may or may not throw an exception. There is a twist in this tale though, since FF 3.5 Javascripts are loaded in the background and then returned to and executed. There may be other newer browsers I don't know about, but for most part, as said, you are correct.

Firstly, THANK YOU for thinking off people who have problems with imageshack. The template looks quite good, the only think I would suggest is a change of typography for the navigation links and the body text. Other than that, well done.

[ATTACH=CONFIG]301[/ATTACH] -tooshort-

I think you meant PHP installations, and that's only because the ini directive is set to have it disabled. Since PHP 5.4 it's always enabled.

Ugh. The only reason why you would want to put includes and the bottom is if you know it's a slow query. If it's local it doesn't make any sense as Javascript is executed after the DOM is loaded. Though, there are very valid and good reasons why stylesheets come before script includes. As far as I'm concerned, use the head tag. Otherwise, if you want to load/change it at runtime use Javascript.

No one ever said scrollbars have to be ugly. Webkit offers scrollable content, see http://css-tricks.com/custom-scrollbars-in-webkit/.

There are template systems for each's need. Lightweight: RainTPL Popular/Buzzy: Smarty Performance: Twig RaintTPL for instance, is a bit over 1k lines and one file, and offers syntax comparable to Twig/Smary, and also has a changeache