That logo definitely needs to happen. But... what type of plug ;)
On Wed, Mar 20, 2013 at 8:45 AM, Braden Shepherdson <bra...@chromium.org>wrote: > That logo needs to happen. > > plugman is the tool for downloading plugins, for inserting their config > file changes, installing their native code, and arranging for their JS > modules to be loaded at runtime. > > cordova-cli is the tool for managing multiple platforms with one www > directory to rule them all. It uses plugman to do most of the heavy > lifting, pointing plugman at its plugins/ directory and each of its > platforms/foo directories in turn. > > Note that I'm speaking normatively here; the current situation is a bit > more of a mess. FUTURE.md is intended to show the route out of the mess. > > Braden > > > On Wed, Mar 20, 2013 at 11:04 AM, Lorin Beer <lorin.beer....@gmail.com > >wrote: > > > cool stuff, guys, +1. Read through FUTURE.md, sounds great! > > > > quick question: this is a general plugin manager, for third party plugins > > as well as core plugins? > > > > HA! Plugman, with 'man' for 'manager', I just now got that. And here I > was > > envisioning Anis dressed up as a superhero with a giant 3-prong AC plug > for > > a helmet. > > > > > > On Wed, Mar 20, 2013 at 7:39 AM, Jeffrey Heifetz < > jheif...@blackberry.com > > >wrote: > > > > > +11 I really like the plan > > > > > > On 13-03-20 10:23 AM, "Andrew Grieve" <agri...@chromium.org> wrote: > > > > > > >Read through FUTURE.md. Like it! Sounds amazing! Great work guys! > > > > > > > > > > > >On Tue, Mar 19, 2013 at 5:02 PM, Filip Maj <f...@adobe.com> wrote: > > > > > > > >> For those unaware, cordova-plugman [1] is a tool under active > > > >>development > > > >> that will be responsible for all the plugin things. > > > >> > > > >> Braden, Anis and I are actively working on getting this tool to a > > > >>working > > > >> state, after which we will more completely integrate with > cordova-cli. > > > >> > > > >> Braden is currently tackling JavaScript "installation" into a > > platform's > > > >> www folder. This uses cordova.js' baked-in clobbers/merges > > functionality > > > >> to attach JS modules to specific global namespaces. > > > >> > > > >> Some of the bigger changes include: > > > >> > > > >> - splitting out plugman install functionality into two separate > steps, > > > >>one > > > >> for handling JS and the other for handling native installs. > > > >> - plugins (at the minimum, the plugin manifest) will be stored in a > > > >> project (currently aiming for under cordova/plugins) for ease of > > looking > > > >> up which plugins are installed and how they are composed > > > >> > > > >> Braden has put up a future branch on cordova-plugman [2] where we > can > > > >>all > > > >> track this work. Additionally he has a FUTURE.md [3] file that lays > > out > > > >> specific changes necessary. > > > >> > > > >> [1] https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git > > > >> [2] > > > >> > > > >> > > https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=shortlog > > > ; > > > >>h= > > > >> refs/heads/future > > > >> [3] > > > >> > > > >> > > > > > > https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=blob;f=FU > > > >>TU > > > >> > RE.md;h=6ff68846fd115059afde3abf000690a566d61ff0;hb=refs/heads/future > > > >> > > > >> > > > > > > > > > --------------------------------------------------------------------- > > > This transmission (including any attachments) may contain confidential > > > information, privileged material (including material protected by the > > > solicitor-client or other applicable privileges), or constitute > > non-public > > > information. Any use of this information by anyone other than the > > intended > > > recipient is prohibited. If you have received this transmission in > error, > > > please immediately reply to the sender and delete this information from > > > your system. Use, dissemination, distribution, or reproduction of this > > > transmission by unintended recipients is not authorized and may be > > unlawful. > > > > > >
