Hi! Thank you very much!
Initially I dismissed weex-toolkit just because weexpack had more activity on github :). Now that I took a closer look, I see that weex-toolkit basically provides an aggregated API for different weex tools. Cheers! Tiago On Wed, 15 Mar 2017 at 00:40 Wenhong Wu <[email protected]> wrote: > 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 > > >
