Re: [twdev] Re: Latest on a plugin dev structure?

2015-11-13 Thread Felix Küppers
Hi Tobias > I'm a bit struggling trying to understand this workflow / setup. > > Here's a setup I created today for a macro called *dict* that > I am trying to turn into and publish as my first actual plugin... Glad you make this step. Given your level of productivity, I expect 100 plugins by the

Re: [twdev] Re: Latest on a plugin dev structure?

2015-11-13 Thread Tobias Beer
Hi Felix, Thanks for all the feedback and walking me through this a little further. > Minification only works and makes sense with javacript and css. > You cannot minify tid files because wikitext is sensititve to newlines etc. > Sure, so this was not the plugin for it :D There definitely

[twdev] Re: Latest on a plugin dev structure?

2015-11-03 Thread Felix Küppers
Hi Phil. For bigger projects, I highly recommend you develop plugins not in the browser. (although great browser based plugin boilerplates exist like Tinka by Andreas Hahn). Do I just leave out the author name from > `wiki\plugins\PhDyellow\pluginname` and just use `wiki\plugins\pluginname`?

[twdev] Re: Latest on a plugin dev structure?

2015-11-03 Thread Philip Dyer
Hi Felix, Thanks for those links. After looking through, this is my summary of those discussions: - have a src and dist folder in the project - src is the working files being worked on - dist contains the compiled plugin ready for inclusion with nodejs. - It is structured