Hi Ken Don't worry, we're not going to remove the togglelinks feature from TW Classic. For a long time we've been very careful about breaking backwards compatibility, and wouldn't do so lightly.
Best wishes Jeremy On Tue, Oct 29, 2013 at 6:45 PM, <[email protected]> wrote: > Thx Tobias for asking! … thx to User who requested this feature, and Thx > Jeremy > > I DO/HAVE use/d this feature Monthly for 5 Years! to aid debugging quirky > TW's I peruse. Actually _not_ _just_ TW related but I use a b r o a d (type > and version) range of browsers and OS'. > > There's been numerous instances (Use Case/s) where _Close_ or > _CloseOthers_ (in Toolbar::Commands) will _not_ function!? > So resort to _CloseAll_ button, or browser refresh ugh! …have to > re-navigate to relevant tiddlers, this is where _chkToggleLinks_ comes to > the rescue! > …OR the worst Use Case is opening each tiddler in Browser Tab!?!! > > I sympathize with your Dev perspective…of grief/hassle, maybe there are > alternate implementations of the _chkToggleLinks_ Feature Set. > > IF/when _chkToggleLinks_ is removed, Please, PLEASE document that FACT at > least in the Revision Tracking Comments w/in GitHub; at best documented > with TWc > > Has there been further Discussions on the _chkToggleLinks_ theme via other > communication media since Mar 2013? > > Has there been further Actions on the _chkToggleLinks_ theme within TWc > (v2.7.x, 2.8.x) &/or TW5 since Mar 2013? > > Thanks for your efforts People, Ken > > ---- some details of my platforms… > TW from V2.1.3 to 2.8.1 > OS: Mac OSX 10.1.5, 10.5.5, Windows NT, XP; iOS 3.1.2, 6.0.1 > browsers: Fx 1.0.7 - 14.0, Opera 12.15, Safari 3.2.1; MSIE …;iOS Safari > for 3.1.2, 6.0.1 > > > On Saturday, March 9, 2013 4:21:30 AM UTC-5, Jeremy Ruston wrote: > >> As far as I can remember, chkToggleLinks came in very early in >> TiddlyWiki's history - early in 2005, I think, before the TiddlyWiki Google >> Group was established. >> >> The feature was suggested by a user, I think with the goal of making it >> easier to "peek" at the target of a link by clicking once to open it and >> then clicking again to close it. I wasn't a huge fan of the idea, >> personally, but was happy to implement it under an option so that people >> could experiment with it. >> >> As time went on I found the feature more and more annoying, probably for >> much the same reasons as you're finding: it complicates one of TW's basic >> operations, and makes it harder to experiment with changes to related >> behaviour. It was one of the features that led to me creating the plugin >> mechanism, so that I didn't have to overload the core with every proposed >> modification or extension. >> >> Anyhow, I'm not sure whether it's worth taking the feature out at this >> point in TW's lifetime, what would you propose? >> >> Best wishes >> >> Jeremy >> >> On Fri, Mar 8, 2013 at 9:49 PM, Tobias Beer <[email protected]> wrote: >> >>> Hi everyone, especially Jeremy / Eric... >>> >>> Can anyone explain the reason behind chkToggleLinks? >>> >>> All I can think of is that it means confusion and... trouble... like the >>> trouble I had when watching the behaviour in trying to understand what is >>> happening and how I can prevent it in my plugin. >>> >>> From my perspective, I would appreciate if this were removed from the >>> core and only implemented if some functionality actually needed it, but not >>> as a global setting for all tiddlyLinks. >>> >>> Single page mode would be a lot more meaningful than this, especially if >>> you desire to use TW as a website. >>> >>> Cheers, Tobias. >>> >>> >> -- >> Jeremy Ruston >> mailto:[email protected] >> >> -- Jeremy Ruston mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
