On Sunday 01 Jun 2008 3:45:03 am Felix Rabe wrote: > It just seems to make sense > to do away with the current layout on the screen and think about how a > completely (100%) scalable interface could look like and work. I got > very inspired by talks of Aza Raskin on this one, and plan to look into > his and Jeff Raskin's research work. You may also want to take a look at http://www.ted.com/index.php/talks/view/id/129. The processing power and memory required for responsive operation are available on desktop/notebook class machines today but not on handhelds. Video I/O also needs to transition from VESA to OpenGL.
> - Memory management. I hate the save button. Why do I have to tell a > computer that a string of bytes in one kind of memory should now move to > another kind of memory that can *also* handle a string of bytes, but > just possesses a different set of attributes? Because of the i/o speed technology gap between volatile memory (~2GB/s) and persistent memory (~3MB/s-30MB/s). As we get a computer to do more, our working set gets larger and persistent i/o takes longer. > Also, startup has a lot of room for improvement. For example, what about > saving a screenshot of the last things that were on my screen and show this > as soon as possible on startup? The user could just keep a TODO list > zoomed in at the end of a session, and within seconds (or less) could > see it again on starting up. You could accomplish this today, but it would be a big privacy hole. A working set may contain private data and should not be accessed without authentication. Imagine a bank transaction window in a startup splash screen! Subbu _______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
