You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Michal Mocny <mm...@google.com> on 2014/05/14 16:33:34 UTC
Can we remove merges/ folder from the default application template?
I'm not proposing we drop support for merges/, I just think that many apps
don't use it so why show it by default? (We've done something similar for
.cordova/ where its still supported but not created by default unless it
actually has non-default values)
The way merges/ works right now is questionably useful (Michael Brooks had
a long post about that a while ago), and with hooks/ most apps can create a
much better alternative for themselves.
So, not a big deal, but one fewer thing to learn for new devs, and less
temptation for them to try using it..
WDYT?
-Michal
Re: Can we remove merges/ folder from the default application template?
Posted by Michael Brooks <mi...@michaelbrooks.ca>.
+1 with Marcel's suggestions.
I've never liked the merges directory myself, but if others find it useful
that's great. I would be happy to see it as an opt in feature.
On Wed, May 14, 2014 at 11:58 AM, Brian LeRoux <b...@brian.io> wrote:
> +1!
>
>
> On Wed, May 14, 2014 at 9:32 AM, Marcel Kinard <cm...@gmail.com> wrote:
>
> > SGTM as long as all the user needs to do to recreate it is a “mkdir”, and
> > that is documented in all the right places. I like the aim of reducing
> the
> > temptation of devs to push buttons that aren’t needed in most cases. The
> > visible surface area is more simple.
> >
> > On May 14, 2014, at 10:33 AM, Michal Mocny <mm...@google.com> wrote:
> >
> > > I'm not proposing we drop support for merges/, I just think that many
> > apps
> > > don't use it so why show it by default? (We've done something similar
> > for
> > > .cordova/ where its still supported but not created by default unless
> it
> > > actually has non-default values)
> > >
> > > The way merges/ works right now is questionably useful (Michael Brooks
> > had
> > > a long post about that a while ago), and with hooks/ most apps can
> > create a
> > > much better alternative for themselves.
> > >
> > > So, not a big deal, but one fewer thing to learn for new devs, and less
> > > temptation for them to try using it..
> > >
> > > WDYT?
> > >
> > > -Michal
> >
> >
>
Re: Can we remove merges/ folder from the default application template?
Posted by Brian LeRoux <b...@brian.io>.
+1!
On Wed, May 14, 2014 at 9:32 AM, Marcel Kinard <cm...@gmail.com> wrote:
> SGTM as long as all the user needs to do to recreate it is a “mkdir”, and
> that is documented in all the right places. I like the aim of reducing the
> temptation of devs to push buttons that aren’t needed in most cases. The
> visible surface area is more simple.
>
> On May 14, 2014, at 10:33 AM, Michal Mocny <mm...@google.com> wrote:
>
> > I'm not proposing we drop support for merges/, I just think that many
> apps
> > don't use it so why show it by default? (We've done something similar
> for
> > .cordova/ where its still supported but not created by default unless it
> > actually has non-default values)
> >
> > The way merges/ works right now is questionably useful (Michael Brooks
> had
> > a long post about that a while ago), and with hooks/ most apps can
> create a
> > much better alternative for themselves.
> >
> > So, not a big deal, but one fewer thing to learn for new devs, and less
> > temptation for them to try using it..
> >
> > WDYT?
> >
> > -Michal
>
>
Re: Can we remove merges/ folder from the default application template?
Posted by Marcel Kinard <cm...@gmail.com>.
SGTM as long as all the user needs to do to recreate it is a “mkdir”, and that is documented in all the right places. I like the aim of reducing the temptation of devs to push buttons that aren’t needed in most cases. The visible surface area is more simple.
On May 14, 2014, at 10:33 AM, Michal Mocny <mm...@google.com> wrote:
> I'm not proposing we drop support for merges/, I just think that many apps
> don't use it so why show it by default? (We've done something similar for
> .cordova/ where its still supported but not created by default unless it
> actually has non-default values)
>
> The way merges/ works right now is questionably useful (Michael Brooks had
> a long post about that a while ago), and with hooks/ most apps can create a
> much better alternative for themselves.
>
> So, not a big deal, but one fewer thing to learn for new devs, and less
> temptation for them to try using it..
>
> WDYT?
>
> -Michal
Re: Can we remove merges/ folder from the default application template?
Posted by Brian LeRoux <b...@brian.io>.
ya I like the idea of making these things discoverable, not incurring the
cognitive overhead during on boarding, and clean path to remove (or
extract) if we so wish
we really should require a ./tests (or ./specs) folder
On Fri, May 16, 2014 at 12:47 PM, Michal Mocny <mm...@chromium.org> wrote:
> I think thats the point.
>
>
> On Fri, May 16, 2014 at 8:05 AM, Wargo, John <jo...@sap.com> wrote:
>
> > I wouldn't - without it there new devs simply wouldn't know the option
> > even exists.
> >
> > John M. Wargo
> > Twitter: @johnwargo
> >
> >
> > -----Original Message-----
> > From: Michal Mocny [mailto:mmocny@google.com]
> > Sent: Wednesday, May 14, 2014 10:34 AM
> > To: dev
> > Subject: Can we remove merges/ folder from the default application
> > template?
> >
> > I'm not proposing we drop support for merges/, I just think that many
> apps
> > don't use it so why show it by default? (We've done something similar
> for
> > .cordova/ where its still supported but not created by default unless it
> > actually has non-default values)
> >
> > The way merges/ works right now is questionably useful (Michael Brooks
> had
> > a long post about that a while ago), and with hooks/ most apps can
> create a
> > much better alternative for themselves.
> >
> > So, not a big deal, but one fewer thing to learn for new devs, and less
> > temptation for them to try using it..
> >
> > WDYT?
> >
> > -Michal
> >
>
Re: Can we remove merges/ folder from the default application template?
Posted by Michal Mocny <mm...@chromium.org>.
https://issues.apache.org/jira/browse/CB-6709
As I went about changing this, I realized the way we create default apps
should probably be changed to use use --copy-from with the hello-world app.
Doing so would mean we import www/ hooks/ merges/ and config.xml from
there, instead of custom handling the default case and pre-populating the
directories from custom locations. So I also filed
https://issues.apache.org/jira/browse/CB-6710
On Fri, May 16, 2014 at 3:47 PM, Michal Mocny <mm...@chromium.org> wrote:
> I think thats the point.
>
>
> On Fri, May 16, 2014 at 8:05 AM, Wargo, John <jo...@sap.com> wrote:
>
>> I wouldn't - without it there new devs simply wouldn't know the option
>> even exists.
>>
>> John M. Wargo
>> Twitter: @johnwargo
>>
>>
>> -----Original Message-----
>> From: Michal Mocny [mailto:mmocny@google.com]
>> Sent: Wednesday, May 14, 2014 10:34 AM
>> To: dev
>> Subject: Can we remove merges/ folder from the default application
>> template?
>>
>> I'm not proposing we drop support for merges/, I just think that many apps
>> don't use it so why show it by default? (We've done something similar for
>> .cordova/ where its still supported but not created by default unless it
>> actually has non-default values)
>>
>> The way merges/ works right now is questionably useful (Michael Brooks had
>> a long post about that a while ago), and with hooks/ most apps can create
>> a
>> much better alternative for themselves.
>>
>> So, not a big deal, but one fewer thing to learn for new devs, and less
>> temptation for them to try using it..
>>
>> WDYT?
>>
>> -Michal
>>
>
>
Re: Can we remove merges/ folder from the default application template?
Posted by Michal Mocny <mm...@chromium.org>.
I think thats the point.
On Fri, May 16, 2014 at 8:05 AM, Wargo, John <jo...@sap.com> wrote:
> I wouldn't - without it there new devs simply wouldn't know the option
> even exists.
>
> John M. Wargo
> Twitter: @johnwargo
>
>
> -----Original Message-----
> From: Michal Mocny [mailto:mmocny@google.com]
> Sent: Wednesday, May 14, 2014 10:34 AM
> To: dev
> Subject: Can we remove merges/ folder from the default application
> template?
>
> I'm not proposing we drop support for merges/, I just think that many apps
> don't use it so why show it by default? (We've done something similar for
> .cordova/ where its still supported but not created by default unless it
> actually has non-default values)
>
> The way merges/ works right now is questionably useful (Michael Brooks had
> a long post about that a while ago), and with hooks/ most apps can create a
> much better alternative for themselves.
>
> So, not a big deal, but one fewer thing to learn for new devs, and less
> temptation for them to try using it..
>
> WDYT?
>
> -Michal
>
RE: Can we remove merges/ folder from the default application
template?
Posted by "Wargo, John" <jo...@sap.com>.
I wouldn't - without it there new devs simply wouldn't know the option even exists.
John M. Wargo
Twitter: @johnwargo
-----Original Message-----
From: Michal Mocny [mailto:mmocny@google.com]
Sent: Wednesday, May 14, 2014 10:34 AM
To: dev
Subject: Can we remove merges/ folder from the default application template?
I'm not proposing we drop support for merges/, I just think that many apps
don't use it so why show it by default? (We've done something similar for
.cordova/ where its still supported but not created by default unless it
actually has non-default values)
The way merges/ works right now is questionably useful (Michael Brooks had
a long post about that a while ago), and with hooks/ most apps can create a
much better alternative for themselves.
So, not a big deal, but one fewer thing to learn for new devs, and less
temptation for them to try using it..
WDYT?
-Michal