Interesting you discuss this,
I have recently started building a plugin repository to help me keep more
information about plugins than the author gives me.
The plugin I am building needs details in it or it would not be very
useful, and in fact I also intend to have a reference to additional no
>
> Diego Mesa wrote:
>
> Just want to mention, I've used the excellent tinka plugin:
>
> https://tinkaplugin.github.io/
>
> to package and edit plugins.
>
> I have also noticed it seems to conventional to include minimal
> documentation, but I am not so sure why. I always have to end up refering
For the benefit of those who may in some future come across this
discussion, this is how I finally implemented it: as suggested I'm using a
<$list> widget to transclude "skin" CSS stylesheets from plugins. These
have to be tagged especially as skin CSS tiddlers (they can be either of
type CSS o
Very pleased to report that I have a working prototype of the modloader
plugin now, complete with a tool to generate patch files. This is going to
need some testing.
On Saturday, 20 January 2018 12:36:13 UTC-6, Evan Balster wrote:
>
> Hey, Jeremy —
>
> I think that this can be written without r
