Presenting: attention - offhandedly push content into other tids

[Mat]

The TWaddler proudly presents...

 attention

As you author a tiddler, this lets you offhandedly "push" content into other tiddlers by merely writing @tiddlername Some stuff here /@ ...so you don't have to go to those other tiddlers.

It is related to #hashtagging and @namealerts. And for those who remember the CherryPicker concept, "attention" is a limited case of this based on a viewtemplate. (Apropos CherryPicker, I hope to eventually make further devs to implement some of the wider ideas mentioned there. Anyone feel free to give it his own shots, of course.)

Big thanks to Tobias Beer for his tobibeer/split filter operators which greatly simplifies manipulating strings.

@tobibeer
question; How should I actually best package "attention" into a plugin so that the user also gets your plugin? Is it only appropriate to add a "Dependencies" note and link to the original source? Ideally I don't want to force the user to go to other places so if it is ethical and possible to someone bake tobibeer/split into my plugin...?

@everyone
Since I have you attention (heh!) I'll also mention that Alain Dutech's Edit Comp-Text concept should fit perfectly here. It lets you select a tiddler title in edit mode, instead of writing it which risks misspellings etc.

Further, the attention concept shoudl be useful for a future social system like TWederation to use like hashtags and alerts. For example, people could alert you (@Bob) and it shows up in your notifications area or on your twCard... for anyone who knows what that is...

[Tobias Beer]

Hi Mat,

 

Big thanks to Tobias Beer for his tobibeer/split filter operators which greatly simplifies manipulating strings.

Thx, appreciated. ;-)

 

@tobibeer
question; How should I actually best package "attention" into a plugin so that the user also gets your plugin? Is it only appropriate to add a "Dependencies" note and link to the original source? Ideally I don't want to force the user to go to other places so if it is ethical and possible to someone bake tobibeer/split into my plugin...?

I think the dependecy bit and a pointer to where to get it makes the most sense.

I would not blame you for your one-stop-shop approach but comes with problems. For one, you would want to make sure to provide others with the latest version... however, you'd want to make sure that that's still compatible in any way.

Baking another plugin like tobibeer/split into your plugin certainly does not sound like a great idea, though. I wouldn't even know what happens there. If you had a kind of Tiddly-Application and something like tobibeer/split was a hard dependency, then of course, ship it with your application... but attention seems to be in plugin land, so, as for me, dependency is the way to go.

Best wishes,

Tobias.

[Thomas Elmiger]

Hi Mat,

When I look at your tab "Notes" I would expect the word "Wow!" to appear on $:/core – but the rest of the tab is there too … is this a bug?

Maybe you are interested in my Extract Macro, which is heavily inspired by your Cherrypicker and could perhaps be used in similar ways. See http://tid.li/tw5/hacks.html#Extract%20Macro (lacks one or two revisions concerning code and docs).

All the best!
Thomas

[Mat]

Thomas Elmiger wrote:

When I look at your tab "Notes" I would expect the word "Wow!" to appear on $:/core – but the rest of the tab is there too … is this a bug?

Thanx. Corrected. No bug, just didn't end properly with "/@".

Maybe you are interested in my Extract Macro, which is heavily inspired by your Cherrypicker and could perhaps be used in similar ways. See http://tid.li/tw5/hacks.html#Extract%20Macro (lacks one or two revisions concerning code and docs).

Aha, interesting! Will look into this futher. Just maybe you've solved some of the stuff I see a need for. Thanks!

<:-)

[Mat]

@Tobias, yeah I'll probably land on dependency with pointer. A bit frustrating for seemingly primitive components like basic filter operators.

Thanks

<:-)