<$reveal state="$:/plugins/something.js" type="match" text="" > WARNING missing
plugin xyz please download from http://weblink
would generate a similar result
this could easly be transformed into a standard macro with three prameters.
if a unique tag like 'requires' is used then the results of
That's a good idea. Thanks!
--
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 tiddlywikidev+unsubscr...@googlegroups.com.
To post to this group, send email to
Hi Stephan
Concerning your original question: Here is what I did in my plugin ToDoNow. It
depends on another plugin of mine called Listreveal.
In the readme I test for the presence of the other plugin and display a hint
accordingly:
!!! ~ToDoNow needs Listreveal
ToDoNow extends the power
Am Dienstag, 27. Februar 2018 12:33:58 UTC+1 schrieb Jeremy Ruston:
>
> The best next step would be for someone to experiment with an
> implementation, and then open an issue referencing it.
>
> Agreed. But I do not feel capable of being that someone.
;) Stephan
--
You received this
Hi Stephan
> Anyhow: Don't you think it's a good idea to have this as a core feature?
> Every plugin then simply needs to define one string per required plugin. The
> core could then take care required plugins are loaded.
Indeed it would be a useful feature if implemented carefully (I
Am Montag, 26. Februar 2018 13:51:14 UTC+1 schrieb Jeremy Ruston:
>
> the approach that is taken is to have a startup module that checks for the
> required dependencies, and displays an alert if any are missing. Have a
> look at the text-slicer plugin for an example of this.
>
Hmmm…
Okay. I
Hi Stephan
> As you saw: "documentation" is a prerequisit for the other 2 tiddlers, but I
> couldnÄt figure out how to make this auto-install when one of the others is
> selected for installation.
> Is this possible at all?
> I thought "dependent" in plugin.info is for this, but either I did it
