I thought about doing that, but I don't want to overload people's browsers and memory by loading a metric-ton of images. From my experience, most browsers don't handle dynamically generated pages' memory or garbage collection too well. I come from an embedded point-of-view, so my definition of "handles memory well" may be a bit biased...
But apparently removing DOM elements from pages doesn't exactly free memory either, so it may not matter anyway... I'll play with it some more... -Chad On Wed, Feb 4, 2009 at 12:15 PM, Peter Denton <[email protected]> wrote: > looks great Jazzy! Works extremely well too. > > I was thinking one thing, once it got to 200 pics, it could throw up a "page > 2" tab, and so on. > > On Wed, Feb 4, 2009 at 9:09 AM, Chad Etzel <[email protected]> wrote: >> >> Thanks to those who provided feedback.. I have made some small tweaks: >> >> - Added an "Auto-Scroll" option which will scroll the page as new pics >> come in. >> - Added "Auto-Resume after 200 pics" option for >> continuous/screen-saver type mode. >> - Made Pause/Resume links mutually-exclusive with >> Fade-In-Fade-Out-Technology (tm) >> - Automatically display the tweets of new pics in the status bar >> unless you are already hovering over a pic. >> >> http://tweetgrid.com/twitpicgrid >> >> -Chad >> >> On Wed, Feb 4, 2009 at 5:04 AM, Stuart <[email protected]> wrote: >> > >> > 2009/2/4 Chad Etzel <[email protected]>: >> >> With many thanks to Noah Everett (the TwitPic dude) for allowing the >> >> use of TwitPic thumbnails, I have created TwitPicGrid at >> >> http://tweetgrid.com/twitpicgrid as a mashup. Watch new TwitPics >> >> arrive as they are tweeted, or search for keywords associated with the >> >> pics. Could be interesting for real-time pics of events (Apple >> >> keynote, Inaguration (oops, too late), Steven Fry being trapped in an >> >> elevator, etc...), or just searching for everyone's cat. >> >> >> >> Feedback welcome. Enjoy. >> > >> > Very nice. >> > >> > Small suggestion... it would be easier to watch if new images appeared >> > at the top-left rather than at the end - no scrolling needed. >> > >> > One other minor UI note... why show both stop and resume links at the >> > same time? Surely they're mutually exclusive. >> > >> > -Stuart >> > >> > -- >> > http://stut.net/ >> > > >
