On Jan 24, 2010, at 5:39 PM, Jim Puls wrote: > On Jan 24, 2010, at 12:36 AM, Caio Chassot wrote: > >>> But we also have to test with *100* windows open. Because that's just what >>> happens whenever you allow multiple of something. (There are people who >>> have 20,000 tabs in my app. Whenever you allow multiples of something, >>> there will be people who go far, far beyond whatever you expected.) >> >> And because I hope we'll be VERY PITA about persisting state, this is >> trouble squared. Crazy users will just keep growing their workspace over >> sessions, and we'll have to make damn sure we can serialize and reload >> everything just as it was. > > How is serializing and reloading 100 windows any more difficult than > serializing and reloading just two?
Well, one thing is that if you want to reload 100 windows all awesome-stylie, you don't want the user to have to wait for it all to happen before they can get busy with their email. So you'd probably want to implement some kind process that reloaded the previous frontmost window first, and then went on to reload the rest of the windows without blocking the app. Whereas with only two windows you could probably just get away with loading them at launch time and making the user wait (hopefully shouldn't take long). So it's maybe a bit more work to do a great job of it. (But the same issue exists with reloading an arbitrary number of message windows, so Letters will have to deal with that at some point anyway.) _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
