On 20 January 2014 07:57, Wu, Donna <donna...@intel.com> wrote: > Currently, I have initialized an Eclipse plugin that including > create and export Crosswalk project. There is no overlap with current > packaging tools both by python and node.js because I just invoked python > packaging tool in the plugin. In the future, if the default packaging tool > move to node.js version we just need to change the invoked tools. > On the other hand, we want to extend capability of the plugin in > future, including exporting XPK package for Tizen or other targets based on > the command-line tools, like make_xpk.py. > So, in this way, we are integrating all the command-line tools > together, expanding the use scenarios of the command-line tools, no doing > the repeated work. In the developing process, we can help to improve the > command-line tools, because we are using the tools in different ways. >
As Donna states, the Eclipse plugin is built on top of any existing command line tools (make_apk.py at the moment, as this is the official tool). This sounds sensible to me. Providing the interfaces to the command line tool are cleanly separated from the Eclipse-specific code, it should be relatively easy to change the underlying command line tools (the stuff I've been working on is mostly backwards-compatible with make_apk.py anyway). As for the tools I've been working on, they are "complete" (usable and working), but just for canary Crosswalk. My plan in the longer term is to make releases which are specific to particular Crosswalk versions, rather than compatible with all Crosswalk versions at once. 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
