Packaging tiddlers with tag alternative

[TonyM]

Folks

A nice way to package a set of tiddler is by tagging them, displaying them as a tag pill and the pill can be dragged and dropped on another wiki. Whilst this is helpful it does mean that the destination wiki now has the tag defined and it in someways starts to pollute the tags.

Is there a way to make a draggable pill based on say a filter based on a field name or value rather than tags?

It would be nice if such a pill would also list the tiddlers as the tag pill dropdown does.

We could call it a filter pill with a drag icon to make it clear.

Regards
Tony

[Mat]

Agree. I've previously made this proposal, please see if you support it.

<:-)

[TonyM]

Supported with reply!

[PMario]

Hi Tony,

I think the "Story plugin" which I'm working on at the moment could be setup that way. At the moment there isn't any code, that works with the "drag-handler". ... but it should be doable.

The main reason, why I didn't publish anything yet is "family business" these days: ;)

-m

[Mat]

PMario wrote:

I think the "Story plugin" which I'm working on at the moment could be setup that way. 

Ah, that's a great insight that there's a conceptual overlap. Stories could really be treated like "objects". 

<:-)

[PMario]

As I found out, stories also have a big overlap with bundles too. ...

-m

[TonyM]

Mario,

I do not fully follow your stories work but it sounds like progress. As I understand stories are really custom populated list fields. Can this go a little more generic if we address the utilisation of list fields if not also by another name, and given such a list could also be "any filter" I see an extension of list handling into both stories, packages, bundles and draggable pills would be a good underlying set of features to many solutions.

Just some thoughts

Tony

[PMario]

On Wednesday, January 1, 2020 at 3:43:40 AM UTC+1, TonyM wrote:

...

I do not fully follow your stories work but it sounds like progress. As I understand stories are really custom populated list fields.

The "initial" story-configuration for users will be list-LIKE-fields. ... The (solved) problem here is a nice draggable "list view" instead of a 1 line text field.

The "complex" type should be a mix of tiddler titles with filters. ... The problem here is drag&drop-filter sorting at the moment. (causes the delay)

 

Can this go a little more generic if we address the utilisation of list fields if not also by another name,

As above I want to use list-like fields. They should work with a generic UI. My first test is a dynamic "table-view". I'm not really happy with it atm. But at least it does something.

 

and given such a list could also be "any filter"

Absolutely right. The content of the list-field is a valid filter "subset". eg: a b c works as list and as filter

So a filter-like field could contain something like this:

 -[enlist{!!list}] or

 -[enlist{!!otherField}sortby{!!test}]] [[a a]]

 -[enlist{xx!!otherField}sortby{xx!!test}]] [[a a]insertbefore[b]]

For the 3rd example let's assume otherField is: a b c  and  test is: c b a  

If you copy this to advanced-search filter tab at tiddlywiki.com you can see crazy stuff going on. It's extremely flexible and powerful.

With constructions like example 3 it will be possible, that users can modify the filtered sort order, without modifying the initial filter or list. So it's possible to update the underlying configuration by an author, without destroying user settings and vice versa.

With an "evaluate filter and copy to xxx-field" it should be possible to "snapshot" the output of the filter to a draggable list. ... UI needs to be improved here.

 

I see an extension of list handling into both stories, packages, bundles and draggable pills would be a good underlying set of features to many solutions.

Yea, it seems to be possible, to replace some usecases of the bundler plugin with the story workflow. This will allow me to add new stuff to the bundler, which I didn't want to add at the moment, because it would create confusion.

----------------

All of the above may seem super complicated, but it turns out, the user workflow is incredibly simple.

have fun!

mario

[TonyM]

Mario,

Thanks for the response, that sounds robust and systematic, making this quite reusable in different contexts. Perhaps the project should be promoted more around lists than stories  although they are a critical list. eg: "List fields and story..."

All of the above may seem super complicated, but it turns out, the user workflow is incredibly simple.

This to me is an indicator its a good fit to TiddlyWikis philosophy.

Can we make such look like a tag bill aqnd drop down and per the OT?

Thanks

Tony