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
On Wednesday, January 1, 2020 at 11:14:12 PM UTC+11, PMario wrote:
>
> 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
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/92070314-3a62-442b-bb28-0205585355c4%40googlegroups.com.
