List of TW5 Plugins?

[Johnny Walker]

Hi all,

Can anybody point a list of available TW5 Plugins?

>I had no luck locating

Thanks

[PMario]

https://github.com/Jermolene/TiddlyWiki5/tree/master/plugins/tiddlywiki
-m

[Jeremy Ruston]

There should be a proper plugin page on tiddlywiki.com; I've made a ticket:

https://github.com/Jermolene/TiddlyWiki5/issues/363

Best wishes

Jeremy

On Sun, Jan 26, 2014 at 11:48 PM, PMario <pmar...@gmail.com> wrote:

https://github.com/Jermolene/TiddlyWiki5/tree/master/plugins/tiddlywiki
-m

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/groups/opt_out.

--
Jeremy Ruston
mailto:jeremy...@gmail.com

[Stephan Hradek]

While we are at it, Jeremy… How would I make my newtiddler widget a proper official plugin? And also the let widget…

[Jeremy Ruston]

Hi Stephan

On Mon, Jan 27, 2014 at 8:39 AM, Stephan Hradek <stephan...@gmail.com> wrote:

While we are at it, Jeremy… How would I make my newtiddler widget a proper official plugin? And also the let widget…

We need to figure out how the plugin library is going to work. The goal is to provide a better end user experience than the TWC approach of plugins being published independently around the web. Goals and considerations:

* To make sure that plugins remain available once published

* To give users some assurance that a plugin has been tested

* To establish a standard format for documentation, tests, demos and examples

* To provide a central place for future upgrade processes to obtain updated plugins

My thoughts are that each plugin needs to have an explicit maintainer who is responsible for updating it for each core release. The listings would deprecate any plugins that haven't been updated since the last release.

The idea of re-using npm to handle plugin installation is exciting: we'd be able to tap into an existing ecosystem of tools for managing dependencies, versioning and so on.

Anyhow, right now, we just have plugins packed into the main TW5 repo. That means that in your case there is the obstacle remaining of not being able to run the Node.js configuration of TW5. That means that you can't run the test suite, which makes it hard for to participate properly in core development. Most TW5 components need to run under Node.js and in the browser, and so need to be tested in both places. I've discussed before that I intend to make it possible to create plugins within the browser, and over time it may become more practical for contributors to work entirely in the browser.

Best wishes

Jeremy.

[Stephan Hradek]

Am Montag, 27. Januar 2014 10:45:46 UTC+1 schrieb Jeremy Ruston: 

Anyhow, right now, we just have plugins packed into the main TW5 repo. That means that in your case there is the obstacle remaining of not being able to run the Node.js configuration of TW5. That means that you can't run the test suite, which makes it hard for to participate properly in core development.

But there is Mario's vagrant which I will for sure try out very soon. My shoulder is a real "pain in the neck" ;) making it difficult to concentrate, so I try to do not too much on the computer besides what I'm paid for.
 

Most TW5 components need to run under Node.js and in the browser, and so need to be tested in both places. I've discussed before that I intend to make it possible to create plugins within the browser, and over time it may become more practical for contributors to work entirely in the browser.

So provided I can run node.js in vagrant - what do I need to add to my widgets to become proper plugins for the current "ecosystem"?

[PMario]

On Monday, January 27, 2014 10:57:51 AM UTC+1, Stephan Hradek wrote:

Am Montag, 27. Januar 2014 10:45:46 UTC+1 schrieb Jeremy Ruston: 

Anyhow, right now, we just have plugins packed into the main TW5 repo. That means that in your case there is the obstacle remaining of not being able to run the Node.js configuration of TW5. That means that you can't run the test suite, which makes it hard for to participate properly in core development.

But there is Mario's vagrant which I will for sure try out very soon. My shoulder is a real "pain in the neck" ;)

Hope, it will be better soon!
To be sure, the configuration works, I did create a pull request with the setting: https://github.com/Jermolene/TiddlyWiki5/pull/351
The request wasn't merged, but the "pull jermolene, push origin" mechanism works. ... You should have a look at the videos, to adjust the git remote settings in the right way. first and second video should be ok ;) .... which reminds me to create a written version too :)
 

Most TW5 components need to run under Node.js and in the browser, and so need to be tested in both places. I've discussed before that I intend to make it possible to create plugins within the browser, and over time it may become more practical for contributors to work entirely in the browser.

So provided I can run node.js in vagrant - what do I need to add to my widgets to become proper plugins for the current "ecosystem"?

@jeremy
I think we should not establish a "workaround". We may not be able to "kill" it anymore.

I'd love to have a solution instead.
Stephan you know: "Nichts hält länger als ein Provisorium" ... I don't know a propper translation for this one:)

Jeremy, Eric and I did discuss the plugin mechanism at hangout 3
http://www.youtube.com/watch?v=jduxruwB5K4
new time formatted annotations at: http://pmario.tiddlyspace.com/#2013-06-03-TW5-hangout-3

At 0:12:15 we started to talk about it. So I think we should review this stuff, and see, how we can implement it.

-mario
http://pmario.tiddlyspace.com/#2013-06-03-TW5-hangout-3

[PMario]

tw5-vagrant - intro video links

TW5 vagrant 01 - http://www.youtube.com/watch?v=JE0l36A_eBI
How to use the box, if you just want to test the client server edition

TW5 vagrant 02 - http://www.youtube.com/watch?v=nIonsfVxR3o
How to adjust some git settings, if you want to use the box to contribute and help to improve the documentation

TW5 vagrant 03 - http://www.youtube.com/watch?v=7SqhNNmZO3k
Some more info about the nodejs autostart mechanism, that is used. How to tweak the settings.

As usual, feedback is very welcome!
-m

[Jeremy Ruston]

Hope, it will be better soon!
To be sure, the configuration works, I did create a pull request with the setting: https://github.com/Jermolene/TiddlyWiki5/pull/351
The request wasn't merged, but the "pull jermolene, push origin" mechanism works. ... You should have a look at the videos, to adjust the git remote settings in the right way. first and second video should be ok ;) .... which reminds me to create a written version too :)

Right, but I believe that I fixed #351 through another approach - is it still causing problems?

 

I think we should not establish a "workaround". We may not be able to "kill" it anymore.

Do you mean we shouldn't establish a workaround for plugin publishing? I'm inclined to agree.

 

I'd love to have a solution instead.

A solution to what?

 

Best wishes

Jeremy

[Johnny Walker]

Excellent,

A Plugin section will be Valuable,

Thanks

[Johnny Walker]

Thanks Appreciated