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 mmocny@google.com designates
 209.85.214.48 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: 
 <CADVgkyNgUE5C8ZDyVAYro-S36Qt+HHK8__XQWDOjp+Jf+w7-JA@mail.gmail.com>
References: <CD3F2F2E.5FF06%michael.wolf@cynergy.com>
	<CD3FC2D8.17B07%fil@adobe.com>
	<CAEeF2TeFwnr=xheSAD9HRj9SuRPJju3xwk228xZiMLmsCNRETg@mail.gmail.com>
	<CADVgkyNgUE5C8ZDyVAYro-S36Qt+HHK8__XQWDOjp+Jf+w7-JA@mail.gmail.com>
Date: Tue, 12 Feb 2013 13:19:30 -0500
Message-ID: 
 <CAEeF2Te7FxcH_SFFXn=qUzMLwX7_wF53Pe0d_BBfVgpwVfNaVg@mail.gmail.com>
Subject: Re: cordova command cli and merges concept pull request
From: Michal Mocny <mmocny@chromium.org>
To: dev@cordova.apache.org
Content-Type: multipart/alternative; boundary=0015175cb28418424704d58b1191

--0015175cb28418424704d58b1191
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 12, 2013 at 1:11 PM, Brian LeRoux <b@brian.io> wrote:

> Splash screens and making an app a type of super plugin are rad ideas
> for other pull requests. ;)
>
> Attached image of me when idea of making an app a plugin came up.

No you didn't ;)


> On Tue, Feb 12, 2013 at 5:58 PM, Michal Mocny <mmocny@chromium.org> wrote=
:
> > Perhaps this is crazy, but: We already have all this awesome
> functionality
> > for plugins -- would it be impossible to just implement an app as a
> plugin?
> >
> >
> > On Tue, Feb 12, 2013 at 12:59 PM, Filip Maj <fil@adobe.com> wrote:
> >
> >> BTW, Michael love the pull req, but is there any chance you can add
> tests
> >> for it?
> >>
> >> On 2/11/13 8:28 PM, "Michael Wolf" <Michael.Wolf@Cynergy.com> wrote:
> >>
> >> >Hey all:
> >> >
> >> >I submitted a pull request for an enhancement of the addition of a
> merges
> >> >folder/concept into the cli build process.
> >> >
> >> >https://github.com/apache/cordova-cli/pull/3
> >> >
> >> >The concept of merges is pretty simple, to support a common core web
> base
> >> >across platforms, but allow for deploying platform specific www conte=
nt
> >> >to specific platforms.  The addition to the CLI tool adds a new folde=
r
> >> >"merges" to the root level.  Upon running "cordova platforms add|remo=
ve
> >> >platform" a new folder is created under the "merges" folder (ie:
> >> >merges/ios , merges/android etc).  Upon running "cordova buid" any
> >> >content added to this folder will be deployed to the associated www
> >> >folder in the platforms.  This carries for either new content being
> >> >added, or more importantly overrides existing content from the www
> >> >folder.  For a very simple example imagine you have a css file named
> >> >css/chrome.css in the www folder, where you could have .backButton {
> >> >display:block;} , but then under merges/android/css/chrome.css you
> could
> >> >have .backButton{display:none;}, this is a very simplistic use but it
> >> >illustrates the concept. This additional workflow to the build system
> in
> >> >the cli enables some great processes for building a nice clean cordov=
a
> >> >app for example.
> >> >
> >> >
> >> > *   Allows for keeping code clean and limits the need for platform
> >> >specific js logic per platform
> >> > *   Enables a process of mocking in custom plugins for in browser de=
v
> >> >(mocks under www real implementations under merges) , and not risking
> >> >this code filtering into production/device code
> >> > *   Allows for creating platform specific assets such as css / font =
/
> >> >images/ videos etc that only gets merged into the specific desired
> >> >platform
> >> > *   Allows for accepting that each platform is unique and sometimes
> need
> >> >specific logic and or shims,  and always deserves the platform specif=
ic
> >> >love, and the build process should support doing this cleanly
> >> >
> >> >Anywho    =C5=A0.. Would love to see this integrated in.
> >> >
> >> >Thanks
> >> >
> >> >mw
> >>
> >>
>

--0015175cb28418424704d58b1191--