How about putting an init timer on webtop and measuring it with your
change in place?
On 2009-04-30, at 22:15EDT, Max Carlson wrote:
Hmmm I can't seem to prove that makes any difference. This is
probably because we're not doing instantiation across multiple
frames - at least this shows no change in swf9:
<canvas>
<view id="foo">
<handler name="onconstruct">
for (var i = 0; 10000 > i; i++) {
new lz.view(this, {x:i, y:i, width:100, height: 100,
bgcolor: 'red'});
}
</handler>
</view>
<inittimer/>
</canvas>
Max Carlson wrote:
Change 20090430-maxcarlson-I by maxcarl...@bank on 2009-04-30
15:28:22 PDT
in /Users/maxcarlson/openlaszlo/trunk-clean
for http://svn.openlaszlo.org/openlaszlo/trunk
Summary: Raise framerate during app initialization
Bugs Fixed: LPP-8136 - Set the framerate to 1000 during app
initialization
Technical Reviewer: ptw
QA Reviewer: hminsky
Details: framerate setter caches any values during init, setting
the framerate to 1000. init() sets the framerate back to the
cached value. Move onafterinit event sending to the end of init()
so it can be used to turn profiling back on.
Tests: Startup should be slightly faster in DHTML and SWF9, where
the framerate can be set dynamically
Files:
M WEB-INF/lps/lfc/views/LaszloCanvas.lzs
Changeset:
http://svn.openlaszlo.org/openlaszlo/patches/20090430-maxcarlson-I.tar
--
Regards,
Max Carlson
OpenLaszlo.org
