Yup. Should be supported on most platforms, but curiously undocumented(!): http://cordova.apache.org/docs/en/3.5.0/plugin_ref_spec.md.html#Plugin%20Specification
It was previously documented here for example: http://cordova.apache.org/docs/en/3.1.0/guide_platforms_android_plugin.md.html Current plugin example: https://github.com/apache/cordova-plugin-splashscreen/blob/5d25cf0250ca48b0ed9cce20e2199bfa3e1eef50/plugin.xml#L69 On Wed, Jul 9, 2014 at 11:51 AM, Anis KADRI <[email protected]> wrote: > isn't there a onload=true for config.xml ? > > > On Wed, Jul 9, 2014 at 2:40 PM, Jan Velecký <[email protected]> wrote: > >> Dear devs, >> I think, there can be a new kind of CordovaPlugin with one huge difference. >> This kind of Plugin should start immediately after application start. This >> has benefits in these situation for example: >> >> * It could be plugin with no Javascript controlling because plugins can >> be also controlled by config preferences (application analytics software >> or ad site, where can be enough dev id) >> * It could be plugin with no any controlling (processing hooks to plugin >> in some way to modify or extend Cordova default behaviour) >> * It could be plugin, which need some time to initialize itself and user >> want this plugin ready promptly when he will need it >> >> >> I have two ideas to get it: >> >> 1.) <using> tag (or some other word) for plugin, which need start >> immediately after application start. >> >> >> 2.) Add to <feature> tag "startPromptly" boolean value (or some other >> word). >> Ideally this could been this parameter passed into constructor of plugin >> and >> plugin can do different things in case it starts promptly or it starts >> later. >> >> >> >> >> Nice day, >> >> Jan Velecký. >> >>
