Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates
 64.18.1.33 as permitted sender)
From: Filip Maj <fil@adobe.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Date: Fri, 9 Aug 2013 11:42:40 -0700
Subject: Re: icons, splash and hooks
Thread-Topic: icons, splash and hooks
Thread-Index: Ac6VMDwLxtwDTemZTemZERPDTJZzbA==
Message-ID: <CE2A7EC5.23B68%fil@adobe.com>
In-Reply-To: <CB3E39AA-90AA-48B9-9FFC-463F91F957AF@apla.me>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.3.5.130515
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hey guys,

Thanks for kicking this thread off. Lots of good stuff here.

First: there are several issues in our JIRA covering icon and splash
screen support. Most of the discussion has happened under the
<icon>-specific issue [1], and I think pretty much everything discussed
about <icon>s applies to <splashscreen>s. Right now: there is no good
support in cordova for icon and splash screens.

Michael: thank you for the pull request to add icon and splash screen
support. I have a bunch of comments:

1. Adding imagemagick as a dependency is probably a bad idea. Does it
build fine on OSX, Linux and Windows? I have my doubts, given my prior
experience with this tool.
2. I am not sure we want to do image processing at all to enable icon and
splash support. Based on [1], it sounds like an explicit enumeration of
particular icon/splash files with particular sizes (to be adapted
appropriately for the varying platforms we support) is the way we are
going with this feature. I encourage everyone to please check out [1],
read through the ideas described in that JIRA issue, and continue
discussion on that issue. Once a general approach to the problem is
identified and agreed on, we can employ the same strategy for splash
screens.
3. It seems like manifest-wise, Michael, you are following what PhoneGap
build has done to add support for icons. While that is nice, it is not the
way the standards are going for application manifests (in fact, XML isn't
the way the standards are going). Again, refer to [1] for discussion on
different ways to implement that.

Ivan, regarding your second point about hooks, I totally agree. We have an
issue filed to enable generic parameter passing to command-line hooks [2].

Ivan, regarding your third point, I don't think that would work out on
windows, will it? Shebangs or whatever you call them? Alternatively: have
a .bat file on windows that invokes node or whatever interpreter you wrote
your scripts in.

[1] https://issues.apache.org/jira/browse/CB-2606
[2] https://issues.apache.org/jira/browse/CB-4382

On 8/8/13 1:16 AM, "Ivan Baktsheev" <owner@apla.me> wrote:

>hello
>
>i have some projects which i want to migrate from cordova 2.x to cordova
>3.0. i'm very happy with the project format change and cordova cli, but
>some issues are very frustrating.
>
>1) icons and splash screens won't copy from res folder
>
>i created an after_prepare hook script
>(https://gist.github.com/apla/6179863) and assets go to the proper
>folders. probably, this can be added to the cordova cli. are there any
>reasons not to include this functionality into cordova?
>
>but this added other two issues:
>
>2) hook scripts know nothing about current command platform. for example,
>when i run "cordova prepare ios" i don't need assets from android copied.
>i propose to make a hook script reading an environment or the second
>command line parameter to get a current platform, would that work?
>
>3) hook is not running on windows, and i have to rename my hook to
>"something.js", windows will run this script via cscript.exe. i think,
>cordova could read the first line of a script file (#!/bin/env node) and
>launch a proper command, or interpret every hook on windows as a nodejs
>script; in this case we would be able to get cross-platform hooks.
>
>thank you!
>