I like merge-flow and legacy-flow Sent from my iPhone
> On Oct 18, 2013, at 6:59 PM, Carlos Santana <csantan...@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 <stevengil...@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 <stevengil...@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 <mmo...@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 <stevengil...@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 <purplecabb...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> IDE or cordova-cli ?? >>>>>>> >>>>>>> @purplecabbage >>>>>>> risingj.com >>>>>>> >>>>>>> >>>>>>> On Fri, Oct 18, 2013 at 12:02 PM, Steven Gill < >>> stevengil...@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 < >> purplecabb...@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 > <csantan...@gmail.com>
