On Tue, Jul 5, 2011 at 5:30 AM, rantingrick <rantingr...@gmail.com> wrote: > Umm, if you want to see where things are "going" you should learn > about the inner workings of chrome which actually spawns a new process > for every tab created; which has the benefit of avoiding application > lock up when one page decides to crash.
There is still one application. There's a single process which is the master; all the other processes die if the master dies. Chrome's isolation of tab-groups has nothing to do with the GUI design question of whether one top-level window is allowed to do more than one thing, which you claimed it should not. >> How would you write a >> user-friendly picker that can cope with myriad instances of >> everything? > > psst: it's called a notebook in GUI jargon. Again, study up on chrome > internals. No, that would not be what it would be called. Also, a notebook is a very specific widget, and it's not quite identical to Chrome's or Firefox's tabbed browsing setup; but again, that has nothing to do with the case. The question is one of UI design. ChrisA -- http://mail.python.org/mailman/listinfo/python-list
