On Thursday, 10 January 2019 11:15:25 UTC+1, TonyM wrote: > > Joe, > > Newlines in filters do not work, however if you passed fieldname="value" > pairs to the create new tiddler action you could use newlines. That is do > not use the triple curly braces. You may need more set widgets, but it > would read better. > > Alternatively you could define the filter in a (global) macro and place it > in the create tiddler using the subfilter operator, after all you may want > to use it more than once. > > You could even move set widgets to macros if they define reusable > variables, this would provide a tiddler of sharable settings and much > simpler new tiddler code. > > That should give you multiple avenues to write readable self documenting > code. >
It's the formatting of the code in printed media that concerns me. I would actually like to see how these different ways of making a control would look on paper - right now I think a lot of the code is pretty difficult to read - a bit of color coding and indentation would help a lot to see the structure. > I assume you are wrapping this in a trigger widget such as a button? > Yes I'm just trying to re-implement the comment plugin in as clear a way as possible (to my eye) I'm just for the moment disregarding css and layout issues. It's just part of learning. Regards > Tony > > -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/af79c8ce-eabf-4d3e-bb6d-18ddfc0ae825%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
