[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-03 Thread TonyM
All, My point was to *add context to the instructions*. I am fine with No JavaScript instructions, just say its "Wiki text and macro plugins" or what ever you see fit. But so people know what it is talking about and the scope of the instruction. Regards Tony On Sunday, 3 May 2020 14:32:19

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread Mohammad
Mark, I think at the time of writing those docs, their focus was on official plugins! By the way I tried in my tutorial create a step by step simple procedure! As you see the main point is: correct naming, folder structure, plugin.info So, any newbie can follow and create one! --Mohammad

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread Mohammad
Hi Birthe On Sunday, May 3, 2020 at 8:40:24 AM UTC+4:30, Birthe C wrote: > > TonyM, > > Mohammad is preparing a section in The Book by Luis on creating plugins > using TW on Node.JS. > Other sections could be written by other if they so wish. > Exactly! In my work all the the time I stick to

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread Birthe C
TonyM, Mohammad is preparing a section in The Book by Luis on creating plugins using TW on Node.JS. Other sections could be written by other if they so wish. Mark S, Exactly! Everything else will lead to confusing when sharing the TW. We can do what we want i private wikies. Birthe søndag

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread 'Mark S.' via TiddlyWiki
Looking at the /dev instructions, I feel there may be an error. It looks like you'll end up with a directory structure like: TW/plugins I think when you do the cloning, you should be in the directory, not the directory. Or am I misunderstanding? Also, you don't need to build the index

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread 'Mark S.' via TiddlyWiki
On Saturday, May 2, 2020 at 7:19:12 PM UTC-7, TonyM wrote: > > Mohammad, > > Presumably this project is about using javascript functions building > plugins? > > As you may know it is quite easy to build "plugins" without javascript, > basically as plugin packages, I am working on multiple

Re: [tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread Mohammad Rahmani
Tony, The procedure is using node.js and it is about wikitext plugins not JS! It is really simple, simpler than developing in explorer! But you are right in the tutorial we should say it is possible to encapsulate javascripts in plugin! perhaps the initial idea was to write plugins in JS.

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread TonyM
Mohammad, Presumably this project is about using javascript functions building plugins? As you may know it is quite easy to build "plugins" without javascript, basically as plugin packages, I am working on multiple methods to do this in the single file wikis and there are lots of

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread 'Mark S.' via TiddlyWiki
There is a procedure mentioned in the developer wiki on how to make plugins by hand without node.js. Probably not user-friendly. On Saturday, May 2, 2020 at 12:57:24 AM UTC-7, Petruschka wrote: > > Hello Mohammad! > > Why node.js? I am asking because I think your "The procedure SHOULD not >

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread Mohammad
Hi Petrushka, I have created some tutorial to be included in The Book of Tiddlywiki! So, this is part of that! See the tutorials here: http://sistan.tiddlyspot.com/ Each tiddler has a prev | next at the bottom where you can follow steps in a linear manner. Hope this help you! Cheers Mohammad

[tw5] Re: A simple procedure to create plugins with TW+Node.JS

2020-05-02 Thread Petruschka
Hello Mohammad! Why node.js? I am asking because I think your "The procedure SHOULD not rely on other plugins only pure TW distributed officially" approach to help others help themselves to packaging is great. I for myself try to not use node.js on the customer desktop systems when entering a