Just a ping for you to look at the code/design... On Thu, Sep 11, 2008 at 11:13 AM, Emily Crutcher <[EMAIL PROTECTED]> wrote:
> > >> Anyway, my main point is that someone just looking at the Wiki isn't going >> to know what it means so there should be additional text describing what >> those charts are -- sorry I wasn't more clear. >> > > Ah! Yes, that makes perfect sense, wiki has been updated. > >> >> >> >>> IE is the primary motivator for this set of changes, as it has the >>> slowest JS system and is most sensitive to memory constraints, so the IE >>> benchmarks are the ones I am focusing on. >>> >> >> That's fine, but it would be helpful to know that there isn't some issue >> on the other browsers. As an example, remember the pathological case of >> arrays on Safari when the index exceeds a certain threshold. >> > > Yep, I figured that would be the next phase, i.e. if this design was > accepted I would polish up the code (more javadocs etc, some extra tests), > do the full suite of benchmarks to check for weird stand-out cases then > submit for final review. As that will all take a bit of time, I don't want > to do it until I know the design has been stabilized though. > > > > >> >> >> -- >> John A. Tamplin >> Software Engineer (GWT), Google >> > > > > -- > "There are only 10 types of people in the world: Those who understand > binary, and those who don't" > -- "There are only 10 types of people in the world: Those who understand binary, and those who don't" --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
