See also a similar discussion on Fields https://groups.google.com/forum/#!topic/tiddlywikidev/iw59ThjJID8
On Thursday, 10 August 2017 10:35:01 UTC+10, TonyM wrote: > > Can I please plead the members of this thread consider my post in the > other group that is related, although it may not be obviouse at first. > > [TW5] Desirable core additions > https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/AduZlD79FZo > > Regards > Tony > > On Monday, August 7, 2017 at 11:54:52 AM UTC+10, Mat wrote: >> >> I just want to bounce this thought to hear if it makes sense: >> >> The idea is about how to simplify the syntax, or at least make it easier >> to learn. >> >> >> A user currently has to learn the distinction between >> >> <<macrocall>> and {{transclusion}} >> >> The two are both simplified expressions for underlying widgets. >> >> And both are basically for text substitution! >> >> ...so just maybe they could both use the *same* format, i.e >> >> <<macrocall>> and <<transclusion>> >> >> >> Of course, this is problematic in that the parser would not know...: >> >> 1. ...if the argument is a macro title or a tiddler title >> 2. ...or even a <<macro with arguments>> or a <<title with spaces>> >> >> >> But, regarding the first: Comparable to how we accept tags as tiddler >> titles <http://mptw.tiddlyspot.com/#%5B%5BTagglyTagging%20History%5D%5D>, >> IMO it would be pretty natural to *not* make a distinction between macro >> titles and tiddler titles. In fact, tiddler philosophy applies pretty well >> also for macros... (Actually, if we pretend for a second that macros are >> *code >> functions*, I think tiddler philosophy and "function philosophy" are >> also pretty similar in objective -i.e to segregate and split out parts in >> code to make them manageable and reusable). >> >> Problem 2 above is of course just a matter of syntactic sugar. >> >> One could imagine this syntax >> >> ((mymacro(arguments list))) ...i.e a macrocall >> >> ((tiddlertitle())) or ((spaced tiddler title())) ...i.e transclusions >> >> >> The round parentheses is just one imaginable example. It does have the >> niceity that picks up on the existing macro def parentheses, i.e in \define >> mymacro*(*parameter list*)* >> >> The syntax is also interesting because it brings further similarity with >> macrocalls when we consider *transclusion with templates*! I.e >> >> ((tiddlertitle(template))) >> >> Again, tiddlers and macros are interchangeable. (Which btw, means core >> macros should probably be suffixed like core tiddlers to not have users >> accidentally overwrite them.) >> >> >> >> Thoughts? >> >> >> <:-) >> > -- 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 tiddlywikidev+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywikidev@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/d3feac2b-950a-4a48-9602-3467f35ad0e5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
