Hi Danielo, I said "Saving and reloading is not really a drawback anymore" because, until recently reloading meant, that afterwards only those tiddlers were displayed that were mentioned in "DefaultTiddlers". But I learnt that one could add "[list[$:/StoryList]]" to DefaultTiddlers and all the open tiddlers are also restored.
Michael Am Sonntag, 26. Januar 2014 20:01:07 UTC+1 schrieb Danielo Rodríguez: > > Hello Michael, > > Glad it helped. What do you mean with "Saving and reloading is not really > a drawback anymore" ? After coding a JavaScript Macro it's true you have to > reload the page to make the core load the core. After that, you don't need > to reload again unless you made changes to the macro. > If you code some good macros, don't forget sharing them! ;) > > El domingo, 26 de enero de 2014 19:26:09 UTC+1, Michael Herrmann escribió: >> >> Hello Danielo and Stephan, >> >> thanks for the hints. From that I learnt that I should have a look at >> tw5magick more often ;-) >> >> The example for a global macro (w/ limitations) was very interesting and >> I had to recognize that I have still not fully anticipated the mindset of >> TW5. >> >> And the JavaScript macro is what I need. Saving and reloading is not >> really a drawback anymore, since now reloading can yield the very same >> tiddlers again. >> >> Thanks a lot >> Michael >> >> Am Samstag, 25. Januar 2014 02:30:15 UTC+1 schrieb Danielo Rodríguez: >>> >>> For me the JavaScript version of the macros is working globally. >>> You can find an example at : >>> >>> http://tw5magick.tiddlyspot.com/ >>> >>> El viernes, 24 de enero de 2014 19:44:21 UTC+1, Michael Herrmann >>> escribió: >>>> >>>> Hello, >>>> >>>> In general I was delighted to see that in TW5 we have some kind of >>>> macros. Unfortunately the scope of macros is mainly the current tiddler. >>>> That means if I have a universally usable macro I have to copy and paste >>>> it >>>> to every tiddler where I want to use it. For me this is almost no benefit. >>>> (Maybe I do not recognize some important aspect that leverages this >>>> characteristics.) >>>> >>>> When I read the documentation tiddler I happily misunderstood the last >>>> part of the sentence: >>>> >>>> Macros are available to the tiddler that defines them, plus any >>>> tiddlers that it transcludes. >>>> >>>> At first glance that sounded to me as if I could prepare a tiddler with >>>> all my macros and only transclude that tiddler wherever I like use one of >>>> those macros. >>>> >>>> Unfortunately this was a misunderstanding and the use is just the other >>>> way round :-( I.e. if I have a tiddler with some macro and I transclude >>>> another tiddler, then the macro is available in this transclusion. Sounds >>>> interesting, but currently no use case comes to my mind. >>>> >>>> I know that there is one tiddler that exports it's macros globally: >>>> $:/core/ui/pageMacros. I see these drawbacks: >>>> >>>> (1) The choice between "not available elsewhere" and "available >>>> everywhere" is a too big step. I would prefer a more fine grain >>>> granularity. >>>> >>>> (2) This system tiddler is under risk to be overwritten when upgrading >>>> TW5. >>>> >>>> So, my question is: wouldn't it be very useful to widen the scope of >>>> macros somehow? Perhaps by some kind of _import_ mechanism? >>>> >>>> regards >>>> Michael >>>> >>>> -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
