Hello Yongsheng. Thanks for your feedback.

On 29 November 2013 01:40, Zhu, Yongsheng <yongsheng....@intel.com> wrote:

> 1)       Is it possible to use this for both Android and Tizen ports? I
> believe it’s important.
>

I have concentrated on producing apk files in the first instance. To
support Tizen packages, I would probably write a different tool, either to
generate apk files from a neutral cross-platform manifest format, or
perhaps to convert xpk to apk. I am not really sure which way Crosswalk
packaging is going, so I went with the format which I feel is a high
priority right now (apks for Crosswalk for Android).


> 2)       Could you please explain a little bit more about grunt and
> related tools? I know it’s used widely for 01.org web apps.  If possible,
> it’ll be appreciated if you can write a document to describe how it works
> technically.
>

grunt is a build tool, similar in intent to ant, rake or make, but far less
powerful and flexible. However, it is fairly easy to extend and understand,
and implemented in JavaScript, which add to its appeal for web developers.

The grunt documentation is pretty thorough and should tell you everything
you want to know: http://gruntjs.com/getting-started


> 3)       I suggest to use JIRA to track all of these items.
>

This project is not currently a formal part of Crosswalk. I have yet to
find the right location for it, and am debating it with the relevant
parties.


> 4)       According to my experience, it’s better to split your task into
> several PRs instead of working out a big solution(patch) internally. We can
> review them one by one and provide feedbacks.
>

I don't intend to implement this as part of Crosswalk itself. Having
packaging code embedded in the Crosswalk source code makes it inaccessible,
difficult to manage, and inconvenient to work on. Splitting the tools for
creating packages from the main source tree for Crosswalk is part of what
I'm proposing.

So I suggest creating a separate standalone project specifically for
xwalk-apk-generator, and managing it via github (including its issue
tracking). Which means that I can't make PRs with patches, as this is
really a parallel effort which sits outside Crosswalk. Whether it is part
of the crosswalk-project github or not is open to debate.

Elliot
-- 
Elliot Smith
Senior Software Engineer
Intel Open Source Technology Centre
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

Reply via email to