Yes, Steve, I’m nodding.
(7)i18n. The whole&& ampersand thing took me a bit to wrap my head around when I first started GUI, and yes, it has it’s place as a standard or common, In my opinion.
Tho it still confuses me (and them also) sometimes why almost every new developer has such a confusion as to the special syntax and to why it is that way… Maybe the age old genie knows why if I had a wish left… Haha
At first my code started looking like “The MenuItem”,
then it was consistently “The MenuItem” with & randomly placed in it,
then on third conversion it became _(“&%s”) The Whole fist Letter thing…,
Now I am faced with many multiple items that have the save Letter to start with,
which brings me to the conclusion, that while simplicity and accessibility is important, I and others cannot sometimes justify spending quite a bit of time
sorting out all the ampersand possabilities, when if the fact is that if you cannot use a mouse for the said app, then the users or handicapped users experience is sometimes hindered.
@Note: What we need is AlphabetSOUP generators for this!
Ex: Use Win32(on Win) to snake a open programs menu into memory and then iterate over the top level menuitems(which are most important ones) and then generate for example a help file, or in my suggestion,
_(%s\t%s) %(&AlphaBETSoup, KeyboardShortcut) or similar.
With blender, I can at least say they go to extreme lengths, to provide 3-mouse button functionality for those that only have 1-2 mouse button functionality, which means if you where 1-handed, then you would almost have severe problems just working with the app.
This kind of attention to detail is sometimes what is missed in todays applications. Let-alone voice functionalities(such as microsoft sam)(which is amusing by the way, as is the dragon you must feed along the way, that can’t type worth a claw)
(4)(6) The most important apps I know uses this: Esc-Esc-Esc. Or has tweakability to do so. It Quits everything or does what you want it to. 1 button three times, not Alt + button, which would be two buttons or more pressed.
I have spent a good portion deal of my life talking and dealing with disabled vets, some of which are blind, and some which have only one hand, amongs’t other problems. When I carried a phone, I recall I would often be working on a vehicle, rolling around on the ground, only to find out that what bugged me was the fact that 911 kept calling me back because this STUPID phone keppt pocket calling with 999(God-Thankfully the car didn’t fall of the jack ATM I answered it) (Nowadays we have key-lock, which is another issue I won’t get into now.).
Accomodating their suggestions first, in my mind, would almost trump anything/one else’s ui complaints to me. And the first suggestion is an alternative solution, or so I hear… What that may be is not for me to decide as long as I provide the option for those in need. When they need it, they just usually ask how, then understand that someone has took great lengths for such few individuals, at times, and may ask for a small bit of help setting up, but them are happy with being able to use an application that otherwise would be unusable to them.
So as far as accessibility is concerned, it should be at the top of the help file explaining why at the very least. (4) Or (F1(1-key) / Esc-Esc-Esc) to get to that point.
As far as (3), that is a fine line inbetween perfection and users pref and vise versa.
(2) Almost Impossible in today’s world.
(5) With blender everyone is a developer.
(1) common…thinks meh. Most users are resistant to change.
Tho… Apple 1-button mouse(NO-WAY!), but on a old-school apple shaped green-transparent-plastic monitor,YEA COOL for nostalgia… playing non the less Oregon Trail(sorry if you died of the plague right before getting there), It wasn’t my fault.
(0) Still no answer on the wx.Menu wx.EVT_MENU_HIGHLIGHT funct question. Oh well, try, try again… Nice chattting tho…
···
On Friday, November 22, 2013 12:00:12 AM UTC-6, Gadget Steve wrote:
On 21/11/13 23:07, James Scholes wrote:
Tim Roberts wrote:
One of the biggest challenges I have on a day to day basis is trying to
persuade some developers of the following:
-
You need to try your stuff on the minimal hardware, and the most
common scenario,
-
Consistency is always appreciated,
-
Just because you can doesn’t mean you should,
-
Where the user has to start most of the time should be the most
obvious place to start,
-
The developer is not usually the main user,
-
Consider the your users might not have your background & abilities,
-
Internationalisation, screen readers, keyboard short-cuts, etc., are
almost always worth considering, cost next to no effort and pay dividends.
Would you believe that 3 days ago I had to explain to a developer with
many years experience what those funny ampersands were doing scattered
through menu names that he kept seeing in UI code.
Gadget/Steve