On Monday, April 13, 2015 at 1:51:29 PM UTC+2, Mat wrote:
>
> Thank you PMario! How would this compare to the @@ benefits that Eric 
> lists, i.e:
>
> [the @@ syntax supports]  @@.class.class.class ...@@  and   
>> @@attr:value;attr:value;...@@
>> ... 
>>
> content inside the @@..@@ block can be *any* wiki text -- including 
>> macros.  
>> ...
>>
> nest the @@...@@ syntax
>>
>
TL;DR

- Wikitext create a "predefined" html output.
- Macros let the user create it. 

----------------------

As Eric wrote, the wikitext [1] style definition [2] can be easily nested, 
but the result is "kind of" predefined. 

Macros give the user the possibility to create there own structure but are 
harder to nest. See <$macrocall> [3] widget. 

Macros are very useful to remove / hide complexity from the end user. See 
my <<myMacro "some text">> example. It's much easier to remember, then the 
first examples. ... 

Or have a view at the TW Table Of Contents macro [4] You just need to type: 
<<toc "Contents>> instead of the whole complex structure [5]. The link 
contains all toc-xxx macros but anyway. ...

hope that helps
mario

[1] http://tiddlywiki.com/#WikiText
[2] http://tiddlywiki.com/#Styles%20and%20Classes%20in%20WikiText
[3] http://tiddlywiki.com/#MacroCallWidget
[4] http://tiddlywiki.com/#TableOfContentsMacro
[5] http://tiddlywiki.com/#%24%3A%2Fcore%2Fmacros%2Ftoc

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/9c259699-75f2-4e25-815d-df153403acf2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to