That seems reasonable, thanks for your input guys. One more question that came up on the issue thread is, does the src attrib need to be relative to the www? The concern here being that you will have several megabytes of icon images in your application package that gets used only for specific platforms, and only at compile time. I'm not sure if there is some sort of convention we can come up with here to alleviate this problem (perhaps in the context of using the CLI tools?).
On 3/4/13 10:19 PM, "Andrew Grieve" <agri...@chromium.org> wrote: >I think we should plan for having all users using CLI. It really is a bit >step forward. So... option b) is what sounds good to me. If users don't >want to use CLI, then they shouldn't use the <icon> tag, and just update >the asset in the native spots manually. > > >On Mon, Mar 4, 2013 at 1:18 PM, Joe Bowser <bows...@gmail.com> wrote: > >> This is compile-time, so I think that the CLI tool should take >> responsibility for compile-time attributes. Per-platform CLI is >> already virtually unmaintainable as it is. >> >> On Mon, Mar 4, 2013 at 10:13 AM, Filip Maj <f...@adobe.com> wrote: >> > I've set up a parent issue to track progress [1]. >> > >> > Since this is a compile-time property, how would we go about >>supporting >> it >> > across all platforms? I'm thinking either a) need to add logic into >>each >> > platform's CLI scripts to parse the contents of config.xml, >>grab/verify >> > icon assets, copy them over into appropriate place or b) move that >> > responsibility into the CLI tool, but then we'd need extra >>documentation >> > on how to update the icon on a per-platform basis in case users are >>not >> > using the cli tools. >> > >> > Thoughts/questions/comments? >> > >> > [1] https://issues.apache.org/jira/browse/CB-2606 >> > >>
