incubator-callback-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cordova Wiki] Update of "PluginDesign" by FilMaj
Date Tue, 24 Apr 2012 21:56:58 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cordova Wiki" for change notification.

The "PluginDesign" page has been changed by FilMaj:
http://wiki.apache.org/cordova/PluginDesign?action=diff&rev1=6&rev2=7

Comment:
Added more information to the plugin design based on drew's prototype

  
  == Directory Structure ==
  
- TBD
+ Below are examples based on existing prototype implementations.
+ 
+  * Based on [[https://github.com/deedubbu/cordova-blackberry-pluggable|Drew's prototype]],
JavaScript and native code is packaged in the same directory. It is a bit tied to the specifics
of the WebWorks platform, but the general structure is:
+   * All plugins plus the core framework are encapsulated as extensions, which is a WebWorks
concept. These extensions package up any necessary JS and native code.
+   * Each extension is included with your final application via declaring specific {{<feature>}}
elements in your application's config.xml file. Each {{<feature>}} maps to a specific
extension: either the core framework or a plugin.
  
  == Meta Files ==
  
@@ -39, +43 @@

      * {{{action}}} - the native plugin method label that maps to the desired native plugin
method. Each native platform has a different mapping mechanism - see below under Native Files
section for more details
      * {{{args}}} - an Array of parameters to pass into the native plugin methods
    * Recommended to use {{{cordova.define}}} as module definition wrapper that conforms with
cordova.
+  * No JavaScript requirements on namespacing plugins (used to be that all plugins were added
to a {{window.plugins}} object). This should be up to the plugin author.
  
  == Native Files ==
  

Mime
View raw message