>
> One of the other goals here is to make the tools magically convenient
> without becoming voodoo. That's the fundamental goal behind turning
> platforms/ into a build artifact: then the answer to "what files in here
> can I edit, and which ones get updated when I run ?" is an
> easy, blanket ans
Braden's got this, +1
On 3/25/13 11:20 AM, "Braden Shepherdson" wrote:
>I'm not sure about moving the platforms folder, build artifact or no,
>because one may be loading it in Eclipse/Xcode/etc. and burying it in a
>hidden folder makes the tools more magical.
>
>One of the other goals here is to
I'm not sure about moving the platforms folder, build artifact or no,
because one may be loading it in Eclipse/Xcode/etc. and burying it in a
hidden folder makes the tools more magical.
One of the other goals here is to make the tools magically convenient
without becoming voodoo. That's the fundam
>
> +1 for ./platforms becoming a build artifact.
I totally support this goal Braden.
When we make the platforms/ a build artifact, I'd like to move the
platforms directory to:
/my-app/.cordova/platform/
Michael
On Fri, Mar 22, 2013 at 3:07 PM, Michael Wolf wrote:
> Agreed +1
>
> On 3/22/13
Agreed +1
On 3/22/13 4:23 PM, "Brian LeRoux" wrote:
>Ya love it. =)
>
>On Fri, Mar 22, 2013 at 1:02 PM, Filip Maj wrote:
>> Agree with everything Braden said
>>
>> On 3/22/13 12:05 PM, "tommy-carlos Williams" wrote:
>>
>>>+1 for ./platforms becoming a build artifact.
>>>
>>>That is already how
Ya love it. =)
On Fri, Mar 22, 2013 at 1:02 PM, Filip Maj wrote:
> Agree with everything Braden said
>
> On 3/22/13 12:05 PM, "tommy-carlos Williams" wrote:
>
>>+1 for ./platforms becoming a build artifact.
>>
>>That is already how we are attempting to roll in our project using the
>>cli, though
Agree with everything Braden said
On 3/22/13 12:05 PM, "tommy-carlos Williams" wrote:
>+1 for ./platforms becoming a build artifact.
>
>That is already how we are attempting to roll in our project using the
>cli, though its not quite right yet.
>
>On 23/03/2013, at 5:26, Braden Shepherdson wrot
+1 for ./platforms becoming a build artifact.
That is already how we are attempting to roll in our project using the cli,
though its not quite right yet.
On 23/03/2013, at 5:26, Braden Shepherdson wrote:
> We want this to stick around. One of my goals for the CLI is to make the
> platforms/f
We want this to stick around. One of my goals for the CLI is to make the
platforms/foo subdirectories completely build artifacts. Native code, web
assets, JS code, all get copied on every prepare. That's not currently true
for native code, but it is for the rest.
Since we're doing that, we need th
Cool. So, is this interim or necessary to exist for all of time?
(Would assume you need some sort of staging area but not sure you need
to keep em around if we can cache the manifest info or something.)
On Fri, Mar 22, 2013 at 11:01 AM, Braden Shepherdson
wrote:
> I assume you mean the top-level
I assume you mean the top-level plugins/ folder in the CLI?
That is where plugins are cached when you cordova plugin add them. Whether
they're coming from local directories or git or wherever, they get copied
here. Then on a prepare this is where the plugin's assets are copied from.
Braden
On F
...
12 matches
Mail list logo
