Download
2015-07-27, 20:32:03
Quote:Also, should this topic be moved to Developer Discussions?
You could simply prefix the post title with [Discussion] or something.
Quote:The original Hello World plugin and the existing wiki illustrates a plugin simple enough to start grasping the basic functions, actions and hooks
I would even argue it doesn't do this completely.
Quote:I suppose the main thing to take away from both of your comments is that there is concern over what the example plugin should illustrate, and what the eventual SDK should consist of .
Yes, and this is much a matter of target audience. What is the level of skills of aspiring plugin developers? For me, it was zero. The only thing I knew about PHP was how to build forms & some other really basic stuff. And when you look at the code for WJ Notepad or some other plugins, you'll see it's pretty "low quality" (in terms of design patterns).
And although I would never use plugins like File editor, DY Lorem Ipsum or I18n language Menu Ex (because what these plugins do is so basic and offers, imo, no substantial benefit over hand-coding/ copy-pasting), it would be overkill to request from plugin authors that they become familiar with classes and OOP for such simple plugins, certainly when they start from zero (I learned more quickly because I already had an OOP/MVVM background in JS).
On the other hand, if I could I would totally urge plugin authors to build plugins which offer something substantial; I mean, plugins which truly save you a lot of effort (but ofc. also require more effort from the dev) eg. I18N, Itemmanager, Newsmanager (to name the truly biggest ones).
Same for custom functions, eg. I don't think
$this->register(array(...)) is much more advantageous than register_plugin(...).Ideally, I think, there would be a 'Hello World' basic example, an intermediate, and an advanced example, perhaps we could even make use of the popular TodoMVC structure for the advanced example. This thread's initiative would be fit for the second/ third one.
