Hi Danielo Oops :-)
I needed to resort and edit a list of tiddlers -- something like the BJ's 'taglist' plugin, however in this case the list was a current list of tiddlers generated from a field rather than a tag. In this case editing by hand with an <$edit-text> widget was sufficient (no drag and drop needed), but first I needed to put the current list of tiddlers with a specific value for the field into a list, in order that it could be edited. I have been assuming that whatever I might need to do, others might need to do also -- so wrote a widget to set the value of a text-reference to the result of a filter expression. After writing the widget, I explored some other use cases. One possible use was to set the 'list' field of the '$:/Storylist' tiddler to the output of a filter expression -- this enables a user to overwrite the storylist with the output of any filter expression. >From there, I thought it might be useful to store snapshots of the storylist or results generated from filter expressions to an entry in a data tiddler -- these snapshots of the storylist can then be retrieved at some later point in time. However, here I came upon the issue that the special 'list' field uses space separated lists of tiddler titles, whereas the output of a filter expression is a comma separated list of titles, and wondered which format would be most useful. regards On Friday, June 20, 2014 12:04:28 PM UTC+2, Danielo Rodríguez wrote: > > You can continue calling me Danielo, as before. > > I'm familiar to your widgets. I'm just asking for this particular one ;) > > El viernes, 20 de junio de 2014 11:37:45 UTC+2, Matabele escribió: >> >> Hi Rodriguez >> >> What impresses me most about TW5 compared with TWC is what can be done >> with a vanilla TW5 'out-of-the-box'. However, I came upon a few limitations >> when developing applications and began writing simple widgets that can be >> stacked around a multi purpose button. This enables a user to build a >> button for the purpose without having to use javascript. >> >> Of necessity the stackable widgets must be simple to use and must also be >> able to be used stacked in succession using widget messages -- this places >> constraints upon the complexity of any individual widget. >> >> But most of all -- these are my first attempts with javascript :-) >> >> regards >> >> >> On Friday, June 20, 2014 11:21:44 AM UTC+2, Danielo Rodríguez wrote: >>> >>> Hi Matabele, >>> >>> What is your use case? Why a widget for such a simple task? And, why do >>> you need to use the list field? >>> >>>> >>>>> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
