Great work. When there is more than one plugin for a similar requirement and that requirement is pervasive amongst tiddlywiki users, and if that requirment is not a size hog then surly it should be in the core ?
This type of solution combined with the ability to add remove tags according to filtered results would be great in the core. By core I assume it can be accessed by other means than just the list command. Tags and there manipulation setting/un-setting if exist/not exist, toggling, cycling etc.. could also be developed to generalise tiddlywiki in a similar way to it's other current open and flexible features (Java/HTML/Wiki Words links and references). Tags should be able to be manipulated with standard set logic. I will endeavor to define clearly and post. Thanks Jon TonyM If you have not found an easy way to do it with TiddlyWiki, you have missed something. www.tiddlywiki.com On Tue, Dec 8, 2009 at 06:08, jnthnlstr <[email protected]> wrote: > Wow. Interesting way to approach the code. Nice work. > > I guess with this filtering thing it's not really a core requirement, > hence why there are 3+ different plugins to solve the problem. What > amount of filtering syntax would you say is definitely a core > requirement? I can't see that the (int) (float) etc. stuff is > particularly common. > > > J. > > > On Dec 7, 1:35 pm, rakugo <[email protected]> wrote: > > I've been getting increasingly frustrated with the TiddlyWiki > > filtering in the core in that it > > * does not support and filtering > > * does not support fields > > > > I wanted a filtering mechanism that worked with DefaultTiddlers in > > particularly I was finding with my TiddlyWeb development I > > increasingly wanted to use the filter [server.bag[bagname]] in my > > DefaultTiddlers tiddler where server.bag is a custom field TiddlyWeb > > defines. > > > > I was determined to use a syntax such as [tag[tag1]tag[tag2]] for and > > filters as it seemed to quite readable syntax. > > > > Turns out it was a bit of a can of worms, I noticed lots of people > > have tried to solve this problem and problems faced involved code > > size, code readability and from a development point of view issues > > with defining regular expressions to match the different syntaxes. > > > > I've been a bit alternative and have created a version of the function > > without any use of regular expressions, instead resorting to defining > > a finite state automata (http://en.wikipedia.org/wiki/Finite- > > state_machine) and in doing so proved my self wrong when I said > > several years ago at uni that "this will never be useful to me". > > > > It's pretty powerful and I imagine it is very useful in conjunction > > with the list macro already in the core, so I imagine it's not just me > > that will find this useful. > > > > I've constructed a TiddlyWiki which explores the possibilities of what > > you can do with this plugin: > http://www.jonrobson.me.uk/development/AdvancedFilterTiddlersPlugin/i... > > > > Word of warning - the plugin overrides the sortTiddlers and > > filterTiddlers core functions. > > Hope someone else finds this useful. > > Jon > > -- > > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<tiddlywiki%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/tiddlywiki?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
