Now to answer your points :

* class.js : after import, it will show up in “Compile Sources”. Move it to “Copy Bundle Resources” as you did with console.html. I had the same problem at one point and wrote about it : http://parmanoir.com/Where_in_build_phases_is_that_file_%3F

* iPhone.bridgeSupport : yep it’s bad :( iPhoneTest2 is written as proof of concept, therefore I manually copied definitions from /System/Library/Frameworks/Foundation.framework/Versions/C/Resources/BridgeSupport/Foundation.bridgesupport — need a better solution !

* NSArray and length : NSArray is bridged only one way now : its elements are accessible from Javascript with the array operator [] and using someNSArray.length should work. But the other way, sending a Javascript array to ObjC, is not yet supported. It’s in the works :)

Also in the works : making JSCocoa work on the iPhone. I don’t own an iPhone but had someone test and libffi does not work. There are people trying to make Python run on the iPhone http://www.telesphoreo.org/pipermail/iphone-python/2008-October/000206.html , I’ll see how that can work out in JSCocoa.