Yeah, Tony, I think that does make sense. In most scripting language that use html markup within them, like PHP, the < a > tag is not really parsed on a display page. It's just a string literal, and PHP just looks inside that string to see if it finds some PHP code. If it does, it replaces that code wherever it is found with whatever literal is the calculated result.
It appears that TW doesn't do it this way, (which is fine, I'm the one who has to get used to it) in that it seems to parse the < a > tag and it's attributes through it's own engine. From that perspective it makes perfect sense. You know, I wouldn't expect so much of TW if you guys hadn't made it so good! There are so many things about it where it is doing such smart stuff so easily. On Monday, June 29, 2020 at 10:21:07 AM UTC-4, TW Tones wrote: > > David > > One way to look at what you tried to do is give a parameter that was made > of two parameters a literal and transclusion in the same parameter in this > case href. > > Imagin if you were tiddlywiki yourself. First you need to evaluate what > the result of the transclusion is then remember it was part of the same > value as the literal string then combine them and only then use the result > as the value to pass as a parameter. > > This is like Eisenstein sitting on a light beam. When you think about it > from tiddlywikis's perspective you are asking too much. You should take > responcibility for concatenation of disparit values before you ask > tiddlywiki to consider it a single value for a parameter. > > Does this make sense to you? > > 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3b70cc16-99c4-4b3d-8269-a31fd94ede57o%40googlegroups.com.
