On Thursday, May 14, 2020 at 3:44:05 PM UTC-5, Faldrian wrote: > > Hi! > > Thanks for the Stroll-Plugin, I like the backlinking and sometimes the > two-river view can come in handy. It's a good assortment of enhancements to > the standard TW. :) >
*Thanks! * > > I have some comments... and I hope I'm not intruding into a community that > has a modus operandi that I don't get and show bad behaviour. > > *You did fine! You will find people are pretty friendly here, but also straightfoward when errors need correcting.* > > 1. There is a caption missing on > "$:/.giffmex/ViewToolbar/new-note-here". The button content only has the > image, but no text. You can check when you use the "more" menu - the "new > tiddler here" is the only one without text. > > *I think I already fixed this with the help of Gerrit Beine earlier in this thread. Perhaps you downloaded your copy before I changed that. Check it at the Stroll site. More menu shows text.* > > 1. I was also missing the animation, but you offered a fix earlier in > the thread. My feeling would be, that this animation duration change > should > not be part of the plugin, as it changes TWs behaviour to your liking and > is not really needed for the plugin to work. > > *Good point, I will change it back to the annoying default behavior. **:-) You are right that it is not an essential part of Stroll, and I would like to keep this as lean and as similar to an out of the box Tiddlywiki as possible.* > > 1. Just a meta thing - and I don't want to impose something! - I would > suggest using some online code repository for this. Benefits would be: > 1. I had to scroll along the whole thread to see if somebody > already reported the missing button text. On an online repository > (github/bitbucket/...) I could have looked in the bug tracker tab and > read > the titles. :) > 2. There is a bug tracker, so different improvements / bug reports > could be handled indepenently, instead in a long thread chronologically > 3. People could make pull requests and the system would deal with > merging the code by itself. You would still be in control what ends up > in > the code, but you would not have to worry about diff files and people > could > suggest improvements and deliver the code for it and you would only > have to > check and merge into the development version. > 4. A list of Changes / a history of the code would be available, > this may be interesting and helpful to see what changes were made > > *I agree, that * *1) adding it to GitHub and also* *2) packaging the bits that are not parts of other plugins into a proper Stroll plugin * *would be good steps for Stroll. I am quite willing for someone who is a longstanding member of the Google Group to adopt Stroll and host it on GitHub, and I could redirect from my site to that one. Seriously, I am not possessive of it, and I am ready to set this project aside and get back to focusing on using Stroll for my own needs. * * FYI I don't know how to package plugins, and I find GitHub hard to understand, so I don't have the patience for those two additional learning curves. My many interests are elsewhere. I am not a coder, just someone with years of experience with TiddlyWiki who cobbles stuff together and hopes it works. And I have lots of generous ad knowledgeable friends here who have helped me figure things out when I got stuck. I * *just wanted to see how much of Roam functionality I could create in a TiddlyWiki, and I got fairly close on the basic functionality. Of course Roam has a lot more going for it than I can replicate, and TiddlyWiki has a lot that Roam does not. I don't see them as rivals, but similar tools for different needs / markets.* *Blessings!* thanks again, I will follow the future changes and am looking forward how > this develops. :) > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/fb031a33-8147-4f43-8402-fc09700d107e%40googlegroups.com.
