At Jeremy's suggestion I'm looking at a halfway-house. So rather than just have evaluated macro parameters switched on or off, we could have a restricted evaluation: the code would be parsed and only executed if it was 'safe'. The user would then have the choice of setting macro parameter evaluation to on, off, or restricted. I'm looking at implementing this at the moment.
What would be useful is people could give some examples of some of the simpler evaluated macro parameters (transclusions) that they used. I've looked at quite a few of Eric's transclusions from TiddlyTools and think that most of these would require unrestricted evaluation, since they access the story or the store. TIA, Martin On Sep 22, 2:42 pm, Tobias Beer <beertob...@googlemail.com> wrote: > Hi Jeremy... > > How difficult would you think it were to implement a sandbox-mode > after including another space... then for a while one could work with > the sandboxed-inclusion and once you're comfortable that things work > as expected, you hit the button to either permanently accept or > otherwise undo the inclusion. > > Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlyw...@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
