The module is wrapped in a closure, with module, exports, and require in scope, as is normal for AMD modules. Do not wrap the file with fine, as it is added automatically. Each tag corresponds to a JavaScript file, and prevents the plugin's users from having to add a tag for each file. Most plugins include one or more JavaScript files. You may use the wildcard * to say supported for all platforms, specify multiple with a pipe character like android|ios or just a single platform like android. Ideally, this file should be within the top level directory of your plugin directory. The script file that tells plugman the version of the custom framework. The version that your framework must have in order to install. Here are the default engines that are supported : cordova cordova-plugman cordova-android cordova-browser cordova-ios cordova-windows cordova-osx windows-os android-sdk (returns the highest Android api level installed) windows-sdk (returns the native windows SDK version) apple-xcode (returns the xcode version) apple-ios (returns the highest iOS version installed) apple-osx (returns the OSX version) You can also specify a custom framework apart from the default ones. NOTE: In Cordova 6.1.0+, the recommended place to specify platform, plugin, and CLI dependencies #ADDING XML TO EVOSCAN 2.9 INSTALL#If no tags are specified, the CLI attempts to install into the specified cordova project directory blindly. The CLI aborts with a non-zero code for any plugin whose target project does not meet the engine's constraints. The child elements of the element specify versions of Apache Cordova-based frameworks that this plugin supports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |