+1 for dropping them in merges/
On Thu, Jul 25, 2013 at 8:51 AM, Braden Shepherdson <[email protected]> wrote: > Setting them up, at least in the default app for cli, in merges/ makes > sense to me. That's the right thing to do, and we want to encourage it. > > Braden > > > On Thu, Jul 25, 2013 at 7:06 AM, Tommy-Carlos Williams > <[email protected]>wrote: > >> Agreed. >> >> It's the difference between a 7-8MB app and a 1MB app on Android for >> example. >> >> I have moved mine out into merges, personally… so only iOS gets the iOS >> splash screens, etc. >> >> Then I use a hook to copy them into the correct file names to be used in >> the app. >> >> - tommy >> >> >> On 24/07/2013, at 10:51 PM, Darryl Pogue <[email protected]> wrote: >> >> > On Wed, Jul 24, 2013 at 10:24 PM, Filip Maj <[email protected]> wrote: >> > >> >> How should we proceed? Close as Not A Problem? On the one hand this is a >> >> userspace problem, on the other we're doing not doing a good job of >> >> encouraging sound engineering. >> >> >> >> What about having the default app have the right types of merges/ >> >> overrides? >> >> >> >> Thoughts? >> >> >> > >> > I had raised a point about this back when there was some discussion about >> > icons >> > being specified in config.xml[1]. >> > >> > Apparently discussion moved to the mailing list, but I don't think there >> > were >> > any conclusions. >> > >> > The issue really isn't that this project includes all these >> splash-screens >> > and >> > icons, but rather that they're in the www folder and end up getting >> copied >> > into >> > each platform's assets. >> > >> > [1] >> > >> https://issues.apache.org/jira/browse/CB-2606?focusedCommentId=13593067&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13593067 >> >>
