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 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 <some command>?" is an easy, blanket answer: "Everything in those directories is a build artifact. You can edit things quickly for testing, but expect them to get overwritten." Braden On Mon, Mar 25, 2013 at 2:11 PM, Michael Brooks <mich...@michaelbrooks.ca>wrote: > > > > +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 <michael.w...@cynergy.com > >wrote: > > > Agreed +1 > > > > On 3/22/13 4:23 PM, "Brian LeRoux" <b...@brian.io> wrote: > > > > >Ya love it. =) > > > > > >On Fri, Mar 22, 2013 at 1:02 PM, Filip Maj <f...@adobe.com> wrote: > > >> Agree with everything Braden said > > >> > > >> On 3/22/13 12:05 PM, "tommy-carlos Williams" <to...@devgeeks.org> > > 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 <bra...@chromium.org> > wrote: > > >>> > > >>>> 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 the full content of the plugins to > > >>>>stick > > >>>> around. Is there a problem with keeping this around? > > >>>> > > >>>> Braden > > >>>> > > >>>> > > >>>> On Fri, Mar 22, 2013 at 2:12 PM, Brian LeRoux <b...@brian.io> wrote: > > >>>> > > >>>>> 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 > > >>>>> <bra...@chromium.org> wrote: > > >>>>>> 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 Fri, Mar 22, 2013 at 1:56 PM, Brian LeRoux <b...@brian.io> wrote: > > >>>>>> > > >>>>>>> ... > > >>>>> > > >> > > > > >
