On Feb 27, 6:22 am, Marcelo <marcelo...@hotmail.com> wrote:
> Berry,
>
> That quite amazing, even in IE! :-)
> But as someone mentioned in another thread, while I think your code is
> very elegant and highly efficient, I am unable to read it.
>
> --
> Marcelo -http://maps.forum.nu
> --
Thanks Marcelo,
I had to do a lot of code consolidation to prevent IE from displaying
"Script running slowly ... " messages. IE counts the number of
statements executed rather than measuring elapsed time to reduce the
dependency on CPU chip speed.
http://support.microsoft.com/kb/175500
One very ugly loop with one 750 character statement is simply to
eliminate another "set-up" loop. It is deeply embedded in other loops
which means it receives heavy traffic. Also, some browsers perform
"just in time" compilation of the JavaScript. Individual complex
statements are well suited for optimization. Compilers can remove
redundant sub-expressions but have difficulty analyzing flow. The
overhead may not be worth the effort.
Another reason is to prevent the "cut & paste" crowd from stealing my
code. I am happy to have people use it but not butcher it.
Some of the optimization techniques are proprietary. I am exploring
my licensing options.
Berry
For what it is worth, 1000 polys of four vertices each are not a good
demonstration of the optimization capabilities. Point reduction
cannot be performed on just four vertices. The intermediate cache is
worthless. It requires big polys to do serious optimization.
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" group.
To post to this group, send email to google-maps-js-api...@googlegroups.com.
To unsubscribe from this group, send email to
google-maps-js-api-v3+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-maps-js-api-v3?hl=en.
