X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=XDdEXttkCR9gywaVYi/4N3n3n6sE0bY76GvrMOkgwZ0=; b=bAMn4yf7MXmWwNcxHhWUVLuk2paHx18WdOZQK1u4lcBYcHTycC0hcjpVFhngT2/FZq oE/4Ak6LwcW/ln3fWkkErvtPpG5JvPLrCMnjkyZrv3BnaelhY3vZXbZaCr0GJbgr7Tcn EaskaLxH5h7+6I8vUNkVGeiZz6zWmcdB8pPT8eD96t4uJR3mmqy/V8tAySgFAlFhUnAn SKS8s+L3GwXxKURv9OagEw22yUSqt1yj/pVQ0MvuKGayCc/fEeK0b0Ov+WFNmFsAxuHI HyGZKhCWLPSX0NYUtB7FJGaDf0NSCA2U+wOldDV38ADwai53Q+RNHSlHAXjhv4q3WSb4 ks0A== MIME-Version: 1.0 X-Received: by 10.28.48.131 with SMTP id w125mr37302745wmw.18.1451186771364; Sat, 26 Dec 2015 19:26:11 -0800 (PST) Date: Sat, 26 Dec 2015 18:26:11 -0900 Message-ID: Subject: [geda-user] how to collaborate on tool tips? From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a114242a402990f0527d8c0f3 Reply-To: geda-user AT delorie DOT com --001a114242a402990f0527d8c0f3 Content-Type: text/plain; charset=UTF-8 I'd like to see collaboration on tooltips. There are still lots of menu items I've never tried, and others I've never been able to get to work. They all probably have some users somewhere. Is there some way that home/bkerin/tooltip_fixes can be set to allow other commiters, or is it already the case that anyone is allowed to commit to non-master branches? A few thoughts on tips: * If it's not obvious from the name *what* it's for, the tip should say (e.g. Lock names, Only names). * If it's not obvious what needs to happen after the item which shows the tooltip is selected, the tooltip should say (e.g. for drawing polygons. Incidentally the existing tooltip isn't enough for me to successfully draw one). * If the associated action is entirely invisible or not easy to notice, the tooltip should probably indicate what the user should look for to verify operation The point of all of these is to make the GUI as self-describing as possible. Britton --001a114242a402990f0527d8c0f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'd like to see collaboration on t= ooltips.=C2=A0 There are still lots of menu items I've never tried, and= others I've never been able to get to work.=C2=A0 They all probably ha= ve some users somewhere.

Is = there some way that home/bkerin/tooltip_fixes can be set to allow other com= miters, or is it already the case that anyone is allowed to commit to non-m= aster branches?

A few though= ts on tips:

* If it's no= t obvious from the name *what* it's for, the tip should say (e.g. Lock = names, Only names).

* If it&= #39;s not obvious what needs to happen after the item which shows the toolt= ip is selected, the
=C2=A0 tooltip should say (e.g. fo= r drawing polygons.=C2=A0 Incidentally the existing tooltip isn't enoug= h for me
=C2=A0 to successfully draw one).

* If the associated action is entirely = invisible or not easy to notice, the tooltip should probably=C2=A0
=C2=A0 indicate what the user should look for to verify operat= ion

The point of all of thes= e is to make the GUI as self-describing as possible.
<= br>
Britton
--001a114242a402990f0527d8c0f3--