You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@weex.apache.org by "erha19 (JIRA)" <ji...@apache.org> on 2017/11/06 13:00:04 UTC
[jira] [Commented] (WEEX-85) Improve the Weextoolkit's experience
and add new features
[ https://issues.apache.org/jira/browse/WEEX-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240247#comment-16240247 ]
erha19 commented on WEEX-85:
----------------------------
Last week I decided not to carry out `weex-lint` function development, the main reason is divided into the following two points:
# For equipment running information needs to be simulated in the real machine, the use of tools cannot simulate the real environment, can not test the real machine running problems. If you need to invest in development efforts, your output may not meet the expectations you expect.
# The basic script's static checking tool can only check the format and the validity of the reference, and there are many lint tools in the front end such as eslint, which feels like we do not need the existing eslint to support the above functions.
It is exciting that weex-devtool 2.0 has been basically developed, you can experience the latest version weex devtool the commands below:
```
npm i weex-toolkit@latest -g
weex xbind debugx weex-debugger
weex debugx
```
There are some new feature on the new weex devtool.
# Consolidated inspector and runtime log information;
# More intuitive and refreshing debugging interface and performance;
# I18n support is provided
# Provide performance analysis tools
The package is published as name of [weex-debugger](https://www.npmjs.com/package/weex-debugger), after full testing it will be upgraded on the next version of weex-devtool.
> Improve the Weextoolkit's experience and add new features
> ---------------------------------------------------------
>
> Key: WEEX-85
> URL: https://issues.apache.org/jira/browse/WEEX-85
> Project: Weex
> Issue Type: Improvement
> Components: Project
> Reporter: erha19
> Assignee: zhengshihan
>
> The new version of the weex-toolkit will support some of the following features:
> - weex-lint plugin
> - weex-devtool 2.0
> The `weex-lint` is a plugin for weex detects whether the syntax is normative and whether there is a runtime error.and a common fix.
> The `weex-devtool 2.0` is an upgrade version of `weex-devtool`, the upgrade version will rewrite the message storeroom of `weex-devtool`, unify the logger and inspector log information, provide a more beautiful interface and lower operating costs, and also The performance data provided by the weex module provides the developer with a page optimization basis.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Re: [jira] [Commented] (WEEX-85) Improve the Weextoolkit's experience
and add new features
Posted by Drew Hansen <fa...@gmail.com>.
After some time using the development tools, I collected some new and
useful functional requirements of weex-devtool：
1. Provide support for weex storage management.
2. Provide compile-time performance data optimization recommendations of
weex project.
3. Provide run-time performance data optimization recommendations.
4. Provides the ability to collect and show fps, network, cpu, memory data.
Please give your comments if any.
2017-11-06 21:00 GMT+08:00 erha19 (JIRA) <ji...@apache.org>:
>
> [ https://issues.apache.org/jira/browse/WEEX-85?page=com.
> atlassian.jira.plugin.system.issuetabpanels:comment-
> tabpanel&focusedCommentId=16240247#comment-16240247 ]
>
> erha19 commented on WEEX-85:
> ----------------------------
>
> Last week I decided not to carry out `weex-lint` function development, the
> main reason is divided into the following two points:
>
> # For equipment running information needs to be simulated in the real
> machine, the use of tools cannot simulate the real environment, can not
> test the real machine running problems. If you need to invest in
> development efforts, your output may not meet the expectations you expect.
> # The basic script's static checking tool can only check the format and
> the validity of the reference, and there are many lint tools in the front
> end such as eslint, which feels like we do not need the existing eslint to
> support the above functions.
>
>
> It is exciting that weex-devtool 2.0 has been basically developed, you can
> experience the latest version weex devtool the commands below:
>
> ```
> npm i weex-toolkit@latest -g
> weex xbind debugx weex-debugger
> weex debugx
> ```
>
> There are some new feature on the new weex devtool.
>
> # Consolidated inspector and runtime log information;
> # More intuitive and refreshing debugging interface and performance;
> # I18n support is provided
> # Provide performance analysis tools
>
> The package is published as name of [weex-debugger](https://www.
> npmjs.com/package/weex-debugger), after full testing it will be upgraded
> on the next version of weex-devtool.
>
> > Improve the Weextoolkit's experience and add new features
> > ---------------------------------------------------------
> >
> > Key: WEEX-85
> > URL: https://issues.apache.org/jira/browse/WEEX-85
> > Project: Weex
> > Issue Type: Improvement
> > Components: Project
> > Reporter: erha19
> > Assignee: zhengshihan
> >
> > The new version of the weex-toolkit will support some of the following
> features:
> > - weex-lint plugin
> > - weex-devtool 2.0
> > The `weex-lint` is a plugin for weex detects whether the syntax is
> normative and whether there is a runtime error.and a common fix.
> > The `weex-devtool 2.0` is an upgrade version of `weex-devtool`, the
> upgrade version will rewrite the message storeroom of `weex-devtool`,
> unify the logger and inspector log information, provide a more beautiful
> interface and lower operating costs, and also The performance data provided
> by the weex module provides the developer with a page optimization basis.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.14#64029)
>