On 11 Apr 2006, at 00:25, Glynn Foster wrote: > Ouch. That does seem a bit of a mess - not sure the current proposal > really cleans that up very much though eg. 'Computer' vs 'File System' > in the Nautilus Go menu. Still a big +1 from me for going with the > community and trying to fix up the inconsistency there, rather than > trying something new.
Well, part of the "trying something new" in the spec was actually to see if I could figure out something that might be a sane solution for the community, but I ended up getting bogged down a bit somewhere inbetween. Judging by the comments in my blog, though, there are already bugs open about it that nobody seems very interested in fixing, so we might have to do the work here ourselves and try and get it back upstream anyway. > Also amusing to see the 'Alt+Home' keyboard > shortcut for 'Documents' menu item ;) Yeah, bit of a last minute idea that one, not sure if it's very helpful :) >> You do have a point, at-poke would be more useful if it also worked >> with Java apps, and I don't think it does (not sure off-hand though), >> so I'm inclined to remove it too. The a11y team wanted it on the >> menus last time though, so that's possibly a discussion for them and >> marketing to sort out between them. > > Hrm, I'd almost argue that it shouldn't even be installed by default - > it's demo-ware, was a 30 minute hack to demonstrate a11y at a > conference. Hmm, I think people like Wipro used it fairly heavily to test the accessibility of our apps too, to find things like missing accessible descriptions. I removed it from the spec before it "froze" anyway though, so marketing and the a11y folks can worry about whether we bother shipping it at all. > >>>>> o Save Screenshot/Take Screenshot - is the string change *really* >>>>> that crucial? >>>> >>>> No, but it matches the title of the dialog that appears when you >>>> select >>>> it, which is needlessly different at the moment. Would want to >>>> try and >>>> get this change back to the community, certainly (as we would with >>>> almost all of the proposed tooltip changes, probably-- most of the >>>> current community ones are dire). >>> >>> I'd be happy with an upstream change - let's get it changed there >>> before >>> we change our menus, IMHO. >> >> Fine by me. > > Cool - I assume you've logged a bug on this? I'd be happy to create a > quick patch for you if needed. I haven't yet... was going to file a whole batch at once based on things that had come up while I was doing the spec, but haven't had a chance yet. Think that'll have to be a post-Easter exercise now. > Do you have any formal process of changing things in the spec? I'm not > so sure we should be freezing the entire spec - it doesn't feel ready, > although other sections are pretty solid. Yeah, there's certainly a fair pile of things that still need thinking about. I don't think there's a formal process in place yet wrt incorporating user feedback, but for any changes I/we can justify ourselves before we get too far down the line, hopefully it should just be a case of getting a nod from the c-team. Cheeri, Calum. -- CALUM BENSON, Usability Engineer Sun Microsystems Ireland mailto:calum.benson at sun.com Java Desktop System Team http://blogs.sun.com/calum +353 1 819 9771 Any opinions are personal and not necessarily those of Sun Microsystems
