> What do you mean by "coded safely and reliably"? (ok, perhaps this is > not a question to discuss without an example..)
Well, a poorly written plugin might fail if it encounters unexpected data, or might leak private information in HTTP headers, or might not work reliably in mobile browsers, or might rely on implementation details in the core that are subject to change. > Do you mean that the server would be needed once -- to generate those > html files so that one can publish them in a DropBox, -- or rather > during the process of browsing? What's the role of the server? Here the server is being used to "bake" html files that can be used independently. > Another thing which is unclear for me in this aspect is the > following.. the most direct quesion is this: will it be possible to > open any set of tiddlers in a tab of a browser, or instead there > should be some pages, each containing some tiddlers and for each > tiddler its container-page should be opened in a new tab? I'm afraid I don't understand the question, can you put it differently? Best wishes Jeremy > > > Hans, > >> what I did was create a central "plugin repository" TW file without any >> other data, > > yes, that's what I'm also thinkning about > >> and set that up so that it kept all its plugins updated in as automated a >> way as possible. > > sure, it's not an issue, even if new plugins are added > > <<< > Using a tag for each "real data" TW file, I "pulled" the updated into > each > one, using Eric's importer based on that tag. > > I reckon such an approach would be relatively easy to support and > automate, > if not in core, then perhaps by a "plugin manager" plugin. > <<< > > this is rather unclear for me. Why did you need some tag if the > central repository contains only things to load anyway? What > "importer" did you use? (and is it possible to set the thing so that > certain TWs wouldn't import, for instance, formulae-generating > plugin?) If you provide more details, it would be very much > appreciated. > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To post to this group, send email to tiddlywiki@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. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@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.
