incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <>
Subject Re: plugin tooling/specification
Date Sun, 16 Sep 2012 01:38:14 GMT
I think that might have been a feature that Anis added. If anything the
documentation just needs updating :)

On 9/15/12 6:00 PM, "Mike Reinstein" <> wrote:

>Hi Fil, Anis,
>> Each platform's underlying implementation
>> has its own "www"
>Okay, makes sense to me. I'm at the point where I'd like to install a
>plugin. In the docs it shows:
>cordova plugin add
>Is there a link somewhere to a real package I can try this with? I"m
>assuming childbrowser is the only supported plugin at the moment?
>I'm also wondering how this statement in the documentation "You having the
>plugin code locally on your computer" relates to the example above? The
>first one seems to imply I can just pull a tar/gzipped copy of the file,
>the second seems to imply that I need to pull it down manually.
>On Sat, Sep 15, 2012 at 8:32 PM, Filip Maj <> wrote:
>> >Ohhh I think I understand. So basically it packages the www resources
>> >the binary at build time?
>> Correct. Each platform's underlying implementation has its own "www"
>> folder. At build time, the top-level www of your project gets copied
>> each platform before doing a compile for that platform.
>> >> platforms/xxx/www gets destroyed and recreated on every build. See
>> >> here<>.
>> >> It's needed to build packages for every platform. It could arguably
>> >> destroyed after every build though. Fil is there a reason why that's
>> >> the case ?
>> That is the case is it not? Line 57?
>> Or do you mean, we should delete the platforms/<platform>/www (or
>> equivalent) after building?
>> If the latter, I don't see the point.

View raw message