Joe, I first studied Cobol on in such a row format, but there is compelling reasons for clear code layout with any language.
Especially now that many compilers, interpreted and other systems eg html and CSS can mini-fy the source code to reduce its size for "deployment". tony On Thursday, January 10, 2019 at 11:24:42 PM UTC+11, Joe Armstrong wrote: > > I was brought up on punched cards (80 cols) of which 9 were rarely used - > so for me > lines longer than 71 characters are a big no no - and I do like the free > use of > white space and newlines to encourage readable formatting. > > 71 character code also prints well in books and papers. > > So writing filters become an art form (if I want them to be less than 71 > characters) :-) > > /Joe > > On Thursday, 10 January 2019 13:07:53 UTC+1, TonyM wrote: >> >> Always Learning yes, >> >> I understand where you are coming from. In its defence the whitespace >> means something in filters, so I think for documentation line feeds and >> leading spaces should be ignored in the filter, not continue to act as >> broken whitespace. >> >> >> - In the https://tiddlywiki.com/#Introduction%20to%20filter%20notation >> tiddler it starts with separating title with spaces. >> - In https://tiddlywiki.com/#Filter%20Expression where it says >> whitespaces it should just say space(s) >> - Also in https://tiddlywiki.com/#Filter%20Run and possibly elsewhere >> >> Perhaps you should request the documentation be fixed and non spaces get >> "eaten", including leading spaces on a line (so each item can be indented) >> >> Regards >> Tony >> >> >> On Thursday, January 10, 2019 at 9:59:37 PM UTC+11, Joe Armstrong wrote: >>> >>> >>> >>> 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/1369c326-813e-48da-ae46-66032ba5c3b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
