Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of iclelland@google.com designates
 209.85.219.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5261fce9.63b6440a.1a95.3dee@mx.google.com>
References: 
 <CAKP6k2tMK-SnFL4d2E77RgQya2X4P6Lr9F+a5o+_PdRmDQA_Ow@mail.gmail.com>
 <CAEeRA4rGQ-Bv8=KiCRZvXQ2Mw2hQiQnqCNT6seCDWBOpdF14Rw@mail.gmail.com>
 <CAKP6k2uEWkhYQ=Ze_3WkoaBSJB6Rw+yLeH-+XfGnqecYsb-pUQ@mail.gmail.com>
 <CAEeRA4o3Gk2zrMWiKafFCnDpZN56R4y4UPph9TTVB9Fu6O2qZw@mail.gmail.com>
 <CAMk5LL=B1VamHaq3KDZA2+SGLKrCJ44-wGbdVve5nzHpVGTBtg@mail.gmail.com>
 <CAHYtTq=1HD17+8vw-O2Rtbn3mhHbkL0TR5C=PRf730qQgJF7QA@mail.gmail.com>
 <CAMk5LLk8Bc9A-YYxzTXuA=EbVCya=2J8LeahFsi-RxEDurw-2g@mail.gmail.com>
 <CAHYtTqmv0so08czqo2pYenO=mnW8rWAGbT9mM+kCgtWHdb3Ffg@mail.gmail.com>
 <CAERS1rtmRN=NzSett1d5DzkTKkEMs+N5s6+83Wg31dMhqgLG+g@mail.gmail.com>
 <CAOBL_k7_e1OHKjd1S1vjA+v41-wQjKK_gFfkE-JpWG3wFR5wOQ@mail.gmail.com>
 <1F75B71F-21D3-4998-A488-E85209ECB157@sap.com>
 <CAOBL_k7_idmjs7GKU-3dwa60-KjMPdHdeToxFNogqmu092ocAA@mail.gmail.com>
 <3C2399F1-DACC-462E-87F8-89FF55CF7BBB@pulse-robotics.com>
 <CANpVHHzCvV7CtHjY-dTscW8QLnqhJeC6oZwZp-CEXO8td20baQ@mail.gmail.com>
 <845affbc987030aeb660ff0c10656d5d@services.senegate.at>
 <CAEeF2Tctsm1k+xW6uNE-zX6cojQX4K5P+Gk-WK9jJnFM-ceDbQ@mail.gmail.com>
 <d57b821fd2471240d7b62b75ae549704@services.senegate.at>
 <CAHYtTqnRRoiAnTjPJ8ocuZ6j3xJC2i1GtDD3w=9MkPnT+SSUHA@mail.gmail.com>
 <CAHYtTqnKQPJbuz1dKrLRofDdDtnCpewKXpGnxqkRLgWXghxrAQ@mail.gmail.com>
 <CANpVHHxB9LhVUa8pnoJd7yQ4NoCNGJ=BR58OB0UdP6iagbgZEw@mail.gmail.com>
 <CAPTyS6D1sPiuK5VHONpi1+aRUSO13Sfox75cGay1_k7npy5VqQ@mail.gmail.com>
 <CADVgkyMgvfAmCfoWeFSNboEm4ageArZ_w9HCb6W8=6rqLgbL8Q@mail.gmail.com>
 <6abfc174dffe4e418838c6e8e6337a1c@DBXPR03MB159.eurprd03.prod.outlook.com>
 <2619C1CC-7677-4183-B479-330E3D449B85@redhat.com>
 <CABiQX1UufMs3ijS5MKrkGjJdjN+2m-929dkRT5zPb7+2HMvhzQ@mail.gmail.com>
 <CANpVHHzKhDwk+Ed0W=vdJPTH0xBMh3QMF-q3wdEKpB86g=5xEg@mail.gmail.com>
 <CAEeF2TeY3_VpNbCxK-nBti2BnAGbn2az+qbdXgXt6ExpyAUJdA@mail.gmail.com>
 <CAMSbhBgJW+nMLa152MgzV0fqx4PRve8UgrPYLuWXaGwXM9SL+A@mail.gmail.com>
 <CAMSbhBghgaQm_mBSrxz2MWATdMraK=sN5cRvhA9_VJ7X11OzKA@mail.gmail.com>
 <CAKP6k2vHowNds3qxB+yV7i=Ma2S95Ex+k0TEy1GU6oE5cdus=w@mail.gmail.com>
 <CAMSbhBikEJ1xFcpdE6G6V0Ji9n7QNwLt2RGcixmorC9=fiAKrg@mail.gmail.com>
 <CAEeF2TdubRaOi=UbBT_cmxWUcNZk+mRX9Rg1NN9LpC9ijf7XVQ@mail.gmail.com>
 <CAMSbhBjRmx4HribUCaLAhObA0ptxJMO3V58Cy2d7wtMBC1du+g@mail.gmail.com>
 <CAMSbhBhG1seoagRLBCsEKJZTnbxLRUDm2PFwZjzNU0mEnqKHDQ@mail.gmail.com>
 <CADVgkyMdrYmzs3B2MV41-Yg8yp-H4AGu4GGN7isW9xjZkmOifA@mail.gmail.com>
 <CAHYtTqkEzSqs3td7ndvEuD9NWMa0sQwPPrzRdwY-t=VUXZOGvg@mail.gmail.com>
 <5261fce9.63b6440a.1a95.3dee@mx.google.com>
From: Ian Clelland <iclelland@google.com>
Date: Mon, 21 Oct 2013 09:20:14 -0400
Message-ID: 
 <CAK_TSXJOfkD=75gtVuDcpOUFQY-KZMCmFQ12tFyh-YtaUO7gtw@mail.gmail.com>
Subject: Re: config.xml discussion, we need to talk
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=089e010d8de23fcff904e94026fd

--089e010d8de23fcff904e94026fd
Content-Type: text/plain; charset=UTF-8

Legacy, though, sounds like it's something that we're actively moving away
from; something that we support only grudgingly, and which we might
deprecate at the drop of a hat.
The platform-only workflow supports legitimate use-cases which CLI probably
will never cover -- things like embedding a cordova web view inside of a
larger platform-native project.

The major difference I see with CLI is that it encourages the "Your cordova
web view *IS* your application" mindset. (And if that's true, then why
wouldn't you aim for cross-platform development?) The pre-CLI workflow is
still the way to build all other sorts of applications.

Ian


On Fri, Oct 18, 2013 at 11:30 PM, purplecabbage <purplecabbage@gmail.com>wrote:

> I like merge-flow and legacy-flow
>
> Sent from my iPhone
>
> > On Oct 18, 2013, at 6:59 PM, Carlos Santana <csantana23@gmail.com>
> wrote:
> >
> > Cross Platform -> use Merge Flow
> >
> > Single Platform -> use Legacy Flow
> >
> > Using "Multi Platform or Cross Platform" is also fine
> >
> > Using "Flow or Mode" is also fine
> >
> >
> >> On Friday, October 18, 2013, Brian LeRoux wrote:
> >>
> >> Ya, to me the difference is that one workflow embraces the native
> platform
> >> and tooling (plugman and bin/scripts) while the other focuses on
> building a
> >> web project (cli/merges/etc).
> >>
> >> As a dev, if I'm ONLY worried about one platform (like a Cordova
> >> implementor or many of our community folk) then bin/scripts suffices. As
> >> soon as I'm concerned with more than one platform the CLI workflows kick
> >> in. That was the use case anyhow.
> >>
> >>
> >> On Fri, Oct 18, 2013 at 3:21 PM, Steven Gill <stevengill97@gmail.com>
> >> wrote:
> >>
> >>> Brian suggested Project Development (CLI workflow) vs Platform
> >> Development
> >>> (bin/scripts)
> >>>
> >>>
> >>> On Fri, Oct 18, 2013 at 3:09 PM, Steven Gill <stevengill97@gmail.com>
> >>> wrote:
> >>>
> >>>> We need more suggestions!
> >>>>
> >>>> Anis suggested picking to arbitrary names that don't reflect the
> >>> workflows
> >>>> but would be easy to refer to.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Fri, Oct 18, 2013 at 12:41 PM, Michal Mocny <mmocny@chromium.org
> >>>> wrote:
> >>>>
> >>>>> I use the IDE with the CLI and hope to make it better.
> >>>>>
> >>>>> In my mind, the old way is for making platform modifications, and the
> >>> new
> >>>>> way threads platforms/ as a build artifact.
> >>>>>
> >>>>> If you must control the platform code, you sacrifice easy upgrades
> and
> >>>>> ease
> >>>>> of multi-platform development, but gain control.
> >>>>> If you want to use the CLI, you lose the ability to make
> modifications
> >>> to
> >>>>> directly platform code without worrying about the implications.
> >>>>>
> >>>>> -Michal
> >>>>>
> >>>>>
> >>>>> On Fri, Oct 18, 2013 at 3:18 PM, Steven Gill <stevengill97@gmail.com
> >
> >>>>> wrote:
> >>>>>
> >>>>>> I like that better.
> >>>>>>
> >>>>>> I know that both methods use the command line, but the cordova-cli
> >> has
> >>>>> cli
> >>>>>> in its name! We call the tool the cordova-cli so it might be more
> >>>>> confusing
> >>>>>> going away from that and calling it anything else. Not saying we
> >>>>> shouldn't
> >>>>>> be open to a name change though just because we called it X since
> >> its
> >>>>>> inception (or am I saying that? :P).
> >>>>>>
> >>>>>> When we write the docs about the other workflow (bin/create,
> >> plugman),
> >>>>>> maybe making the IDE an integral part of it would make it make more
> >>>>> sense
> >>>>>> calling that workflow IDE. Just a thought.
> >>>>>>
> >>>>>>
> >>>>>>> On Fri, Oct 18, 2013 at 12:09 PM, Jesse <purplecabbage@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> IDE or cordova-cli ??
> >>>>>>>
> >>>>>>> @purplecabbage
> >>>>>>> risingj.com
> >>>>>>>
> >>>>>>>
> >>>>>>> On Fri, Oct 18, 2013 at 12:02 PM, Steven Gill <
> >>> stevengill97@gmail.com
> >>>>>>>> wrote:
> >>>>>>>
> >>>>>>>> I think SinplePlatform vs MultiPlatform is misleading because
> >> you
> >>>>> can
> >>>>>> use
> >>>>>>>> the CLI to do single platform development.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Fri, Oct 18, 2013 at 11:51 AM, Jesse <
> >> purplecabbage@gmail.com>
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> SinglePlatform vs MultiPlatform makes the most sense to me.
> >>>>>>>>>
> >>>>>>>>> SinglePlatform = Focus on a single platform, and use plugman
> >> and
> >>>>> the
> >>>>>>>>> platform scripts directly. Useful when you only have that
> >>>>> particular
> >>>>>>>> device
> >>>>>>>>> to test on, or only have access to that device's marketplace.
> >>>>> Also
> >>>>>>>> useful
> >>>>>>>>> for platform developers who are focused primarily on the
> >> native
> >>>>> code.
> >>>>>>>>> ( aka DivideAndConquer )
> >
> >
> >
> > --
> > Carlos Santana
> > <csantana23@gmail.com>
>

--089e010d8de23fcff904e94026fd--