Hi Jeremy, > Yet another idea that might work for intensive development is to have your > plugin on your local drive, but include it via a file:// uri from a <script> > tag in your MarkupPreHead. That way, you could edit-save-refresh in the usual > way.
I've considered that and it is fine up until the point where the plugin itself contains template that need to be accessed as tiddler text. I could work around that by having the plugin create that stuff as shadow tiddlers. Yet, in my current case that's really not what I want as these templates are not intended for others to be edited. On the other hand, as a general question, at the time of loading those plugins via MarkupPreHead, would the core be ready to register shadows, etc? Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
