Finally, it's a real plugin: see the new demo page <http://maximilian-schillinger.de/tw5-keyboard-navigation-plugin.html>.
I followed this HowTo <https://tiddlywiki.com/dev/#Developing%20plugins%20using%20Node.js%20and%20GitHub>. It recommends adding a README file when creating the GitHub repo. But now this *README.md* is also included in the plugin (contents tab). 1. How can I exclude it (same for *tw5-keyboard-navigation.html* and *tw5-keyboard-navigation-plugin.html*)? 2. Why is does *navigation.css* include an absolute path? ( *navigation.js* does not!) Best regards, Max Am Sonntag, 3. November 2019 10:46:34 UTC+1 schrieb MaxGyver: > > @Jeremy: Thanks for your answer! I was looking for a quick and easy > solution at first, but on the long run I want to create a real plugin that > can be imported by drag and drop. > > @Tony: I have never tried the sticky title option before. This looks like > a good feature. And your proposal sounds absolutely reasonable. > > > Am Sonntag, 3. November 2019 07:10:52 UTC+1 schrieb TonyM: >> >> Max >> >> On your question >> >> - If you scroll down half a tiddler, which one should be edited when you >> press "e"!? >> >> If you turn on sticky titles in theme tweets and ensure the e operates >> the tiddlers who's sticky title is visible I think would be the best. Ie >> the top in the view screen even if, you are looking at the bottom of it. >> Ideally it could detect if sticky titles was in use or not and if not edit >> the tiddler who's title is visible at the top. >> >> Regards >> Tony >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d1700842-184a-44eb-84f8-aba7e6c9b6c3%40googlegroups.com.
