IF you made a "database" of plugins, what would be the fields?

64 views
Skip to first unread message

@TiddlyTweeter

unread,
Apr 6, 2019, 11:31:20 AM4/6/19
to tiddl...@googlegroups.com
Following from my last post.

I'm unclear what info is needed on a plugin to ensure it documented ...

I got as far as ...

author...
release
-no...
tw
-version-up...
fetch
-address...
view-demo...
license...

I am NOT clear if this was ever standardised?

J.

David Gifford

unread,
Apr 6, 2019, 12:15:41 PM4/6/19
to TiddlyWiki
Two fetch addresses, one for the plugin and one for the demo

Topic(s)

Dave

On Saturday, April 6, 2019 at 9:31:20 AM UTC-6, @TiddlyTweeter wrote:
Following from my last post.

I'm unclear what info is needed on a plugin to ensure it documented ...

I got as far as ...

author...
release
-no...
tw
-version-up...
fetch
-address...
license
...

I am NOT clear if this was ever standardised?

J.

@TiddlyTweeter

unread,
Apr 6, 2019, 12:30:45 PM4/6/19
to TiddlyWiki
Ciao Dave

Perhaps, rather "fetch" for plugin and "view demo".

I updated accordingly.

J. x

Jed Carty

unread,
Apr 6, 2019, 12:55:10 PM4/6/19
to TiddlyWiki
If I were to do this hypothetical thing it would be done about like this http://inmysocks.tiddlyspot.com/#twCard%20Listing%20-%20Plugins

@TiddlyTweeter

unread,
Apr 6, 2019, 2:29:22 PM4/6/19
to TiddlyWiki
Thanks Jed, Very helpful.

TonyM

unread,
Apr 6, 2019, 11:56:15 PM4/6/19
to TiddlyWiki
I do have my own registry.

I create a new tiddler with a related tiddler name eg $:/plugins/tobibeer/split has 

Plugin-tobibeer/split containing


  • Source
  • keywords:
  • plugintiddler:
  • reference:
  • repository:
   This lets me avoid changing the actual plugin tiddler whilst adding details that may have being omitted from the plugin tiddler.

Regards
Tony
Reply all
Reply to author
Forward
0 new messages