 Added PlugIn interface and PlugInGenerator utility for creating custom PlugIns. Some basic knowledge of JavaScript is needed to create PlugIns. The PlugInGenerator can be launched from NeoAppBuilder's Tools menu.

 A partial help file (draft) is included.

 Several minor fixes and enhancements.

The PlugIn Generator allows you to create custom plugins from your own code or create wrappers for existing JavaScript libraries. There wasn't time to create documentation for this utility, but I'll try to get that out in the next couple of weeks. Much of it should be self-explanatory, but feel free to post questions, suggestions, etc. An example Date & Time plugin is included with source (Documents\NeoAppBuilder\PlugIns) so you can see the process. Plugins include a source file (*.nabpsrc) and a compiled file (*.nabp) for distribution and installation into NeoAppBuilder. The compiled *.nabp file contains everything needed by the plugin, including any external files, libraries, etc.

This is great update, congratulations!The posssibility to easily create plugins opens the door to a bunch of already existing libraries.

I have some questions and comments about the Plugin Generator:NAB exports all the plugins code even if the functions of someone of them are not called at all within the app?Is it possible to know what plugins needs an app to run properly?Will it be possible in the future to add more file types (mainly image files) so we can be sure they are available into an specific folder?I think it would be also very handful to have any way to organize the functions within a plugin (subcategories)

NAB exports all the plugins code even if the functions of some of them are not called at all within the app?

Only installed plugins that are actually used by the app will be compiled/exported. However, as with JavaScript libraries, even if you only use a single function from a plugin the entire plugin will be compiled.

Is it possible to know what plugins needs an app to run properly?

You should get a generic error if you try to run or compile an app that requires a plugin you don't have, but it's the same error you would get if your app contains a typo. NAB doesn't have any way of knowing if a code error is simply a typo or a missing plugin.

Will it be possible in the future to add more file types (mainly image files) so we can be sure they are available into an specific folder?

Yes, I think so. This is a basically first draft so I expect that there will be lots of changes as people start working with the PlugInGenerator. I'm sure there will be JavaScript libraries that require files and different things. One of the things that needs to be worked out is where the various libraries expect those files, etc. to be and how that can be communicated to NAB.

I think it would be also very handful to have any way to organize the functions within a plugin (subcategories)

Yes, we did something similar with NeoBook and can probably do that here too in the future.