Re: [SPAM] Re: Joins on capabilities that have passed through different membranes
Mike Stay <[email protected]> Sun, 17 Jan 2016 12:42:00 -0800
| Newsgroups | gmane.comp.capabilities.general |
|---|---|
| Message-ID | <CAAvuwX-RtxrAtjWv8y+NxwPkeHHPhnmw2FJ2diBSxOxzGFqefQ@mail.gmail.com> |
--===============3540986173637273711== Content-Type: multipart/alternative; boundary=001a11c3db7039b88705298dac80 --001a11c3db7039b88705298dac80 Content-Type: text/plain; charset=UTF-8 I have issues with their claim as well; in particular, I don't think they ever tried making it a coherent caps-based system, but tried to use some caps-like ideas in their existing system. On Fri, Jan 15, 2016 at 6:44 PM, Sandro Magi <[email protected]> wrote: > I'm skeptical of this UI claim. This behaviour is exactly what happens > when people open Word attachments directly from some e-mail clients. An > additional strip at the top says you're in read-only mode, and provides a > button to begin editing. This pattern has clearly existed for many years > already, and persists to this day, so it can't be so confusing as to be > unusable. > > Sandro > > On 05/01/2016 2:46 PM, Mike Stay wrote: > >> On Tue, Jan 5, 2016 at 11:14 AM, Alan Karp <[email protected]> wrote: >> >>> Marc Stiegler came up with a clever UI affordance to make all this clear. >>> If Ihab views the document with Kenton's capability, Ihab sees a ro view. >>> If Ihab opens it with his own, he sees a rw view. In either case, he see >>> the same document, which reduces any possible confusion. Since Ihab does >>> have write permission, his UI has an Edit button (actually a tab in >>> Stiegler's UI). >>> >> Google's UI researchers claimed to us that people would get a >> read-only view from somewhere and then be confused when they couldn't >> edit it, even when there was an edit button. People don't look for >> controls they don't expect to need. >> > > > _______________________________________________ > cap-talk mailing list > [email protected] > http://www.eros-os.org/mailman/listinfo/cap-talk > -- Mike Stay [email protected] --001a11c3db7039b88705298dac80 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he= lvetica,sans-serif">I have issues with their claim as well; in particular, = I don't think they ever tried making it a coherent caps-based system, b= ut tried to use some caps-like ideas in their existing system.</div></div><= div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Jan 15, 20= 16 at 6:44 PM, Sandro Magi <span dir=3D"ltr"><<a href=3D"mailto:smagi@hi= gherlogics.com" target=3D"_blank">[email protected]</a>></span> wro= te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-= left:1px #ccc solid;padding-left:1ex">I'm skeptical of this UI claim. T= his behaviour is exactly what happens when people open Word attachments dir= ectly from some e-mail clients. An additional strip at the top says you'= ;re in read-only mode, and provides a button to begin editing. This pattern= has clearly existed for many years already, and persists to this day, so i= t can't be so confusing as to be unusable.<span class=3D"HOEnZb"><font = color=3D"#888888"><br> <br> Sandro</font></span><span class=3D"im HOEnZb"><br> <br> On 05/01/2016 2:46 PM, Mike Stay wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> On Tue, Jan 5, 2016 at 11:14 AM, Alan Karp <<a href=3D"mailto:alanhkarp@= gmail.com" target=3D"_blank">[email protected]</a>> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Marc Stiegler came up with a clever UI affordance to make all this clear.<b= r> If Ihab views the document with Kenton's capability, Ihab sees a ro vie= w.<br> If Ihab opens it with his own, he sees a rw view.=C2=A0 In either case, he = see<br> the same document, which reduces any possible confusion.=C2=A0 Since Ihab d= oes<br> have write permission, his UI has an Edit button (actually a tab in<br> Stiegler's UI).<br> </blockquote> Google's UI researchers claimed to us that people would get a<br> read-only view from somewhere and then be confused when they couldn't<b= r> edit it, even when there was an edit button.=C2=A0 People don't look fo= r<br> controls they don't expect to need.<br> </blockquote> <br> <br></span><div class=3D"HOEnZb"><div class=3D"h5"> _______________________________________________<br> cap-talk mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">cap-talk@mai= l.eros-os.org</a><br> <a href=3D"http://www.eros-os.org/mailman/listinfo/cap-talk" rel=3D"norefer= rer" target=3D"_blank">http://www.eros-os.org/mailman/listinfo/cap-talk</a>= <br> </div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>= <div class=3D"gmail_signature">Mike Stay<br><a href=3D"mailto:[email protected]= om" target=3D"_blank">[email protected]</a></div> </div> --001a11c3db7039b88705298dac80-- --===============3540986173637273711== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ cap-talk mailing list [email protected] http://www.eros-os.org/mailman/listinfo/cap-talk --===============3540986173637273711==--