Thanks, @Zak -your reply has inspired me to (a) be patient (am doing fine w/ v5.1.22 of TW + Stroll, in fact) and (b) to try my hand a bit of scripting, per message just posted about my "Task Tracker scripting challenge <https://groups.google.com/u/1/g/tiddlywiki/c/1GLZFOgtHKQ>."
Moreover: following your link to the Stroll Help page <https://giffmex.org/stroll/stroll.html#Help%20%2F%20Acknowledgments>, i stumbled upon the TiddlyWiki toolmap <https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM> that @Dave Gifford has somehow managed to compile. I cannot imagine the work involved in compiling such a list, let alone keeping it current... So i now see how the bigger issue here of how to manage plugin dependencies is a hairy one indeed. Why: the Task Management category (the problem space i am currently exploring) alone has some 27 solutions linked (!), and if one were to install any number of these plugins -what the TW product architecture makes it so easy to do- i can well imagine how easy it would be to fall into the hellhole of cascading dependency failures. So: i am ever-more convinced now that my best survival strategy in these waters is to: (1) keep my complement of installed plugins to the absolute minimum of things i really can't live without; and (2) learn as much as i can about what's under the hood of those, in case i am ever having to patch up some leak on my own, should ever come to that (i sure hope not, because i've been down that road of my own making a few times in past, and i've got the scars to prove it!) /walt On Monday, December 28, 2020 at 8:26:56 PM UTC [email protected] wrote: > > So i gotta ask, am curious: which path have you taken? > I am currently living with it until it's fixed. > > > i do wish i had the coding chops to fix the problem > Don't think it would be too hard to track down the problem. Especially > because of the TiddlyWiki approach, i.e. it is only html + javascript. And > your browser already has some powerful debugging tools built in :) > > > how are these Plugin dependencies to be managed? > I suppose it comes down to the individual author(s) of a particular > plugin. > > Some plugins follow a more "traditional" flow. It has a public source code > repo (github/gitlab/etc.), issue tracker, etc. > > Other plugins don't have their code in a publicly accessible place (e.g. > private github repo/file system/google drive/etc.) and so there isn't > really a traditional issue tracker available. > > The Stroll support page [1] indicates it falls in the second category and > that simply posting issues to this group is good enough. > > [1]: https://giffmex.org/stroll/stroll.html#Help%20%2F%20Acknowledgments > > On Monday, December 28, 2020 at 6:50:07 PM UTC+2 ludwa6 wrote: > >> Thanks, @z... for validating the issue. >> >> So i gotta ask, am curious: which path have you taken? roll back to >> earlier version of TW, or live w/o Stroll until it's fixed? >> >> This raised for me a related issue -that is, more generally speaking: how >> are these Plugin dependencies to be managed? Not to apply any pressure to >> FOSS developers who have given so much to the commons already (esp @jeremy >> & @david gifford -you guys rock!), i do wish i had the coding chops to fix >> the problem, but alas... All i can do is post a message here in the gGroup >> and wait, until... What, i wonder? Maybe i'll be lucky and catch notice of >> a fix, if/when it flows thru this channel. >> >> Or better: is there an issue tracker somewhere, for these issues to be >> flagged and worked-on until they get solved? Am always happy to >> participate in this process as a tester, when it comes to software as >> important to me as TW + Stroll is! >> >> /walt >> >> On Monday, December 28, 2020 at 3:59:56 PM UTC [email protected] >> wrote: >> >>> @ludwa6 - same issue here so don't think you are missing anything. >>> >>> On Sunday, December 27, 2020 at 7:33:24 PM UTC+2 ludwa6 wrote: >>> >>>> As reported some weeks ago >>>> <https://groups.google.com/g/tiddlywiki/c/dZmp1gQivJI/m/CHKsGbMQAQAJ>, >>>> when i upgraded TW to version 5.1.23, certain features -both Close and >>>> Delete buttons in the edit screen- stopped working; this was purported to >>>> be related to some code in the Stroll plugin that would need to be >>>> updated. >>>> >>>> Meanwhile: my workflow being more dependent on Stroll than new features >>>> of TW v5.1.23, i've rolled my TW instance back to v5.1.22... Which remains >>>> my working version, as nothing seems to have changed in Stroll code, >>>> unless >>>> i am missing something. >>>> >>>> Now nearly a month on, i am wondering: Am i in fact missing something? >>>> I don't hear of other in this community having any such problems, so i >>>> wonder if this might in fact be a problem on my end. Am using >>>> TiddlyDesktop 0.0.13 (13) to manage my working index.html file, in case >>>> that matters. Would love to hear any ideas about how to get around this >>>> problem! >>>> >>> -- 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/2416eb68-9729-4893-ad73-5c3a1c463d78n%40googlegroups.com.
