On Oct 29, 11:33 pm, Eric Shulman <[email protected]> wrote: > It's important to avoid making assumptions about the expected layout > and usage of macros and commands.
You're right. That thought has been bothering me all along. Can you give more concrete examples of the layouts you mentioned, which I cut? Your point about context sensitivity is especially interesting because context sensitivity invalidates some of my assumptions. Also, I mentioned a list of things accesskeys can do: follow links, push buttons, and set focus. Do your example layouts require that shortcuts do things accesskeys can't? In other words, does the difficulty lie with associating accesskeys with the right HTML, or the abilities of accesskeys once associated? I can imagine useful things to do, which is not the same as a requirement. For example, it might be nice to move the mouse over a link to a tiddler, and use a keyboard or mouse command to act on the target, such as "close" or "open in edit mode". TiddlyWiki remains usable even without those features, though. > Regardless of any custom layout concerns, an even more fundamental > problem exists: access key handling is inconsistently-implemented on > different browsers. OK. So are you saying that an industrial-strength access-key based solution is impossible, or difficult, or something else? -- Derek --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en -~----------~----~----~----~------~----~------~--~---
