Tony! I think the problem is backward compatibility. Cheers Mohammad
On Friday, February 22, 2019 at 1:31:59 AM UTC+3:30, TonyM wrote: > > Mohammad, > > I understand but if you used $name in Wikify my rule above would be > broken, and it would be impossible to tell when to use it and when not to. > The only way out would be to change all widget parameters to begin with a $ > > This issue can only be solved by understanding why the $ is used and in > which cases, which is after all a small list and noted in the documentation. > > Regards > Tony > > > On Friday, February 22, 2019 at 8:43:52 AM UTC+11, Mohammad wrote: >> >> Hello Tony! >> Thank you for clarification. I understood the reason! >> But for simplicity I asked why not use $ also for wikify widget >> attributes! I mean this way it much more simpler to learn. >> and it is kind of semantic naming rule. >> >> By the way I respect developer opinion! >> >> I share my own experience, I have to keep tiddlywiki.com open all the >> time, because when coding (specially a little complex one) I mixed these >> things and >> I had cases, it took me hours to debug the code. >> >> Cheers >> Mohammad >> >> On Friday, February 22, 2019 at 1:02:23 AM UTC+3:30, TonyM wrote: >>> >>> Mohammad, >>> >>> I may be confusing to you now but with respect it is not. >>> >>> In wikify you will never need to provide another parameter other than >>> defined in the the wikify macro >>> AttributeDescription >>> name The name of the variable to assign >>> text The text to parse and render >>> type The ContentType <https://tiddlywiki.com/#ContentType> of the text >>> (defaults to text/vnd.tiddlywiki) >>> mode The parse mode: block (the default) or inline >>> output Keyword indicating the desired output type, defaulting to text (see >>> below) >>> However in The $macrocall widget you may very well want to define a >>> field called "name" and give it a value bvecaue you may have a field called >>> name, thus $name is used for the parameter >>> >>> The advantage of the widget form is that it allows macro parameters to >>> be specified as widget attributes >>> *parameters* Macro parameters specified as attributesThis includes >>> *$macrocall* >>> *ActionCreateTiddlerWidget* >>> *ActionDeleteFieldWidget* >>> *ActionSendMessageWidget* >>> *ActionSetFieldWidget* >>> *VarsWidget* >>> >>> Each of the above need to be able to have the the parameter name=value >>> thus provide $name=parmval to stop a clash. They are all quite general in >>> nature. >>> >>> It is actually very simple, Ask yourself in any given widget may you >>> need to be able to set a value (Typically a field) of the same name as on >>> of the documented parameters? >>> >>> Regards >>> Tony >>> >>> On Friday, February 22, 2019 at 1:50:53 AM UTC+11, Mohammad wrote: >>>> >>>> Unfortunately it is confusing >>>> >>>> <$wikify name= ... >>>> <$macrocall $name= ... >>>> >>>> >>>> I would recommend for widget, use widget parameter with $ and >>>> everything else without it! >>>> But seems for backward compatibility there are very hard to revise! >>>> >>>> --Mohammad >>>> >>> -- 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/b0083415-5375-432d-84a5-51dfe68571a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
