What came to mind for me was how the palettes in the Pauric example had to remain resident INSIDE the browser window. That is a pretty strong restriction, IMHO.
To me the biggest issue with "the browser" is the wrapper. Why? To have an addressing system? a sandbox? There are other ways to do this, no? Marimba had a good example of managing JavaApplets and Adobe had a previous example that flopped for other reasons. What's interesting is that people haven't even questions the #1 element of the browser, even more prominent and central than the back button or bookmarks. That is (wait for it) ... the addressbar. Are URLs really necessary any more? If they are, why the heck are they and if you are going to blow up the architecture of the browser, shouldn't also blow up some of the core legacy antiquated elements that make up the very core of http? -- dave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=32535 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
