cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CB-6481) Add unified hooks support for cordova app and plugins
Date Tue, 12 Aug 2014 02:59:12 GMT


ASF GitHub Bot commented on CB-6481:

Github user csantanapr commented on the pull request:
    Here is a gist of a Hook I'm working on for IBM
    You can see how I'm using Context opts and requireCordovaModule
    2 Items I'm looking how to improve is:
    1.  I want to be able to use nopt module, but I can't using requireCordovaModule, because
nopt is a dep from cli not cordova-lib
    2. Getting a parser for the platform doing 
    platforms = context.requireCordovaModule('../cordova/platforms')
    parser = new platforms[platformId].parser(platformPath);
    It feels like using a private API ;-)

> Add unified hooks support for cordova app and plugins
> -----------------------------------------------------
>                 Key: CB-6481
>                 URL:
>             Project: Apache Cordova
>          Issue Type: New Feature
>          Components: CLI, Plugman
>            Reporter: Sergey Grebnov
>            Assignee: Sergey Grebnov
> As per "Proposal: hooks support for plugins" dev mail thread discussion
> Hi, I have an idea how we can add more flexibility to plugin developers.
> Note, right now we have Application Developers – someone who use Cordova for developing
applications and Plugin Developers – someone who creates plugins so that Application Developers
can use them. For Application Developers we expose  hooks so that they can customize their
build/package/etc process. I want us to provide similar sort of flexibility to Plugin Developers
so that they can go beyond of <source/>, <framework/>  tags and get mechanism
to add custom installation,  build logic required by a plugin. Example usage will include:
downloading/compiling additional binaries, marking source file to be copied to output dir,
changing target build platform,  etc. At present time the steps described could be only achieved
by hooks manually added by Application Developer, but the right way is to allow Plugin Developer
to expose this as part of plugin definition.
> Example configuration could look like
> ```
> <script type="postinstall" src="scripts/postinstall.js" />
> <script type="preinstall" src="scripts/preinstall.js" />
> <script type="install" src="scripts/install.js" />
> ```
> beforeinstall/preinstall – run before plugin is installed
> install/postinstall/afterinstall – run after plugin is installed
> uninstall – run after plugin is uninstalled

This message was sent by Atlassian JIRA

View raw message