Quote:
Originally Posted by democrite
As with pretty much all apps and **recommended** standard I'D guidelines provided by all operating systems or gui environmnts, such wouldn't be taking away from toolbars or window controls but merely making more or less everything important available on menus.
How is a beginner to know where to start? Does any other app developer say read the manual. Or if i forget what keyboard shortcuts are for what, i could merely look at the menu to see them plus with well organized menus, I could learn of any common actions and app functions i may not yet know. All apps use menus for a reason. Unfortunate you are not convinced or others complain of such. I am merely asking to adopt standard guidelines and convention.
|
- but I've more or less given up on the issue.
If you add Preferences to
The Menubar, you can remove everything from
The main toolbar*, but the Menubar is still a
click-me bar. On Windows (80%+ of users) a conventional menu bar can be driven from the keyboard via Alt+? sequences and arrow keys.
Whilst there's a user configurable keyboard shortcut for just about everything - most people have a limited to capacity to remember the ones that they don't use frequently.
Observation: I can
navigate my way around the arguably more complex Tag browser and detached Book Details panels with the keyboard but not the Toolbars. It might be useful to have settings for the Main Toolbar and Menubar similar to that provided for the Tag Browser - see
Allow the Tag browser to have keyboard focus in L&F->Tag Browser.
But that doesn't address the issues of discoverabilty and coherence - e.g. Create catalogue in the Conversion actions menu
Then there's Restart in Debug and Without Plugins in the Preferences actions, whilst vanilla Restart is a shag on a rock in a separate single action toolbar item.
* The same doesn't hold true if you add Preferences to The context menu for the books in the calibre library, it must be in the Main Toolbar or Menubar 
Quote:
Originally Posted by theducks
If in doubt: Press F1
That is basic help in most windows app, since forever (Win 3 and before) Many of my DOS app use it before Windows
|
The original F1 help was contextual - if I pressed F1 whilst the cursor was in the "Part number" control (widget in modern parlance) I would get the instructions for entering a Part number - usually via a link to a page in a local Compiled Help (CHM) document.
If I press F1 in calibre, my web browser springs to life showing the first page of the calibre User Manual, its search function is near useless so I download the PDF and discover its 430 pages long.
Chalk and cheese.
I project managed the development of several MC/LOB systems that specified the provision of context sensitive help. Coordinating the activities of the technical writers and the software engineers was 'a challenge'. This was a major factor in its demise - tooltips are an inferior substitute.
I assigned F1 to None soon after I installed calibre, also for other programs. At one stage I removed the F1 key, I might do it again next time that MS chatbot thing sticks its oar in.
BR