Possible feature - the list pill

[TonyM]

Folks,

Since lists and list fields are such an important element in TiddlyWiki I think we should consider making them first class, as a result I suggest the development of the following;

• A "List Pill", like the tag pill but it operates on named fields (default list)
• A way to copy/drag the list or a list field on any tiddler to another tiddler ideally via the List pill.
• The ability to reorder items on any list field using the list pill.
• The ability to add extensions to the list pill as we currently can on tag pills

Examples would be 

• taking a snapshot of the StoryList list field and keep it for later
• A list pill for the tags field to drag and drop all tags on one tidler to another

I will work on this in time but I thought I would raise it as a useful extension to standard features 

• What are your thoughts?
• Could you do this?
• What other features would extend this further?
• How can we make it easy for naive user?

Regards

Tony

[PMario]

Hi Tony,

I did create the foundation for stuff like this with the Story Editor Proposal.

I did create some PRs for the core already, that I will make stuff as you describe easier for plugin authors.

 - Add isUnique to qualify - and - update core tabs macro
 - Action create tiddler improved

 - Add new parameters to fields-widget and fields-operator.

So it would be nice if you could support those PRs. More stuff will follow, once file-backups plugin is out.

-mario

[PMario]

Hi,

My plan is, to integrate the "draggable list" implementation for every field in the tiddler "info" section for every tiddler.

So it should contain just enough UI to work as a primitive "Story Editor". Authors should be able to improve the "basic functions", if they combine them in new ways.

-m

[Mat]

TonyM wrote:

• A "List Pill", like the tag pill but it operates on named fields (default list)

As I replied to a similar proposal of yours, I've posted on gh about what could perhaps be called a "Filter Pill". IMO this is more general than a "List Pill" (because you can do this "[{myfield}]" and more) and it is in line with the many other widgets and macros that center around a filter.

<:-)

[TonyM]

Mario & Mat,

I was aware of your work Mario on this and this idea is in part to complement it. I see your progress but not so clear on how to leverage it beyond the story.

My point here is a specific ui element following the existing tag pill. Unlike in Mat's proposal My idea was focused on "list fields" not just "list" but any field that contains a list, this would include the story list but more. I thoroughly support a filtered list pill, and can see how I may make what I need from that.

I have a large tiddlywiki running in a production environment, I used a consistent naming standard for anyname-list fields typically these lists fields contain a set of titles of existing tiddlers for example a list of Offices, a list of people both of these are what I call objects and have their own instances, object-type, view and edit templates etc... Then tiddlers can contain lists of these "objects", using a "field definition" method it would be trivial to identify fields used as lists and provide immediate access to list field handling.

A quick mock up (the labels default but can be changed)

The next step would be to permit the addition of items to the list from the pill.

Regards

Tony

[TonyM]

Mario,

My plan is, to integrate the "draggable list" implementation for every field in the tiddler "info" section for every tiddler.

Good idea but can we allow the methods used to achieve this be accessible in wikitext if desired?

And as discussed elsewhere any field nominated as a list field.

Regards

Tony