WikiLabs plugin update + New plugins

[PMario]

Hi folks,

I did update my plugins homepage at: https://wikilabs.github.io/, to be compatible with TW 5.1.23 ... Old plugins are _not_ broken, BUT they don't contain all the new features.

BACKUP FIRST !!!

The easiest way to update is, to drag-import the green button WikiLabs Plugin Configuration from the homepage to your local wiki.

Afterwards you can use the default TW "Plugin import" mechanism.

UPDATED plugins:

edit-tabs,

link-to-tabs ... Now support the Alt-<left> Alt-<right> navigation int the Advanced search panel

new-tiddler-from-search ... Supports the same keyboard navigation features as the default search dropdown. + Alt-left/right to switch tabs ..

NEW plugins:

click-effect ... If you click and realease the left mous-button a little CSS animation is activated. This should help me recording videos, and it should support everyone, which wants to explain TW

space-space-newline

 ... Add a new wikitext rule, that allows you to use common-mark compatible "hard linebreaks" in default wikitext

keyvalues  ... Contains a new filter operator, that was rejected from the core. It will help all of you who like to work with data-tiddlers

pragma-comment ... Allows utility authors to write comments in the "pragma areae" (If you don't know what this means, there is a high chance you don't need it!)

Detailed intros + some videos will follow soon!

ALL the other plugins do have updated license info. So you should have a closer look to the "history" tab, to see if you should update.

Have fun and a Happy New Year!

mario

PS - If you USE it: Support it :)

[Mat]

Great stuff Mario! Thanks for sharing!

<:-)

[TiddlyTweeter]

Great stuff! ...

FWIW ...

pragma-comment ... Allows utility authors to write comments in the "pragma areae" (If you don't know what this means, there is a high chance you don't need it!)

Great to see this released as its own plugin! Immensely useful for adding comments. Its very clever they never result in any HTML at all. It it does the needed job of allowing us to comment TW coding properly without any performance hit. Brilliant!

Best wishes

TT

[Joshua Fontany]

I like the click-effect plugin. Very good idea.

Best,
Joshua Fontany

[PMario]

On Monday, December 28, 2020 at 1:14:50 AM UTC+1 joshua....@gmail.com wrote:

I like the click-effect plugin. Very good idea.

Yea, I think the default "click animation" can help users to explain the UI to others and the "Element Pulse" can help to point out "paragraphs of text" or to help debugging (a little bit :)

-m

[Saq Imtiaz]

Neat idea Pmario. I would have used click-effect already today as I need to record a video (not TW related but in TW), but it turns out the plugin doesn't play well with some of my personal plugins.  

click-effect completely overwrites  $:/core/modules/utils/dom/popup.js , making it impossible to use with any plugins that extend the popup class.

Cheers,
Saq

[PMario]

On Monday, December 28, 2020 at 3:52:27 PM UTC+1 Saq Imtiaz wrote:

click-effect completely overwrites  $:/core/modules/utils/dom/popup.js , making it impossible to use with any plugins that extend the popup class.

Yea, that's a problem. ..  I think the core popup.js should provide a possibility to extend its function. .. The "element pulse" is already part of the core, but doesn't work. .. So we need a fix anyway. ...

Do you have an idea, how we could extend the core, to make it easier for plugin authors?

-mario

[Saq Imtiaz]

@pmario It isn't a perfect solution but it would significantly decrease the chances of clashes with other plugins if you tweak/extend popup.js instead of overwriting.

So you would need to overwrite handleEvent and add pulseElement and clickAnimation methods.

Something like:

/*\

title: $:/plugins/wikilabs/popup-tweaks.js

type: application/javascript

module-type: startup

\*/

var Popup = require("$:/core/modules/utils/dom/popup.js").Popup;

Popup.prototype.clickAnimation = function.....

I expect we are going to need to extend or refactor the popup mechanism for the new flexbox layout. So we can keep in mind at that time to add hooks where it might seem appropriate.

[David Gifford]

Hi Mario

I added the four new plugins to the Toolmap https://dynalist.io/d/zUP-nIWu2FFoXH-oM7L7d9DM

Space space to Writing and editing, font and paragraph manipulation

Click effect to Navigation misc

Pragma and keyvalues to Developer / advanced tools

If you would like them in different or additional categories, please let me know and I will move / add them.

[PMario]

Thank you David!

-m

[PMario]

Hi Saq,

I did update the click-effect plugin. Now I'm only changing the functions that are needed.

See: history tab of the plugin!

-mario

On Monday, December 28, 2020 at 3:52:27 PM UTC+1 Saq Imtiaz wrote:

[Saq Imtiaz]

Thank you @pmario !

I'll remember that I can use it next time I need to record a video :)

[PMario]

On Monday, January 4, 2021 at 9:45:21 PM UTC+1 Saq Imtiaz wrote:

Thank you @pmario !

I'll remember that I can use it next time I need to record a video :)

Which of your plugins, did cause a problem? .. I would be interested, if we can see a pattern, how to fix the problem in a generic way - for the core!

-m

[TW Tones]

Mario,

As usual I love your work. and you inspire new ideas;

Please forgive me from straying from the OT, but I raise this as it may be a simple extension of your "Click Effect".

I observed: Using the  "Click Effect"  Element pulse  is interesting because it helps identify the html element where clicked. It is a hint of what using the browser dev tools inspect does.

This makes me wonder if an alternate plugin could allow one to "click and copy html elements, or classes" specified in the html from the screen. 

• This would bring a simplified version of making use of the inspect tool tool to locate elements and the applicable classes on a TiddlyWiki
• Actually we may be able to launch an innerwiki that has such a plugin installed where the user can select any visible element from an empty wiki, and lookup its critical details needed when customising or designing
• This may work well in conjunction with the new layouts switch to assist in the development of new layouts, especially if a designer can quickly identify the appropriate class or html element, simply by clicking it.
• Such a tool could simultaneously copy the resulting value to both the clipboard and as the content of what we can call a clipboard tiddler. The system clipboard allows the result to be placed anywhere else on the device, but the  clipboard tiddler allows additional functionality to be designed to respond to the values, such as advanced search, links and references, documentation lookup etc... in the current Wiki.

behind this ideas are the following possible features;

• The idea that in cases where we may want to copy to the clipboard, we also copy to a clipboard tiddler is a powerful pattern, 
• Then regardless of what is in the system clipboard the wiki can paste from its own clipboard into tiddlers.
• This can be extended to list most recently used or a history of copy to clipboard actions, and pasted from a dropdown of prior values, 
  • both on tiddlers and in text.
• This would be a useful extension to the current copy to clipboard actions in the core, not to mention custom implementations.
• When we have wiki clipboard's such as a tag names, even fieldname/value pairs it is possible to have buttons or icons on which to drag and drop values to apply then to the displayed tiddler.

In closing the possibilities I described here could be used to help users and designers a like to make use of TiddlyWikis "self documenting" features given its open source, to learn about tiddlywiki itself.

Regards

'Tony

[Stobot]

@pmario - I know this is an old post, but I had a need again for the keyvalues plugin and it is a LIFE SAVER. One of my wikis is dedicated to a scrape of my companies ActiveDirectory and I had it setup one tiddler per user (all 26,000 of us) and searching was painful. I instead dumped the same information into a datatiddler with just the userid as the key, and a delimited string of fields as the value, and your keyvalues filter operator allows me to search *instantly*. It's such a game-changer for when you have these mini-databases for lookups and things. I hope these datatiddler enhancements continue to be supported in the future! Sent a small paypal tip :)

[PMario]

On Thursday, September 23, 2021 at 10:49:03 PM UTC+2 Stobot wrote:

@pmario - I know this is an old post, but I had a need again for the keyvalues plugin and it is a LIFE SAVER. One of my wikis is dedicated to a scrape of my companies ActiveDirectory and I had it setup one tiddler per user (all 26,000 of us) and searching was painful. I instead dumped the same information into a datatiddler with just the userid as the key, and a delimited string of fields as the value, and your keyvalues filter operator allows me to search *instantly*. It's such a game-changer for when you have these mini-databases for lookups and things. I hope these datatiddler enhancements continue to be supported in the future! Sent a small paypal tip :)

Thanks a lot!

Data tiddlers have advantages for some usecases and disadvantages for others. ... I think the concept of dadatiddlers can only be removed if we can create something, that is adequate but works with tiddlers. At the moment we don't have such a mechanism.

-mario

[TiddlyTweeter]

Stobot wrote:

@pmario - ... I had it setup one tiddler per user (all 26,000 of us) and searching was painful. I instead dumped the same information into a datatiddler with just the userid as the key, and a delimited string of fields as the value, and your keyvalues filter operator allows me to search *instantly*.

I just want to comment: that is extremely useful to know!

Tx, TT

[TiddlyTweeter]

PMario wrote ...

Data tiddlers have advantages for some usecases and disadvantages for others. ... I think the concept of dadatiddlers can only be removed if we can create something, that is adequate but works with tiddlers. At the moment we don't have such a mechanism.

Right. Your KEYVALUES PLUGIN looks most interesting. I flirted with it before but couldn't understand it well. 

I'm a bit of an idiot so need some hand-holding at first. 

Would it be okay to open a discussion thread about its practical use on Your GitHub?

Best, TT

[PMario]

On Friday, September 24, 2021 at 2:12:39 PM UTC+2 TiddlyTweeter wrote:

Would it be okay to open a discussion thread about its practical use on Your GitHub?

Sure. You can open a discussion: https://github.com/wikilabs/plugins/discussions

-mario