Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of fil@adobe.com designates
 64.18.1.184 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Sat, 15 Sep 2012 19:29:53 -0700
Subject: Re: plugin tooling/specification
Thread-Topic: plugin tooling/specification
Thread-Index: Ac2TsykdqTq4z85zR22hQ6ZyibfAPw==
Message-ID: <CC7A877B.DD5E%fil@adobe.com>
In-Reply-To: 
 <CANpVHHy1DSNrEXhB8ttx5FhoKxFNMw3nOeCKBW_UyiSG=bOkxQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Right. I'm ok with this but wanted to keep the exact cordova-powered
platform projects as untouched as possible, so you could cd into those
directories and do whatever you want (run usual cordova project commands,
compile, etc). So removing the www from there forces everyone to always go
through the tool.

On 9/15/12 7:23 PM, "Anis KADRI" <anis.kadri@gmail.com> wrote:

>On Sat, Sep 15, 2012 at 5:32 PM, Filip Maj <fil@adobe.com> wrote:
>
>>
>> >Ohhh I think I understand. So basically it packages the www resources
>>into
>> >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
>>into
>> each platform before doing a compile for that platform.
>>
>> >> platforms/xxx/www gets destroyed and recreated on every build. See
>> >> here<http://bit.ly/PFKQvS>.
>> >> It's needed to build packages for every platform. It could arguably
>>be
>> >> destroyed after every build though. Fil is there a reason why that's
>>not
>> >> 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?
>>
>
>Yes that's what I meant.
>
>
>>
>> If the latter, I don't see the point.
>>
>
>To avoid confusion. The reason why we're discussing this is because Mike
>got confused after seeing the root www and a www in each platform
>subfolder. There is also no reason to keep them around since they get
>destroyed before every build anyway. So maybe they should just get
>destroyed _after_ every build. You'd just recursively copy the folder
>before every build. I don't really care either way. Just trying to avoid
>the "Where do I drop my code?" scenario.