[10:58]<simono> hannesw, talking about spidermonkey performance: http://deanm.github.com/pre3d/monster.html google blog tells me this 3d software renderer runs smooth in v8 :) [10:59]<hannesw> nice [11:01]<hannesw> simono: how does it run in spidermonkey? [11:01]<hannesw> (can't test right now) [11:29]<simono> runs bad [11:31]<simono> seconds per frame [11:59]<hannesw> ok, but: 1) this doesn't benchmark the js engine but the whole browser, and 2) v8 sucks because it doesn't support js 1.7+ [12:08]<simono> okay, it runs in the browser and uses canvas - so not a pure js performance test [12:15]<simono> still impressive :) [13:52]<simono> for a unit test i would like to replace a collection on a hopobject with a mockup (grid.items = fakeItems). when i call list() on the mockup, helma starts complaining. no easy way around this i guess [13:52]<simono> something like dontWatchThisProperty(grid.items) [14:18]<hannesw> helma ng should now be fully compatible with the serverjs securable modules proposal. [14:18]<hannesw> http://github.com/hns/helma-ng/commit/dca49178a31c009fd61c6c4878d9da716edbb6da [14:25]<simono> nice [14:26]<simono> include('helma/file') == include('/helma/file') :) or is the latter just wrong? [14:27]<simono> got it [15:26]<hannesw> '/helma/file' will be interpreted as absolute path (in a file system sence) [15:27]<hannesw> that's an admission to making resources outside the helma/app dir available [15:27]<hannesw> i really implemented that to get to shared jar files, not modules... [15:29]<simono> i understand [15:31]<hannesw> the resource loading framework in the back is the same for scripts, skins, jar files, etc [15:32]<simono> hm, i stumbled across findResource() and figured [16:00]<hannesw> just replaced this: [16:00]<hannesw> http://github.com/hns/helma-ng/blob/d7bcdc3afd98cd821e9965b824aa8962c686b6f1/src/org/helma/web/HelmaServlet.java [16:00]<hannesw> with that: [16:01]<hannesw> http://github.com/hns/helma-ng/commit/9acfcaa39954cf8684ac22353cb438cc735e27d8 [16:01]<hannesw> but in the end, we'll use the best of both worlds :-) [16:01]<hannesw> java for thread management, timeouts etc, and js for implementation details. [16:04]<simono> interesting to see in code what i have as a diagram :) [16:07]<simono> in modules you have webapp.js and webapp-folder. that seems strange [18:18]<jirkap> hello. What is so special about the User prototype? I mean - are there any restrictions or I can actually use it as any other prototype? Like var x = new User() - is there anything wrong with that (according to docs)? [18:31]<jirkap> oh, I think I found the answer :) app.registerUser explains it all