Hi!
I have noticed that many people drive away from weex because there is still
no clear, fully-working path to create a Weex project from scratch.
I took a shot at contributing to that part some weeks ago but had to stop
due to lack of time (or skill? :P).
This is what I know:
- Weex-toolkit (weex's cli) is, in a big part, a copy of the cordova-cli
implementation;
- Weex-toolkit platform add commands just copies a template to the
project, and does not make all the transformations that the cordova-cli
does, such as:
- change the path names according to the project name;
- change the package names/folders in android according to the appID;
- change some file names according to the appId/bundleID in
android/iOS;
- change class names and other bits of code in the android/iOS
project to match the app name.
I would like weex-toolkit add platform commands to create a properly
configured project, with the correct name, bundle id, paths, namespaces,
etc. And I am ready to dive into it again!
So I have some questions:
- Is anyone working on that? Someone I could join in this? Anyone wants
to join me?
- Mirroring the cordova implementation seemed a very smart move to get
with something working fast, but now it seems to me that it is an
over-engineered solution. Cordova is an old-ish project, and its cli
clearly had too many iteractions. I looked into the NativeScript cli (tns)
and it feels much more modern and fresh. Wouldn't it be a good idea to
start a weex-toolkit from scratch?
- I created a vue-cli template for weex (
https://github.com/tralves/weex-vue) that sets some variables and
configurations. I think it could be a good solution to have users bootstrap
the project with the vue-cli they already know and love, and then use the
weex-toolkit to work with the native and weex details.
What are your thoughts?
Thanks!
Tiago
