Thanks for your comments. 1. yes, weex "init" and "create" has different purpose at the very beginning, "init" was used to quickly setup H5 project for frontend engineer, while "create" would create a complete project with native files. These two commands will be consolidate to have same result in near future.
2. We started to use Vue from Jan this year. But tools haven't fully support vue yet. Next formal release in near future, vue will be supported by default, and .we project would be supported with option like "--type=we" as maintenance. Thanks for your cool advices. If you interested, pls refer to "vue2.0" branch in weexpack project. Your contribution was warmly welcomed. Thanks On Mon, Mar 20, 2017 at 10:48 PM, Tiago Alves <[email protected]> wrote: > Thanks for the replies! > > I am glad to see the tools being bundled into one! Can someone help me with > the following doubts? > > 1) When we create a vue project (`weex init my-project`) then we cannot add > the native platforms (`weex platform add android`). This seems to work > exclusively with "weex projects" (`weex create my-project`), the type that > still uses .we files. > > I have searched all the branches in the weexpack project and couldn't find > a way to add native platforms to a "vue project". > Is there someone working on this? If so, where? If not, should I contribute > directly to the weexpack project, or that discussion should occur here? > > 2) I think that the commands `weex init` and `weex create` are there mostly > for historical reasons, but will be confusing for the developer. How about > adding a parameter to `weex init` so it canl create a legacy .we project? > E.g. `weex init my-project --type=we` would do the same as `weex create > my-project`. > > Thanks in advance. I apologise if this discussion should be occurring > elsewhere. In that case, please redirect me to the right place :) > > Tiago > > > > On Mon, 20 Mar 2017 at 06:48 蒲欢(拈笑) <[email protected]> wrote: > > > We have > > recently sorted out our tools. > > Weex-toolkit > > are playing an import role in out development chain.Developers > > doesn't care about weexpack or weex-devtools. You could create, debug and > > build > > a Weex project via one cli command tool: > > weex-toolkit(https://github.com/weexteam/weex-toolkit). > > > > And we > > have updated some details about weex-toolkit, just go > > https://weex.apache.org/guide/tools/toolkit.html > > to have a deep understanding about weex-toolkit. > > ------------------------------------------------------------ > ------发件人：Wenhong > > Wu <[email protected]>发送时间：2017年3月15日(星期三) 11:40收件人：dev < > > [email protected]>主 题：Re: Sorting out Weex APIs and tools > > Hi, Tiago, > > > > Thanks for your valuable points. > > Weex cli command has just unified to toolkit, which means you don't need > to > > use weexpack or devtool separately. All comes to a simple way, after npm > > install weex-toolkit. You just call weexpack subcommand after weex like > > "weex create xxx" "weex platform add XXX" "weex run xxx"...which will > > automatically launch and execute weexpack. The same happens to > > weex-devtool, you call "weex debug xxx" instead of "weex-devtool xxx". > > For details, pls refer to https://github.com/weexteam/weex-toolkit. And > > we're now working on official toolchain document, try giving weex > > development an easy experience. > > Pls feel free to comments or submit issues in toolkit github :) > > > > Thanks > > > > On Wed, Mar 15, 2017 at 12:58 AM, sospartan <[email protected]> > wrote: > > > > > > > I'm totally agree with you. The weex tooling is confusing, even for > me, as > > > a team member, use/dev weex everyday. > > > > > > I'd like in some day, we can use one single tool to manage all these > > > things. > > > > > > This thread may take some time for rest of team, since it's midnight in > > > china. 😅 > > > > > > Thanks for the feedback. > > > > > > Tiago Alves <[email protected]>于2017年3月14日 周二下午9:40写道： > > > > > > Hello all! > > > > > > I am a newcomer that is still trying to wrap his head around the > project. > > > And hey, maybe it's good thing to have an outsider's perspective! > > > > > > After some days experimenting with Weex, the Hackernews project, > weexpack > > > and weex-toolkit, I still have this question: How will people use Weex > in > > > the future? The success of open source projects depends more on the > > > developer experience (that includes APIs, docs and tools) than the > > > technical quality of the solution. > > > > > > So my question is: where are we heading? As far as I could learn from > the > > > docs, the workflow would be: > > > > > > 1. Create the app: > > > > weexpack create my-project // weexpack > > > or > > > > weex create my-project // weex-toolkit > > > or > > > > vue init weex my-project // vue-cli > > > ? > > > > > > 2. Configure native platforms in the config.xml > > > > > > 3. Add platforms > > > > weexpack platform add android/ios // weexpack > > > or > > > > weex platform add android/ios // weex-toolkit > > > ? > > > > > > 4. Debug platforms using weex-toolkit: > > > > weex debug dist/index.weex.js > > > > > > 5. Run/deploy natively: > > > > weexpack platform run > > > > > > I would like to see 3 things happening to this project: > > > 1) A definition of the experience we want for the developer. > > > > > 2) weexpack and weex-toolkit should have a clearer scope. Their docs > should > > > > > have a distinction of what is deprecated, with special care for > overlapping > > > features. > > > 3) A "getting started" doc that guides the developer from 0 to having a > > > Vue2.0 Weex debuggable app. > > > > > > > > Weex is under heavy development and I get that. The worrying part is > that I > > > don't see where Weex's developer experience is heading to. > > > > > > So, how will developers us weex in the future? > > > > > > Thanks! > > > Tiago > > > > > > -- > > > sospartan > > > https://weex-project.io > > > > > >
