[tw5] Re: Plugin design: splitting up vs. duplicating

2020-05-11 Thread PMario
Hi, I think, it depends on how "connected" your plugins are. If 1 functionality is hardly used *without* the other, I would keep it in 1 plugin. If it is very likely, that they are useful alone, and do completely different things, you should split them. The chance is high, that users demand d

[tw5] Re: Plugin design: splitting up vs. duplicating

2020-05-11 Thread bimlas
HCHaase, Tiddly handles plugin dependencies well, so I would vote for separate plugins in this regard. https://tiddlywiki.com/#Plugin%20Dependencies If we look at how NPM (Node.js Package Manager) works, it is entirely made up of package dependencies: each package does one single thing (in pr

[tw5] Re: Plugin design: splitting up vs. duplicating

2020-05-10 Thread HC Haase
Thank you for your thoughts. it is good to get some other persepctives. as I feard, this is not a clean cut. -- 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 tidd

[tw5] Re: Plugin design: splitting up vs. duplicating

2020-05-09 Thread TonyM
HC, This is a very good Question. I think whilst coding can be a science sometime it becomes an art. Here are a few thoughts that may guide the decision - Do the various features of the belong as one logical unit? - This seems so when there are dependencies - Are the features valuab