On Oct 20, 1:52 am, Eric Shulman <[email protected]> wrote: > Also, keep in mind that, athough it might seem that the unused > accessKeys are available to assigned to core commands, there are > currently some *plugins* that are already generating command links > with accessKey definitions (e.g.,http://www.TiddlyTools.com/#GotoPlugin, > which uses "G").
You've written a number of plugins, I see, so your point of view makes sense. One problem is that there aren't many accesskeys available. Another problem is that you have different pieces of code, unaware of each other, all trying to set accesskeys. What if two plugins decide to use the same key? Core/ plugin clashes are a symptom of the larger problem of code clashes, I'd say. Does the TiddlyWiki architecture say anything about the order of plugins loading? In other words, can the user assume that accesskey assignments will be read in a certain order? Or are we talking about uncharted design territory? A shadow tiddler with user customizations to keys might be the answer, if it can be parsed at the right time. Maybe after all plugins are loaded and before any command/ macro instances are created? As a user, I've never seen a good solution to the problem of finding and customizing plugin code. And the same problem applies to programs like Emacs, though the set of keys is much larger. My life is much easier when I know the entire set of commands I'm trying to assign keys to. As an author, you may not want your key taken away from you. I see the point which is why the solution has to be well-thought-out. Out of curiosity, do you think my patches so far can be implemented as plugins? -- 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 -~----------~----~----~----~------~----~------~--~---
