[jira] [Commented] (WEEX-75) [Vote] change weex branch flow
[ https://issues.apache.org/jira/browse/WEEX-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183610#comment-16183610 ] Adam Feng commented on WEEX-75: --- +1 > [Vote] change weex branch flow > -- > > Key: WEEX-75 > URL: https://issues.apache.org/jira/browse/WEEX-75 > Project: Weex > Issue Type: Wish > Components: Project >Reporter: Zechang Xie >Assignee: sospartan > > Dear All weex developers, >I suggest that changing weex branch flow for better communication: >* make master as main branch, that we can see develop process clearly; > previously we develop at branch named 0.XX-dev; >* make release as publish branch,that we can release version at it; >* delete extra branches like dev,0.16-dev and so on; > Please reply this emali to vote for this suggestion, thanks. > reply +1 as agree. > reply -1 as disagree. > reply 0 as no-idea. > Best Wishes! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-75) [Vote] change weex branch flow
[ https://issues.apache.org/jira/browse/WEEX-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185584#comment-16185584 ] Adam Feng commented on WEEX-75: --- If it is passed, please be sure to make a pull request to change the branch management of CONTRIBUTING.md, thanks. > [Vote] change weex branch flow > -- > > Key: WEEX-75 > URL: https://issues.apache.org/jira/browse/WEEX-75 > Project: Weex > Issue Type: Wish > Components: Project >Reporter: Zechang Xie >Assignee: sospartan > > Dear All weex developers, >I suggest that changing weex branch flow for better communication: >* make master as main branch, that we can see develop process clearly; > previously we develop at branch named 0.XX-dev; >* make release as publish branch,that we can release version at it; >* delete extra branches like dev,0.16-dev and so on; > Please reply this emali to vote for this suggestion, thanks. > reply +1 as agree. > reply -1 as disagree. > reply 0 as no-idea. > Best Wishes! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (WEEX-75) [Vote] change weex branch flow
[ https://issues.apache.org/jira/browse/WEEX-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185584#comment-16185584 ] Adam Feng edited comment on WEEX-75 at 9/29/17 9:44 AM: If it is passed, please be sure to make a pull request to change the branch management part of CONTRIBUTING.md, thanks. was (Author: cxfeng): If it is passed, please be sure to make a pull request to change the branch management of CONTRIBUTING.md, thanks. > [Vote] change weex branch flow > -- > > Key: WEEX-75 > URL: https://issues.apache.org/jira/browse/WEEX-75 > Project: Weex > Issue Type: Wish > Components: Project >Reporter: Zechang Xie >Assignee: sospartan > > Dear All weex developers, >I suggest that changing weex branch flow for better communication: >* make master as main branch, that we can see develop process clearly; > previously we develop at branch named 0.XX-dev; >* make release as publish branch,that we can release version at it; >* delete extra branches like dev,0.16-dev and so on; > Please reply this emali to vote for this suggestion, thanks. > reply +1 as agree. > reply -1 as disagree. > reply 0 as no-idea. > Best Wishes! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (WEEX-34) Update csslayout to Yoga
[ https://issues.apache.org/jira/browse/WEEX-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-34. - Resolution: Won't Fix No need to upgrade Yoga anymore > Update csslayout to Yoga > > > Key: WEEX-34 > URL: https://issues.apache.org/jira/browse/WEEX-34 > Project: Weex > Issue Type: Task >Reporter: sospartan > > Weex bundle old csslayout source code, which is out of date. > The library is renamed to 'yoga'. > In android side, it's provided jcenter artifacts: > > https://bintray.com/facebook/maven/com.facebook.yoga%3Ayoga > latest version is 1.4.2 > After change to remote dependency, source code under > 'android/sdk/src/main/java/com/taobao/weex/dom/flex' could be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-67) ios SDK 0.13.0
[ https://issues.apache.org/jira/browse/WEEX-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-67. --- Resolution: Fixed > ios SDK 0.13.0 > -- > > Key: WEEX-67 > URL: https://issues.apache.org/jira/browse/WEEX-67 > Project: Weex > Issue Type: Bug >Reporter: Mr.Dragonn >Assignee: sospartan > Attachments: 2621772495-599fbe19b5b07_articlex.png > > Original Estimate: 96h > Remaining Estimate: 96h > > ios SDK升级到0.13.0以后 运行程序就会报错 > 我们项目是从weex0.3.0的版本就开始用,当时还不支持cocoapods 所以只能在本地通过 > pod 'WeexSDK', :path=>'./sdk/' > 引用 > 而且我们还在原来的SDK基础上做了一些改动(例如text选中动画效果等...),所以需要用到SDK中的源文件,现在直接使用cocoapods来引用的时候开放出来的头文件中没有我们进行修改的头文件.在0.12.0版本以前我们还是将SDK文件下载到本地 > 然后引入到工程来使用,但是在0.13.0开始,引入SDK后就出现各种错误 > 现在下载0.16.0引入到项目中 > 执行pod 'WeexSDK', :path=>'./sdk/' > 结果文件夹下没有weex文件 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-64) Upgrade to API 25
[ https://issues.apache.org/jira/browse/WEEX-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-64: - Assignee: Adam Feng (was: sospartan) > Upgrade to API 25 > - > > Key: WEEX-64 > URL: https://issues.apache.org/jira/browse/WEEX-64 > Project: Weex > Issue Type: New Feature >Reporter: YorkShen >Assignee: Adam Feng > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-64) Upgrade to API 25
[ https://issues.apache.org/jira/browse/WEEX-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-64. --- Resolution: Fixed > Upgrade to API 25 > - > > Key: WEEX-64 > URL: https://issues.apache.org/jira/browse/WEEX-64 > Project: Weex > Issue Type: New Feature >Reporter: YorkShen >Assignee: Adam Feng > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-74) commit-msg in git hook should allow user to submit commit with title [WEEX-xxx]
[
https://issues.apache.org/jira/browse/WEEX-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng reassigned WEEX-74:
-
Assignee: (was: sospartan)
> commit-msg in git hook should allow user to submit commit with title
> [WEEX-xxx]
> ---
>
> Key: WEEX-74
> URL: https://issues.apache.org/jira/browse/WEEX-74
> Project: Weex
> Issue Type: Improvement
> Components: Project
>Reporter: Jonathan Dong
>Priority: Minor
>
> According to the current commit log policy, people can only submit commit
> with the title:
> {action} [{module}] {description}
> more details can be found
> [here](https://github.com/apache/incubator-weex/blob/master/CONTRIBUTING.md#commit-log)
> As we decided to re-adopt Apache's Jira to track project's bugs and features,
> we hope we can use the auto-correlation feature to automatically connect
> commit with Jira issue by setting your commit log title with "[WEEX-xxx]
> ". So it is needed to change the commit-msg git hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (WEEX-74) commit-msg in git hook should allow user to submit commit with title [WEEX-xxx]
[
https://issues.apache.org/jira/browse/WEEX-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng resolved WEEX-74.
---
Resolution: Fixed
> commit-msg in git hook should allow user to submit commit with title
> [WEEX-xxx]
> ---
>
> Key: WEEX-74
> URL: https://issues.apache.org/jira/browse/WEEX-74
> Project: Weex
> Issue Type: Improvement
> Components: Project
>Reporter: Jonathan Dong
>Assignee: Adam Feng
>Priority: Minor
>
> According to the current commit log policy, people can only submit commit
> with the title:
> {action} [{module}] {description}
> more details can be found
> [here](https://github.com/apache/incubator-weex/blob/master/CONTRIBUTING.md#commit-log)
> As we decided to re-adopt Apache's Jira to track project's bugs and features,
> we hope we can use the auto-correlation feature to automatically connect
> commit with Jira issue by setting your commit log title with "[WEEX-xxx]
> ". So it is needed to change the commit-msg git hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (WEEX-74) commit-msg in git hook should allow user to submit commit with title [WEEX-xxx]
[
https://issues.apache.org/jira/browse/WEEX-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng reassigned WEEX-74:
-
Assignee: Adam Feng
> commit-msg in git hook should allow user to submit commit with title
> [WEEX-xxx]
> ---
>
> Key: WEEX-74
> URL: https://issues.apache.org/jira/browse/WEEX-74
> Project: Weex
> Issue Type: Improvement
> Components: Project
>Reporter: Jonathan Dong
>Assignee: Adam Feng
>Priority: Minor
>
> According to the current commit log policy, people can only submit commit
> with the title:
> {action} [{module}] {description}
> more details can be found
> [here](https://github.com/apache/incubator-weex/blob/master/CONTRIBUTING.md#commit-log)
> As we decided to re-adopt Apache's Jira to track project's bugs and features,
> we hope we can use the auto-correlation feature to automatically connect
> commit with Jira issue by setting your commit log title with "[WEEX-xxx]
> ". So it is needed to change the commit-msg git hook.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (WEEX-72) English document in "Set Up Development Environment" need to be updated
[ https://issues.apache.org/jira/browse/WEEX-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-72: - Assignee: Adam Feng (was: sospartan) > English document in "Set Up Development Environment" need to be updated > --- > > Key: WEEX-72 > URL: https://issues.apache.org/jira/browse/WEEX-72 > Project: Weex > Issue Type: Bug > Components: Project >Reporter: Jonathan Dong >Assignee: Adam Feng >Priority: Minor > Labels: easyfix > > The English version of the document "Set Up Development Environment" has some > grammar glitches, the "dotWe" link at the bottom is not accessible. > Document URL: http://weex-project.io/guide/set-up-env.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-72) English document in "Set Up Development Environment" need to be updated
[ https://issues.apache.org/jira/browse/WEEX-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-72. --- Resolution: Fixed > English document in "Set Up Development Environment" need to be updated > --- > > Key: WEEX-72 > URL: https://issues.apache.org/jira/browse/WEEX-72 > Project: Weex > Issue Type: Bug > Components: Project >Reporter: Jonathan Dong >Assignee: Adam Feng >Priority: Minor > Labels: easyfix > > The English version of the document "Set Up Development Environment" has some > grammar glitches, the "dotWe" link at the bottom is not accessible. > Document URL: http://weex-project.io/guide/set-up-env.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-76) Update "Set Up Development Environment" English Document
[ https://issues.apache.org/jira/browse/WEEX-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-76. --- Resolution: Fixed > Update "Set Up Development Environment" English Document > > > Key: WEEX-76 > URL: https://issues.apache.org/jira/browse/WEEX-76 > Project: Weex > Issue Type: Bug > Components: Project >Reporter: Jonathan Dong >Assignee: Adam Feng >Priority: Minor > > The English version of the document "Setup development environment" needs to > be updated for some grammar and expression glitches. > Document URL: http://weex-project.io/guide/set-up-env.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-76) Update "Set Up Development Environment" English Document
[ https://issues.apache.org/jira/browse/WEEX-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-76: - Assignee: Adam Feng (was: sospartan) > Update "Set Up Development Environment" English Document > > > Key: WEEX-76 > URL: https://issues.apache.org/jira/browse/WEEX-76 > Project: Weex > Issue Type: Bug > Components: Project >Reporter: Jonathan Dong >Assignee: Adam Feng >Priority: Minor > > The English version of the document "Setup development environment" needs to > be updated for some grammar and expression glitches. > Document URL: http://weex-project.io/guide/set-up-env.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-19) Weex(iOS)，If want to let the frame adjust content's height, you need set frame(0, 0, width, NAN), but it sometime will crash
[
https://issues.apache.org/jira/browse/WEEX-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng reassigned WEEX-19:
-
Assignee: xingZhang
> Weex(iOS)，If want to let the frame adjust content's height, you need set
> frame(0, 0, width, NAN), but it sometime will crash
>
>
> Key: WEEX-19
> URL: https://issues.apache.org/jira/browse/WEEX-19
> Project: Weex
> Issue Type: Bug
> Environment: iOS
>Reporter: yuedong
>Assignee: xingZhang
>
> - (void)setFrame:(CGRect)frame
> {
> if (!CGRectEqualToRect(frame, _frame)) {
> _frame = frame;
> WXPerformBlockOnMainThread(^{
> if (_rootView) {
> _rootView.frame = frame;
> WXPerformBlockOnComponentThread(^{
> [self.componentManager rootViewFrameDidChange:frame];
> });
> }
> });
> }
> }
> if the _rootView is not nil, the frame(0, 0, width, NAN) will direct set to
> _rootView, then will crash.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (WEEX-31) weex support Event Bubbling
[ https://issues.apache.org/jira/browse/WEEX-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-31. --- Resolution: Fixed > weex support Event Bubbling > --- > > Key: WEEX-31 > URL: https://issues.apache.org/jira/browse/WEEX-31 > Project: Weex > Issue Type: New Feature > Environment: iOS, Android, HTML5 >Reporter: Tianyi Ma > Original Estimate: 72h > Remaining Estimate: 72h > > This version will follow the W3C standard to implement event bubbling. > Before: jsfm receives the event after the fireEvent event, which triggers the > corresponding element binding. > After: jsfm receive fireEvent event, it will trigger the corresponding > element of the event handler, and the event back to the root component > recursive, triggering the path of all binding handler node. > To terminate the bubbling behavior: In the handler for the node on the path, > write el.stopPropagation() to prevent further delivery. > For forward compatibility, the bubbling mechanism is not turned on by > default. If you want to use it, you can open it in the configuration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-28) Component height animation not properly
[ https://issues.apache.org/jira/browse/WEEX-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-28: - Assignee: Adam Feng > Component height animation not properly > --- > > Key: WEEX-28 > URL: https://issues.apache.org/jira/browse/WEEX-28 > Project: Weex > Issue Type: Bug > Environment: Android, iOS >Reporter: moxun >Assignee: Adam Feng > > There are two issues with animation: > Issue1 for iOS: > The pivot of animation is the center of component instead of top. > demo: http://dotwe.org/weex/4a14b70cb38e7a4e249ef8c983c6d1cb > expect： the default pivot is the top of component > Issue2 for Android and iOS: > The container size does not vary with the size of the content. > demo: http://dotwe.org/weex/539606f1a765742f492994415d419d0c > except: the container size increases or decreases as the content size -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-28) Component height animation not properly
[ https://issues.apache.org/jira/browse/WEEX-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-28. --- Resolution: Fixed > Component height animation not properly > --- > > Key: WEEX-28 > URL: https://issues.apache.org/jira/browse/WEEX-28 > Project: Weex > Issue Type: Bug > Environment: Android, iOS >Reporter: moxun >Assignee: Adam Feng > > There are two issues with animation: > Issue1 for iOS: > The pivot of animation is the center of component instead of top. > demo: http://dotwe.org/weex/4a14b70cb38e7a4e249ef8c983c6d1cb > expect： the default pivot is the top of component > Issue2 for Android and iOS: > The container size does not vary with the size of the content. > demo: http://dotwe.org/weex/539606f1a765742f492994415d419d0c > except: the container size increases or decreases as the content size -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-27) Prerender
[ https://issues.apache.org/jira/browse/WEEX-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-27: - Assignee: Adam Feng > Prerender > - > > Key: WEEX-27 > URL: https://issues.apache.org/jira/browse/WEEX-27 > Project: Weex > Issue Type: New Feature > Environment: Android, iOS, (not Html5) >Reporter: xingjiu >Assignee: Adam Feng > Attachments: TB12RlEQFccXFXX.jpg > > Original Estimate: 504h > Remaining Estimate: 504h > > In order to impove the page open speed, we have intro many ways, such as > js-bundle prefetch. > Now we have a new idea of render the next page in background. When click the > button to jump to the next page, just show it, no other js file execute cost > needed. > We call it prerender. > First. Limition > Prerender will benifit user experience of waiting time of new page load. > It is like a tradition way, use extre space(memory) to reduce time cost. > We need to protected our app`s memory cost, so just one page can be > prerendered. This limit maybe removed later. > Second. How we do? > One way is to store the callNative commander in memory. > We know weex use javascript engine to explain how the page will be render, > then js will use callNative() to make native views created. > Once we just store the callNative commander, not to execute it. When the page > is truely show, do the commander executed. > The attach image is the order of weex render steps currently. > Finally. > Our goal is to make weex page show quickly. > We assure that using prerender, the page open in one second will reach 99.9+ > precent. And the global festive main page will works prefect in prerender > mode. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-43) Add release job to travis CI
[ https://issues.apache.org/jira/browse/WEEX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-43: - Assignee: Adam Feng (was: sospartan) > Add release job to travis CI > > > Key: WEEX-43 > URL: https://issues.apache.org/jira/browse/WEEX-43 > Project: Weex > Issue Type: Task > Components: Project >Reporter: sospartan >Assignee: Adam Feng > > Some changes will make to project's travis config: > * Put commands to `.travis` config use `if` statement, avoid using script > file will make more easier to determine problems. > * Add our release test > * Create a release source tarball > * test build script for source release > * upload daily build artfacts (This will wait until we add snapshot upload > script) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-36) Fix problems in 0.12 RC3
[
https://issues.apache.org/jira/browse/WEEX-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng reassigned WEEX-36:
-
Assignee: Adam Feng (was: sospartan)
> Fix problems in 0.12 RC3
>
>
> Key: WEEX-36
> URL: https://issues.apache.org/jira/browse/WEEX-36
> Project: Weex
> Issue Type: Task
> Components: Project
>Reporter: sospartan
>Assignee: Adam Feng
> Fix For: 0.12
>
>
> In RC3 vote, Craig point out we have lots issue of the source tarball.
> So I'll explain these problems one by one.
> {quote}
> > I also must vote -1 on this release.
> >
> > clr% find . -name "*.jar"
> > ./android/playground/gradle/wrapper/gradle-wrapper.jar
> > ./android/sdk/gradle/wrapper/gradle-wrapper.jar
> > ./android/sdk/license/license-gradle-plugin-0.12.1.jar
> > ./android/sdk/license/maven-license-plugin-1.10.b1.jar
> > ./android/sdk/license/plexus-utils-3.0.24.jar
> > ./android/weex_debug/gradle/wrapper/gradle-wrapper.jar
> > ./android/weex_debug/libs/classes.jar
> > ./scripts/apache-rat-0.12.jar
> >
> > 1. These jar files are not source and must not appear in the source release.
> >
> {quote}
> These files were excluded from release. Some of them were replaced with maven
> dependencies in SDK(android/sdk).
> {quote}
> > 2. I appreciate the effort involved in compiling the
> > POSSIBLE-NOTICES-FOR-BIN-DIST. But looking into these dependencies I am >
> > troubled by the difficulty actually finding the licenses of the projects.
> >
> > For example, the "possible notice" for animaitonjs (possible typo here)
> > refers to https://www.npmjs.com/package/animationjs from > which it is
> > impossible (ok, perhaps possible but I could not find a link) to find the
> > actual project.
> >
> > References to npmjs in this entire file should be removed and replaced by
> > references to the home of the project. (Not relevant > for this release
> > because the files are not actually being distributed.)
> >
> {quote}
> The projects' link were all fixed.
> {quote}
> > 3. The java source files in android/commons/src are still in the
> > com.alibaba name space. Assuming that these are actually weex > source
> > files, they must be repackaged to org.apache.
> >
> {quote}
> Package name is now 'org.apache'. I'll use a script to update the package
> name when release.
> {quote}
> > 4. The javascript source files in playground/app/src are missing the
> > license header. They have a style that I do not recognize. > Are these
> > generated files? The first several lines of storage-demo.js:
> >
> > /**/ (function(modules) { // webpackBootstrap
> > /**/// The module cache
> > /**/var installedModules = {};
> >
> > /**/// The require function
> > /**/function __webpack_require__(moduleId) {
> >
> > /**/// Check if module is in cache
> > /**/if(installedModules[moduleId])
> > /**/return installedModules[moduleId].exports;
> >
> {quote}
> These pre-build files were excluded. README_RELEASE will tell you to build
> weex from ground.
> {quote}
> > 5. The java files in playground/app/src/main/java_zxing are in the
> > com.google name space. They have a google license header.
> >
> {quote}
> The 'playground' sample project was excluded, so were these files.
> {quote}
> > 6. The packages/weex-html5 contains LICENSE and NOTICE files. These should
> > be in the top level directory of the release.
> >
> {quote}
> These files were excluded, not using to build weex SDK.
> {quote}
> > 7. The scripts/rh contains LICENSE and NOTICE files. These should be in the
> > top level directory of the release.
> >
> {quote}
> These files were excluded, not using to build weex SDK.
> {quote}
> > 8. There is an executable file that doesn't belong:
> >
> > clr% ls -l start
> > -rwxr-xr-x@ 1 clr staff 161 Apr 27 20:34 start
> >
> {quote}
> These files were excluded, not using to build weex SDK. It's just some
> utility script in development.
> {quote}
> > 9. There is an executable gradlew in sdk/gradle that doesn't belong in a
> > source release.
> >
> {quote}
> Excluded. You can use your installed gradle to set this up.
> {quote}
> > 10. There are shared objects in sdk/libs that don't belong in a source
> > release.
> >
> {quote}
> Excluded. They are download during build.
> {quote}
> > 11. There are NOTICE and LICENSE files in ios/sdk that seem to be unix
> > executable files.
> >
> > clr% ls -l ios/sdk
> > total 40
> > -rwxr-xr-x@ 1 clr staff 11343 Apr 27 20:34 LICENSE
> > -rwxr-xr-x@ 1 clr staff575 Apr 27 20:34 NOTICE
> >
> {quote}
> Removed from project. It's a left-over.
> {quote}
> > 12. The README.md doesn't tell me how to build/use org.apache.weex. The
> > first several lines refer to third-party projects fro
[jira] [Assigned] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo
[ https://issues.apache.org/jira/browse/WEEX-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-44: - Assignee: Adam Feng (was: sospartan) > Add script to upload snapshot artifact to maven/pods repo > - > > Key: WEEX-44 > URL: https://issues.apache.org/jira/browse/WEEX-44 > Project: Weex > Issue Type: Sub-task > Components: Project >Reporter: sospartan >Assignee: Adam Feng > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-36) Fix problems in 0.12 RC3
[
https://issues.apache.org/jira/browse/WEEX-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng resolved WEEX-36.
---
Resolution: Fixed
> Fix problems in 0.12 RC3
>
>
> Key: WEEX-36
> URL: https://issues.apache.org/jira/browse/WEEX-36
> Project: Weex
> Issue Type: Task
> Components: Project
>Reporter: sospartan
>Assignee: Adam Feng
> Fix For: 0.12
>
>
> In RC3 vote, Craig point out we have lots issue of the source tarball.
> So I'll explain these problems one by one.
> {quote}
> > I also must vote -1 on this release.
> >
> > clr% find . -name "*.jar"
> > ./android/playground/gradle/wrapper/gradle-wrapper.jar
> > ./android/sdk/gradle/wrapper/gradle-wrapper.jar
> > ./android/sdk/license/license-gradle-plugin-0.12.1.jar
> > ./android/sdk/license/maven-license-plugin-1.10.b1.jar
> > ./android/sdk/license/plexus-utils-3.0.24.jar
> > ./android/weex_debug/gradle/wrapper/gradle-wrapper.jar
> > ./android/weex_debug/libs/classes.jar
> > ./scripts/apache-rat-0.12.jar
> >
> > 1. These jar files are not source and must not appear in the source release.
> >
> {quote}
> These files were excluded from release. Some of them were replaced with maven
> dependencies in SDK(android/sdk).
> {quote}
> > 2. I appreciate the effort involved in compiling the
> > POSSIBLE-NOTICES-FOR-BIN-DIST. But looking into these dependencies I am >
> > troubled by the difficulty actually finding the licenses of the projects.
> >
> > For example, the "possible notice" for animaitonjs (possible typo here)
> > refers to https://www.npmjs.com/package/animationjs from > which it is
> > impossible (ok, perhaps possible but I could not find a link) to find the
> > actual project.
> >
> > References to npmjs in this entire file should be removed and replaced by
> > references to the home of the project. (Not relevant > for this release
> > because the files are not actually being distributed.)
> >
> {quote}
> The projects' link were all fixed.
> {quote}
> > 3. The java source files in android/commons/src are still in the
> > com.alibaba name space. Assuming that these are actually weex > source
> > files, they must be repackaged to org.apache.
> >
> {quote}
> Package name is now 'org.apache'. I'll use a script to update the package
> name when release.
> {quote}
> > 4. The javascript source files in playground/app/src are missing the
> > license header. They have a style that I do not recognize. > Are these
> > generated files? The first several lines of storage-demo.js:
> >
> > /**/ (function(modules) { // webpackBootstrap
> > /**/// The module cache
> > /**/var installedModules = {};
> >
> > /**/// The require function
> > /**/function __webpack_require__(moduleId) {
> >
> > /**/// Check if module is in cache
> > /**/if(installedModules[moduleId])
> > /**/return installedModules[moduleId].exports;
> >
> {quote}
> These pre-build files were excluded. README_RELEASE will tell you to build
> weex from ground.
> {quote}
> > 5. The java files in playground/app/src/main/java_zxing are in the
> > com.google name space. They have a google license header.
> >
> {quote}
> The 'playground' sample project was excluded, so were these files.
> {quote}
> > 6. The packages/weex-html5 contains LICENSE and NOTICE files. These should
> > be in the top level directory of the release.
> >
> {quote}
> These files were excluded, not using to build weex SDK.
> {quote}
> > 7. The scripts/rh contains LICENSE and NOTICE files. These should be in the
> > top level directory of the release.
> >
> {quote}
> These files were excluded, not using to build weex SDK.
> {quote}
> > 8. There is an executable file that doesn't belong:
> >
> > clr% ls -l start
> > -rwxr-xr-x@ 1 clr staff 161 Apr 27 20:34 start
> >
> {quote}
> These files were excluded, not using to build weex SDK. It's just some
> utility script in development.
> {quote}
> > 9. There is an executable gradlew in sdk/gradle that doesn't belong in a
> > source release.
> >
> {quote}
> Excluded. You can use your installed gradle to set this up.
> {quote}
> > 10. There are shared objects in sdk/libs that don't belong in a source
> > release.
> >
> {quote}
> Excluded. They are download during build.
> {quote}
> > 11. There are NOTICE and LICENSE files in ios/sdk that seem to be unix
> > executable files.
> >
> > clr% ls -l ios/sdk
> > total 40
> > -rwxr-xr-x@ 1 clr staff 11343 Apr 27 20:34 LICENSE
> > -rwxr-xr-x@ 1 clr staff575 Apr 27 20:34 NOTICE
> >
> {quote}
> Removed from project. It's a left-over.
> {quote}
> > 12. The README.md doesn't tell me how to build/use org.apache.weex. The
> > first several lines refer to third-party projects from > Alibaba and
> > coco
[jira] [Resolved] (WEEX-60) support perspective for rotate in 3d dimension
[ https://issues.apache.org/jira/browse/WEEX-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-60. --- Resolution: Fixed > support perspective for rotate in 3d dimension > -- > > Key: WEEX-60 > URL: https://issues.apache.org/jira/browse/WEEX-60 > Project: Weex > Issue Type: New Feature >Reporter: xingZhang >Assignee: xingZhang > > iOS Android and html5 will support a new feature about perspective function > in transform when making rotation in 3d dimension according to the w3c > description > [here](https://developer.mozilla.org/en-US/docs/Web/CSS/perspective) > the default value of perspective function is +inf , thus it will be parallel > projection. > perspective function can be the following value: >perspective(20px) > note: the function must be the first one in transform > other case will be invalid. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-77) weex闪退问题
[ https://issues.apache.org/jira/browse/WEEX-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196540#comment-16196540 ] Adam Feng commented on WEEX-77: --- Hi, could you please provide more information, how to recurrent the crash， etc. > weex闪退问题 > > > Key: WEEX-77 > URL: https://issues.apache.org/jira/browse/WEEX-77 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.16 >Reporter: bangyuezou >Assignee: zhengshihan > > 1Caused by: java.lang.ArrayIndexOutOfBoundsException: length=8192; index=8192 > 2at com.android.okhttp.okio.Buffer.writeUtf8(Buffer.java:818) > 3at com.android.okhttp.okio.Buffer.writeUtf8(Buffer.java:793) > 4at > com.android.okhttp.okio.RealBufferedSink.writeUtf8(RealBufferedSink.java:57) > 5at > com.android.okhttp.internal.http.HttpConnection.writeRequest(HttpConnection.java:172) > 6at > com.android.okhttp.internal.http.HttpTransport.writeRequestHeaders(HttpTransport.java:76) > 7at > com.android.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:766) > 8at > com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:463) > 9at > com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:405) > 10at > com.android.okhttp.internal.huc.HttpURLConnectionImpl.getHeaders(HttpURLConnectionImpl.java:162) > 11at > com.android.okhttp.internal.huc.HttpURLConnectionImpl.getHeaderFields(HttpURLConnectionImpl.java:222) > 12at > com.networkbench.agent.impl.instrumentation.NBSHttpURLConnectionExtension.getHeaderFields(SourceFile) > 13at > com.taobao.weex.adapter.DefaultWXHttpAdapter$1.run(DefaultWXHttpAdapter.java) > 14at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) > 15at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) > 16at java.lang.Thread.run(Thread.java:776) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-79) Modify document website style of weex.
[ https://issues.apache.org/jira/browse/WEEX-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-79: - Assignee: Hanks Zhang (was: sospartan) > Modify document website style of weex. > -- > > Key: WEEX-79 > URL: https://issues.apache.org/jira/browse/WEEX-79 > Project: Weex > Issue Type: Improvement >Reporter: erha19 >Assignee: Hanks Zhang > > Problem: > Document page space is less and poor reading effect > Solution: > - Change background-color of body. > - Add a separate scroll bar for the document page -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-78) The ES7 methods should be removed to improve compatibility
[ https://issues.apache.org/jira/browse/WEEX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-78: - Assignee: Hanks Zhang (was: sospartan) > The ES7 methods should be removed to improve compatibility > -- > > Key: WEEX-78 > URL: https://issues.apache.org/jira/browse/WEEX-78 > Project: Weex > Issue Type: Bug > Components: JSFM >Reporter: Hanks Zhang >Assignee: Hanks Zhang > Labels: patch > > The implementation of event bubbling in JSF is using > `Array.prototype.includes` API [1] which is defined in ECMAScript 2016 (ES7). > This method is not compatible with low version js engines and should be > replaced. > [1] > https://github.com/apache/incubator-weex/blob/4bc653653c1460dcad0642ef654e593c89ebaaf1/html5/runtime/vdom/Element.js#L412 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo
[ https://issues.apache.org/jira/browse/WEEX-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-44: - Assignee: xingZhang (was: Adam Feng) > Add script to upload snapshot artifact to maven/pods repo > - > > Key: WEEX-44 > URL: https://issues.apache.org/jira/browse/WEEX-44 > Project: Weex > Issue Type: Sub-task > Components: Project >Reporter: sospartan >Assignee: xingZhang > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-43) Add release job to travis CI
[ https://issues.apache.org/jira/browse/WEEX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-43: - Assignee: Zechang Xie (was: Adam Feng) > Add release job to travis CI > > > Key: WEEX-43 > URL: https://issues.apache.org/jira/browse/WEEX-43 > Project: Weex > Issue Type: Task > Components: Project >Reporter: sospartan >Assignee: Zechang Xie > > Some changes will make to project's travis config: > * Put commands to `.travis` config use `if` statement, avoid using script > file will make more easier to determine problems. > * Add our release test > * Create a release source tarball > * test build script for source release > * upload daily build artfacts (This will wait until we add snapshot upload > script) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-27) Prerender
[ https://issues.apache.org/jira/browse/WEEX-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-27. --- Resolution: Fixed > Prerender > - > > Key: WEEX-27 > URL: https://issues.apache.org/jira/browse/WEEX-27 > Project: Weex > Issue Type: New Feature > Environment: Android, iOS, (not Html5) >Reporter: xingjiu >Assignee: Adam Feng > Attachments: TB12RlEQFccXFXX.jpg > > Original Estimate: 504h > Remaining Estimate: 504h > > In order to impove the page open speed, we have intro many ways, such as > js-bundle prefetch. > Now we have a new idea of render the next page in background. When click the > button to jump to the next page, just show it, no other js file execute cost > needed. > We call it prerender. > First. Limition > Prerender will benifit user experience of waiting time of new page load. > It is like a tradition way, use extre space(memory) to reduce time cost. > We need to protected our app`s memory cost, so just one page can be > prerendered. This limit maybe removed later. > Second. How we do? > One way is to store the callNative commander in memory. > We know weex use javascript engine to explain how the page will be render, > then js will use callNative() to make native views created. > Once we just store the callNative commander, not to execute it. When the page > is truely show, do the commander executed. > The attach image is the order of weex render steps currently. > Finally. > Our goal is to make weex page show quickly. > We assure that using prerender, the page open in one second will reach 99.9+ > precent. And the global festive main page will works prefect in prerender > mode. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-70) weex pull request rules discuss
[ https://issues.apache.org/jira/browse/WEEX-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-70: - Assignee: Adam Feng (was: sospartan) > weex pull request rules discuss > --- > > Key: WEEX-70 > URL: https://issues.apache.org/jira/browse/WEEX-70 > Project: Weex > Issue Type: Improvement > Components: Project >Affects Versions: 0.17 >Reporter: Zechang Xie >Assignee: Adam Feng > > weex pull request rules discuss for better run weex in apache. > give me your suggest. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-71) weex commit and pr log rules discuss
[ https://issues.apache.org/jira/browse/WEEX-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-71: - Assignee: Zechang Xie (was: sospartan) > weex commit and pr log rules discuss > > > Key: WEEX-71 > URL: https://issues.apache.org/jira/browse/WEEX-71 > Project: Weex > Issue Type: Improvement > Components: Project >Affects Versions: 0.17 >Reporter: Zechang Xie >Assignee: Zechang Xie > Labels: discussion > > weex commit and pr log rules discuss for better running weex in apache -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-51) The console APIs doesn't work on Android
[ https://issues.apache.org/jira/browse/WEEX-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-51: - Assignee: YorkShen (was: sospartan) > The console APIs doesn't work on Android > > > Key: WEEX-51 > URL: https://issues.apache.org/jira/browse/WEEX-51 > Project: Weex > Issue Type: Bug > Components: JSFM >Affects Versions: 0.15 >Reporter: Hanks Zhang >Assignee: YorkShen > > As Weex switched its js engine to JSC on Android, the console APIs doesn't > work anymore. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-66) Support FlatGUI
[ https://issues.apache.org/jira/browse/WEEX-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-66: - Assignee: YorkShen (was: sospartan) > Support FlatGUI > --- > > Key: WEEX-66 > URL: https://issues.apache.org/jira/browse/WEEX-66 > Project: Weex > Issue Type: New Feature >Reporter: YorkShen >Assignee: YorkShen > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-63) Android refactor lines
[ https://issues.apache.org/jira/browse/WEEX-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-63: - Assignee: YorkShen (was: sospartan) > Android refactor lines > -- > > Key: WEEX-63 > URL: https://issues.apache.org/jira/browse/WEEX-63 > Project: Weex > Issue Type: New Feature >Reporter: YorkShen >Assignee: YorkShen > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-49) add osName to weex.config.env
[
https://issues.apache.org/jira/browse/WEEX-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng reassigned WEEX-49:
-
Assignee: Danz He (was: sospartan)
> add osName to weex.config.env
> -
>
> Key: WEEX-49
> URL: https://issues.apache.org/jira/browse/WEEX-49
> Project: Weex
> Issue Type: Improvement
> Components: Project
>Affects Versions: 0.15
>Reporter: Danz He
>Assignee: Danz He
>
> Since the *weex.config.env.platform* on web has tell user that the
> environment is 'Web', there should be another property to tell which system
> ('android' or 'iOS') it is on. So a *weex.config.env.osName* is needed. On
> Android and iOS platform, the platform name and the osName is the same,
> however on Web platform (webview or mobile browsers), they are different.
> For example, a weex page runing in a chrome browser on a Android device with
> weex-vue-render. access the two properties will be:
> * weex.config.env.platform: 'Web'
> * weex.config.env.osName: 'android'
> * weex.config.env.osName: 'iOS'
> doc: http://weex.apache.org/references/weex-variable.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (WEEX-45) clearTimeout and clearInterval doesn't work when funId is greater than 127
[ https://issues.apache.org/jira/browse/WEEX-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-45: - Assignee: YorkShen > clearTimeout and clearInterval doesn't work when funId is greater than 127 > -- > > Key: WEEX-45 > URL: https://issues.apache.org/jira/browse/WEEX-45 > Project: Weex > Issue Type: Bug >Reporter: YorkShen >Assignee: YorkShen > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-33) Config Ability in weex
[ https://issues.apache.org/jira/browse/WEEX-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-33: - Assignee: xingZhang > Config Ability in weex > -- > > Key: WEEX-33 > URL: https://issues.apache.org/jira/browse/WEEX-33 > Project: Weex > Issue Type: New Feature >Reporter: xingjiu >Assignee: xingZhang > Original Estimate: 504h > Remaining Estimate: 504h > > Background： > As we know, weex now has NO config module. Every mobile of weex are using the > same config (the config in source code). > More and more module or component requires the ability to sperate one from > each other. > Such as Prefetch, Prerender module. There should be a way to config the how > the module works, like how many items it cound do the prefetch. This config > will be different in different apps. > Solution: > Add a module named of WXConfigModule in weex_sdk, a simple key-value storage > is enough. > API is > void setConfig(String name, Object value) > Object getConfig(String name) > void sync(String name) // get the lastest config from server > void syncAll() > void invalid(String name) // option. invalid a config for once, using in > debug of bugfix scenario > The default implement is calling the config interface. > App like TAOBAO will using orange to sync configs from server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-35) A component open URL got different action on iOS and Android
[ https://issues.apache.org/jira/browse/WEEX-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-35: - Assignee: xingZhang > A component open URL got different action on iOS and Android > > > Key: WEEX-35 > URL: https://issues.apache.org/jira/browse/WEEX-35 > Project: Weex > Issue Type: Bug > Environment: iOS, Android >Reporter: Isken Huang >Assignee: xingZhang > > iOS: > https://github.com/apache/incubator-weex/blob/master/ios/sdk/WeexSDK/Sources/Component/WXAComponent.m#L63 > Android: > https://github.com/apache/incubator-weex/blob/master/android/sdk/src/main/java/com/taobao/weex/ui/component/WXA.java#L53 > iOS SDK's is when href exist and string length more then 0 to do something. > Android SDK's is when href is not null to do something. This logic should be > the same. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-32) weex-vue-framework add services mechanism
[ https://issues.apache.org/jira/browse/WEEX-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-32: - Assignee: Hanks Zhang > weex-vue-framework add services mechanism > - > > Key: WEEX-32 > URL: https://issues.apache.org/jira/browse/WEEX-32 > Project: Weex > Issue Type: New Feature > Environment: iOS, Android >Reporter: Tianyi Ma >Assignee: Hanks Zhang > Original Estimate: 120h > Remaining Estimate: 120h > > See details at https: //github.com/alibaba/weex/issues/1938 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-18) bubble up event of click in android
[ https://issues.apache.org/jira/browse/WEEX-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-18: - Assignee: Adam Feng > bubble up event of click in android > --- > > Key: WEEX-18 > URL: https://issues.apache.org/jira/browse/WEEX-18 > Project: Weex > Issue Type: Improvement > Environment: weex_sdk 0.11 / 0.10 >Reporter: xingjiu >Assignee: Adam Feng > Labels: android, event > Original Estimate: 672h > Remaining Estimate: 672h > > Binding a click event on child element, when the parent element binding a > long press event. Then just long press at the child element. > Two mistakes occurs: > 1. the parent long press event not be fired. > 2. the child click event fired. > Demo is at http://dotwe.org/weex/a20e3898b3875e04d28ef394509d2088 > I know this is a hard work to resolve it, while we can find out a solution > firstly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-54) [proposal] Support to detect the feature compatibility of weex
[
https://issues.apache.org/jira/browse/WEEX-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng reassigned WEEX-54:
-
Assignee: Hanks Zhang (was: sospartan)
> [proposal] Support to detect the feature compatibility of weex
> --
>
> Key: WEEX-54
> URL: https://issues.apache.org/jira/browse/WEEX-54
> Project: Weex
> Issue Type: New Feature
> Components: JSFM
>Affects Versions: 0.15
>Reporter: Hanks Zhang
>Assignee: Hanks Zhang
>Priority: Minor
> Labels: features
>
> h2. Background
> Because Weex support to extend components and modules, so the host
> environment will be very different. Weex needs a mechanism to detect whether
> a feature is supported in the current environment.
> h2. API Design
> {code:javascript}
> weex.supports(condition : String) : Boolean | Null
> {code}
> * param: a formatted string. @TYPE/NAME
> * return value: supported -> true | unsupported -> false | unclear -> null
> h2. Usage
> {code:javascript}
> // Detects whether the embed component is supported
> weex.supports('@component/embed')
> // Detects whether the picker module is supported
> weex.supports('@module/picker')
> // Detects whether the dom.getComponentRect method is supported
> weex.supports('@module/dom.getComponentRect')
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (WEEX-17) Abstract a common `weex` variable for each JS framework
[
https://issues.apache.org/jira/browse/WEEX-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng reassigned WEEX-17:
-
Assignee: Hanks Zhang
> Abstract a common `weex` variable for each JS framework
> ---
>
> Key: WEEX-17
> URL: https://issues.apache.org/jira/browse/WEEX-17
> Project: Weex
> Issue Type: Improvement
>Reporter: Jinjiang Zhao
>Assignee: Hanks Zhang
>Priority: Minor
> Labels: features
>
> I think before a Weex instance initialized by a certain JS framework, we can
> abstract and prepare something which every JS framework will do the same and
> put them into a common `weex` variable. Then this variable could be used
> directly in a JS framework.
> It contains:
> 1. A CallbackManager instance: to convert callback into a unique callbackId
> in this Weex page, just for passing the id to native as the callback itself.
> 2. A NativeModuleGetter instance: to require a native module in this Weex
> page. Because it certainly need processes functions, so it depends on the
> CallbackManager instance.
> 3. A Document instance: every Weex page must have and only have one Document
> instance.
> 4. Config object of the Weex page. It should contains env info, framework
> info and bundle info.
> 5. CSS Units calculator. It depends on config object.
> 6. All injects from JS Services.
> All of above could be passed into JS framework for init. And
> NativeModuleGetter instance, Document instance, config object and CSS units
> calculator could be exposed on `weex` variable as `{ requireModule(name),
> document, config, unit }`. So the new API design of
> `framework.createInstance` could be:
> function createInstance(id, code, info)
> and parameter info contains: { weex, callbacks, services }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (WEEX-81) shadow render wrong
[ https://issues.apache.org/jira/browse/WEEX-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201832#comment-16201832 ] Adam Feng commented on WEEX-81: --- [~acton393] please have a look at the box-shadow issue > shadow render wrong > --- > > Key: WEEX-81 > URL: https://issues.apache.org/jira/browse/WEEX-81 > Project: Weex > Issue Type: Bug > Components: iOS >Reporter: jackyking >Assignee: Adam Feng >Priority: Minor > Attachments: correct.png, wrong.png > > > see demo http://dotwe.org/vue/fbbd9910d1423975370424d7f19893d5 > shadow should be like this: !correct.png|thumbnail! > but rendered this: !wrong.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-81) shadow render wrong
[ https://issues.apache.org/jira/browse/WEEX-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-81: - Assignee: xingZhang (was: Adam Feng) > shadow render wrong > --- > > Key: WEEX-81 > URL: https://issues.apache.org/jira/browse/WEEX-81 > Project: Weex > Issue Type: Bug > Components: iOS >Reporter: jackyking >Assignee: xingZhang >Priority: Minor > Attachments: correct.png, wrong.png > > > see demo http://dotwe.org/vue/fbbd9910d1423975370424d7f19893d5 > shadow should be like this: !correct.png|thumbnail! > but rendered this: !wrong.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-88) BOOL arguments cannot be received correctly by component's method in 32-bit iOS devices
[
https://issues.apache.org/jira/browse/WEEX-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216678#comment-16216678
]
Adam Feng commented on WEEX-88:
---
It looks good to me, please create a pull request, thanks.
> BOOL arguments cannot be received correctly by component's method in 32-bit
> iOS devices
> ---
>
> Key: WEEX-88
> URL: https://issues.apache.org/jira/browse/WEEX-88
> Project: Weex
> Issue Type: Bug
> Components: iOS
>Affects Versions: 0.15
> Environment: iPhone 4s (iOS 9.1), iPhone 5 simulator (iOS 10.3)
>Reporter: Shiwen XU
>Assignee: Adam Feng
>Priority: Blocker
>
> BOOL arguments cannot be received correctly by component's method in 32-bit
> iOS devices. It appears that the received argument is always some integer
> value other than boolean value.
> This problem might be introduced by the macro *WX_ARGUMENTS_SET*.
> {code:title=WXUtility.h|borderStyle=solid}
> #define WX_ARGUMENTS_SET(_invocation, _sig, idx, _obj, _ppFree) \
> do {\
> const char *encode = [_sig getArgumentTypeAtIndex:(idx) + 2];\
> switch(encode[0]){\
> WX_EPCHAR_CASE(_invocation, idx, _C_CHARPTR, _obj, char *,
> UTF8String, _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_INT, _obj, int, intValue,
> _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_SHT, _obj, short, shortValue,
> _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_LNG, _obj, long, longValue,
> _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_LNG_LNG, _obj, long long,
> longLongValue, _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_UCHR, _obj, unsigned char,
> unsignedCharValue, _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_UINT, _obj, unsigned int,
> unsignedIntValue, _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_USHT, _obj, unsigned short,
> unsignedShortValue, _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_ULNG, _obj, unsigned long,
> unsignedLongValue, _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_ULNG_LNG, _obj,unsigned long
> long, unsignedLongLongValue, _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_FLT, _obj, float, floatValue,
> _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_DBL, _obj, double, doubleValue,
> _ppFree)\
> WX_ENUMBER_CASE(_invocation, idx, _C_BOOL, _obj, bool, boolValue,
> _ppFree)\
> default: { [_invocation setArgument:&_obj atIndex:(idx) + 2];
> *(_ppFree + idx) = 0; break;}\
> }\
> }while(0)
> {code}
> The BOOL value in 32-bit iOS is a typedef of signed char so its *@encode* is
> *_C_CHR* instead of *_C_BOOL*. We can find the typedef in objc.h.
> {code:title=objc.h|borderStyle=solid}
> #if defined(__OBJC_BOOL_IS_BOOL)
> // Honor __OBJC_BOOL_IS_BOOL when available.
> # if __OBJC_BOOL_IS_BOOL
> # define OBJC_BOOL_IS_BOOL 1
> # else
> # define OBJC_BOOL_IS_BOOL 0
> # endif
> #else
> // __OBJC_BOOL_IS_BOOL not set.
> # if TARGET_OS_OSX || (TARGET_OS_IOS && !__LP64__ && !__ARM_ARCH_7K)
> # define OBJC_BOOL_IS_BOOL 0
> # else
> # define OBJC_BOOL_IS_BOOL 1
> # endif
> #endif
> #if OBJC_BOOL_IS_BOOL
> typedef bool BOOL;
> #else
> # define OBJC_BOOL_IS_CHAR 1
> typedef signed char BOOL;
> // BOOL is explicitly signed so @encode(BOOL) == "c" rather than "C"
> // even if -funsigned-char is used.
> #endif
> {code}
> But *WX_ARGUMENTS_SET* didn't consider the case of *_C_CHR*. In this case the
> default condition is executed and the *NSNumber pointer* value will be casted
> to a *BOOL* value so the received argument is always wrong.
> If I add this line of code and the received argument will become correct.
> {code}
> WX_ENUMBER_CASE(_invocation, idx, _C_UCHR, _obj, unsigned char,
> unsignedCharValue, _ppFree)\
> /* added code */
> WX_ENUMBER_CASE(_invocation, idx, _C_CHR, _obj, char, charValue, _ppFree)\
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (WEEX-89) View with linear gradient could not render its border radius correctly
[ https://issues.apache.org/jira/browse/WEEX-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219921#comment-16219921 ] Adam Feng commented on WEEX-89: --- Could you please provide simpler demo using http://dotwe.org/vue/ ? > View with linear gradient could not render its border radius correctly > -- > > Key: WEEX-89 > URL: https://issues.apache.org/jira/browse/WEEX-89 > Project: Weex > Issue Type: Bug > Components: iOS >Reporter: leozdgao >Assignee: Adam Feng >Priority: Blocker > Attachments: correct-without-gradient.PNG, incorrect-with-gradient.PNG > > > A view with linear gradient could not render its border radius correctly, > check the attachment please, the file 'incorrect-with-gradient' shows the > problem, and the file `correct-without-gradient` is the view without linear > gradient and it render its border-radius correctly. > And my style is right here: > ``` > backgroundImage: linear-gradient(to right, '#FF00A0', '#FF0041'); > border-top-left-radius: 8px; > border-top-right-radius: 8px; > ``` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-168) [iOS] AnimationModule needsLayout may show incorrect
[ https://issues.apache.org/jira/browse/WEEX-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285642#comment-16285642 ] Adam Feng commented on WEEX-168: Any details or demos? > [iOS] AnimationModule needsLayout may show incorrect > > > Key: WEEX-168 > URL: https://issues.apache.org/jira/browse/WEEX-168 > Project: Weex > Issue Type: Bug >Reporter: qz >Assignee: Adam Feng >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (WEEX-223) Wrong Weex SDK version in example
[ https://issues.apache.org/jira/browse/WEEX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376759#comment-16376759 ] Adam Feng commented on WEEX-223: [~codefurture] please confirm the version. > Wrong Weex SDK version in example > - > > Key: WEEX-223 > URL: https://issues.apache.org/jira/browse/WEEX-223 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: android 0.18.0 >Reporter: biaomingzhong >Assignee: zhengshihan >Priority: Major > > I am using Bintray JCenter 0.18.0 version. While having explicitly version in > my build.gradle file, when I try out the Official example about Weex > Environment, the version in page showing is 0.17.0 > [DotWe link is official waterfall > example|http://dotwe.org/vue/22ed65f7797069cb6763cd741496972f] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-222) Sticky header in waterfall is not sticky
[ https://issues.apache.org/jira/browse/WEEX-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376760#comment-16376760 ] Adam Feng commented on WEEX-222: [~codefurture] > Sticky header in waterfall is not sticky > > > Key: WEEX-222 > URL: https://issues.apache.org/jira/browse/WEEX-222 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: Playground App Android >Reporter: biaomingzhong >Assignee: zhengshihan >Priority: Critical > > * Just upgrade weex_sdk to 0.18.0. But the sticky header is not sticky in > playground app. > * [DotWe link is official waterfall > example|http://dotwe.org/vue/7a9195643e9e8da352b0d879cdbe68c0] > * I have tried this waterfall example in Taobao app. Scan result has same > problem that the sticky header is not sticky. > * But I downgrade to SDK 0.17. It works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (WEEX-230) input bug
[ https://issues.apache.org/jira/browse/WEEX-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384464#comment-16384464 ] Adam Feng commented on WEEX-230: Please follow the bug report guideline [http://weex-project.io/bug-report-guidelines.html] and provide a detailed demo. > input bug > -- > > Key: WEEX-230 > URL: https://issues.apache.org/jira/browse/WEEX-230 > Project: Weex > Issue Type: Bug >Reporter: 郑江荣 >Assignee: Adam Feng >Priority: Blocker > > input 当设置的绑定的变量值为空字符串之后，再次改变绑定的值，界面上输入框的值不再改变，不设置空字符串就没问题 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-230) input bug
[ https://issues.apache.org/jira/browse/WEEX-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-230. Resolution: Fixed > input bug > -- > > Key: WEEX-230 > URL: https://issues.apache.org/jira/browse/WEEX-230 > Project: Weex > Issue Type: Bug >Reporter: 郑江荣 >Assignee: Adam Feng >Priority: Blocker > > input 当设置的绑定的变量值为空字符串之后，再次改变绑定的值，界面上输入框的值不再改变，不设置空字符串就没问题 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-92) How to use playground
[ https://issues.apache.org/jira/browse/WEEX-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-92. --- Resolution: Fixed > How to use playground > - > > Key: WEEX-92 > URL: https://issues.apache.org/jira/browse/WEEX-92 > Project: Weex > Issue Type: Task > Components: iOS >Affects Versions: 0.12 >Reporter: wei >Assignee: Adam Feng >Priority: Blocker > Labels: weex > Original Estimate: 24h > Remaining Estimate: 24h > > Why scanning QR code use playground in phone is show a blank, i found this > [#http://dotwe.org/vue/6792fe75b4ba4661b0d154aa99618ed9/] only support code > on line. how to use playground debugger in my local? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-221) Can I use wx in my project
[
https://issues.apache.org/jira/browse/WEEX-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng resolved WEEX-221.
Resolution: Fixed
> Can I use wx in my project
> --
>
> Key: WEEX-221
> URL: https://issues.apache.org/jira/browse/WEEX-221
> Project: Weex
> Issue Type: Wish
> Components: Project
>Reporter: Xu XiaoTeng
>Assignee: zhengshihan
>Priority: Critical
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I want to find an absolute css unit to show some ui element, then I found wx
> unit is possible to implement this function. But there's some warning at
> Android App running. (The wx unit is about to deprecated in the future.)
> I know there is a faq explain this issue:
> {code:java}
> var height = 88 * 750 / env.deviceWidth{code}
> Is there a simple way to implement this function?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (WEEX-222) Sticky header in waterfall is not sticky
[ https://issues.apache.org/jira/browse/WEEX-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-222. Resolution: Fixed > Sticky header in waterfall is not sticky > > > Key: WEEX-222 > URL: https://issues.apache.org/jira/browse/WEEX-222 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: Playground App Android >Reporter: biaomingzhong >Assignee: zhengshihan >Priority: Critical > > * Just upgrade weex_sdk to 0.18.0. But the sticky header is not sticky in > playground app. > * [DotWe link is official waterfall > example|http://dotwe.org/vue/7a9195643e9e8da352b0d879cdbe68c0] > * I have tried this waterfall example in Taobao app. Scan result has same > problem that the sticky header is not sticky. > * But I downgrade to SDK 0.17. It works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-223) Wrong Weex SDK version in example
[ https://issues.apache.org/jira/browse/WEEX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-223. Resolution: Fixed Fixed by republishing > Wrong Weex SDK version in example > - > > Key: WEEX-223 > URL: https://issues.apache.org/jira/browse/WEEX-223 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: android 0.18.0 >Reporter: biaomingzhong >Assignee: zhengshihan >Priority: Major > > I am using Bintray JCenter 0.18.0 version. While having explicitly version in > my build.gradle file, when I try out the Official example about Weex > Environment, the version in page showing is 0.17.0 > [DotWe link is official waterfall > example|http://dotwe.org/vue/22ed65f7797069cb6763cd741496972f] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-222) Sticky header in waterfall is not sticky
[ https://issues.apache.org/jira/browse/WEEX-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-222. -- Assignee: Adam Feng (was: zhengshihan) > Sticky header in waterfall is not sticky > > > Key: WEEX-222 > URL: https://issues.apache.org/jira/browse/WEEX-222 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: Playground App Android >Reporter: biaomingzhong >Assignee: Adam Feng >Priority: Critical > > * Just upgrade weex_sdk to 0.18.0. But the sticky header is not sticky in > playground app. > * [DotWe link is official waterfall > example|http://dotwe.org/vue/7a9195643e9e8da352b0d879cdbe68c0] > * I have tried this waterfall example in Taobao app. Scan result has same > problem that the sticky header is not sticky. > * But I downgrade to SDK 0.17. It works. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-223) Wrong Weex SDK version in example
[ https://issues.apache.org/jira/browse/WEEX-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-223. -- > Wrong Weex SDK version in example > - > > Key: WEEX-223 > URL: https://issues.apache.org/jira/browse/WEEX-223 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.18 > Environment: android 0.18.0 >Reporter: biaomingzhong >Assignee: zhengshihan >Priority: Major > > I am using Bintray JCenter 0.18.0 version. While having explicitly version in > my build.gradle file, when I try out the Official example about Weex > Environment, the version in page showing is 0.17.0 > [DotWe link is official waterfall > example|http://dotwe.org/vue/22ed65f7797069cb6763cd741496972f] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-221) Can I use wx in my project
[
https://issues.apache.org/jira/browse/WEEX-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng closed WEEX-221.
--
Assignee: Adam Feng (was: zhengshihan)
> Can I use wx in my project
> --
>
> Key: WEEX-221
> URL: https://issues.apache.org/jira/browse/WEEX-221
> Project: Weex
> Issue Type: Wish
> Components: Project
>Reporter: Xu XiaoTeng
>Assignee: Adam Feng
>Priority: Critical
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I want to find an absolute css unit to show some ui element, then I found wx
> unit is possible to implement this function. But there's some warning at
> Android App running. (The wx unit is about to deprecated in the future.)
> I know there is a faq explain this issue:
> {code:java}
> var height = 88 * 750 / env.deviceWidth{code}
> Is there a simple way to implement this function?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (WEEX-57) android aar connot download
[ https://issues.apache.org/jira/browse/WEEX-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-57. --- Resolution: Fixed > android aar connot download > --- > > Key: WEEX-57 > URL: https://issues.apache.org/jira/browse/WEEX-57 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.13 >Reporter: marekchen >Assignee: zhengshihan >Priority: Critical > > android studio use compile 'weex-project:weex_sdk:0.13.1', > get hint : > Error:(33, 14) Failed to resolve: weex-project:weex_sdk:0.13.1 > href="openFile:C:/develope/calendar/platforms/android/weexplugin/build.gradle">Show > in FileShow in > Project Structure dialog -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (WEEX-272) weex 集成到android 端时 使用vuex store 的界面报错
[ https://issues.apache.org/jira/browse/WEEX-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-272: -- Assignee: Hanks Zhang (was: zhengshihan) > weex 集成到android 端时 使用vuex store 的界面报错 > -- > > Key: WEEX-272 > URL: https://issues.apache.org/jira/browse/WEEX-272 > Project: Weex > Issue Type: Bug > Components: Android >Reporter: shanyong >Assignee: Hanks Zhang >Priority: Major > Attachments: 1.png > > > 03-30 14:55:25.501 26596-26618/com.weex.app D/jsLog: TypeError: undefined is > not an object (evaluating 'this.$store.state')__ERROR -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-249) [iOS]fix WXRuleManager multi-thread crash
[ https://issues.apache.org/jira/browse/WEEX-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-249. Resolution: Fixed > [iOS]fix WXRuleManager multi-thread crash > - > > Key: WEEX-249 > URL: https://issues.apache.org/jira/browse/WEEX-249 > Project: Weex > Issue Type: Bug > Components: iOS >Reporter: XuYouyang >Assignee: Adam Feng >Priority: Major > Attachments: WX20180315-114430.png, WX20180315-114554.png, > WX20180315-114848.png > > > fontFamilyDic type is WXThreadSafeMutableDictionary in WXUtility.m but the > real type is NSMutableDictionary created in WXRuleManager.m. > It may cause crash in multi-thread. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-271) Extend the pulldown WXRefreshComponent to support immediate load of the appear
[ https://issues.apache.org/jira/browse/WEEX-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-271. Resolution: Fixed > Extend the pulldown WXRefreshComponent to support immediate load of the appear > -- > > Key: WEEX-271 > URL: https://issues.apache.org/jira/browse/WEEX-271 > Project: Weex > Issue Type: Improvement > Components: iOS >Affects Versions: 0.18 > Environment: iOS 8.0+ >Reporter: mengjianjun >Assignee: Adam Feng >Priority: Major > Original Estimate: 48h > Remaining Estimate: 48h > > WXRefreshComponent current only support the ②, shuold add new type of①. > // ①refreshForAppear: load more when refresh component begin appear(if scroll > is dragging or decelerating, should delay) > // ②refreshForWholeVisible: load more until the whole refresh component > visible > NSString *_refreshType; -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-270) WXListComponent should add reload type of data update
[ https://issues.apache.org/jira/browse/WEEX-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-270. Resolution: Fixed > WXListComponent should add reload type of data update > - > > Key: WEEX-270 > URL: https://issues.apache.org/jira/browse/WEEX-270 > Project: Weex > Issue Type: New Feature > Components: iOS >Affects Versions: 0.18 > Environment: iOS 8.0+ >Reporter: mengjianjun >Assignee: Adam Feng >Priority: Major > Original Estimate: 48h > Remaining Estimate: 48h > > Currently WXListComponent data update only supports insertRows. This can't be > satisfied under some drop-down loading scenes. For example, the pulldown load > needs to be positioned to the original position. When the tableView is still > decaling and inserts and tries to fix the position, the cell will blink. > Because when deceiring, the externally modified contentOffset will be > re-edited by the internal implementation of tableView, altering contentOffset > alternately will cause flicker problems. If you use the tableView reloadData > this is not a problem, so you need to support the WXListComponent in the > drop-down restore location scene to add the reload attribute. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-268) Expose UpdateLayout function
[ https://issues.apache.org/jira/browse/WEEX-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-268. Resolution: Fixed > Expose UpdateLayout function > > > Key: WEEX-268 > URL: https://issues.apache.org/jira/browse/WEEX-268 > Project: Weex > Issue Type: New Feature > Components: Android >Reporter: chuyi >Assignee: zhengshihan >Priority: Minor > > Some plugin like bindingx(github.com/alibaba/bindingx) need a global > updateLayout function. So that they can invalidate view's layout. > https://github.com/apache/incubator-weex/pull/1089 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-267) monitor the frequency of module invoke
[ https://issues.apache.org/jira/browse/WEEX-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-267. Resolution: Fixed > monitor the frequency of module invoke > -- > > Key: WEEX-267 > URL: https://issues.apache.org/jira/browse/WEEX-267 > Project: Weex > Issue Type: Improvement > Components: iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > add an extra method for monitor protocol instead of commit the frequency of > module usage in monitor alarm -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (WEEX-264) waterfall组件在计算时候产生CRASH
[
https://issues.apache.org/jira/browse/WEEX-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng reassigned WEEX-264:
--
Assignee: xingZhang (was: Adam Feng)
> waterfall组件在计算时候产生CRASH
> ---
>
> Key: WEEX-264
> URL: https://issues.apache.org/jira/browse/WEEX-264
> Project: Weex
> Issue Type: Bug
> Components: iOS
>Affects Versions: 0.17
> Environment: 飞猪客户端8.5.9线上版本，不是必先，能否在组件内部添加对应保护
>Reporter: lichetnao
>Assignee: xingZhang
>Priority: Major
>
> # {{*** Terminating app due to uncaught exception 'CALayerInvalidGeometry',
> reason: 'CALayer position contains NaN: [nan 0.33]'}}
> # {{}}
> # {{Last Exception Backtrace:}}
> # {{0 CoreFoundation 0x0001866aefe0 __exceptionPreprocess :124 (in
> CoreFoundation)}}
> # {{1 libobjc.A.dylib 0x000185110538 _objc_exception_throw :56 (in
> libobjc.A.dylib)}}
> # {{2 CoreFoundation 0x0001866aef28 +[NSException raise:format:] :116
> (in CoreFoundation)}}
> # {{3 QuartzCore 0x0001899c5acc CA::Layer::set_position(CA::Vec2 const&,
> bool) :156 (in QuartzCore)}}
> # {{4 QuartzCore 0x0001899c5c48 -[CALayer setPosition:] :44 (in
> QuartzCore)}}
> # {{5 UIKit 0x00018c839d74 -[UIView setCenter:] :228 (in UIKit)}}
> # {{6 UIKit 0x00018c8440b0 -[UICollectionReusableView
> _setLayoutAttributes:] :232 (in UIKit)}}
> # {{7 UIKit 0x00018c816020 +[UIView(UIViewAnimationWithBlocks)
> _setupAnimationWithDuration:delay:view:options:factory:animations:start:animationStateGenerator:completion:]
> :644 (in UIKit)}}
> # {{8 UIKit 0x00018c82c718 +[UIView(UIViewAnimationWithBlocks)
> animateWithDuration:delay:options:animations:completion:] :108 (in UIKit)}}
> # {{9 UIKit 0x00018d0d46a4 -[UICollectionViewAnimation
> startWithAnimator:] :1364 (in UIKit)}}
> # {{10 UIKit 0x00018d0ee24c __71-[UICollectionView
> _updateWithItems:tentativelyForReordering:animator:]_block_invoke.2030 :932
> (in UIKit)}}
> # {{11 UIKit 0x00018c816020 +[UIView(UIViewAnimationWithBlocks)
> _setupAnimationWithDuration:delay:view:options:factory:animations:start:animationStateGenerator:completion:]
> :644 (in UIKit)}}
> # {{12 UIKit 0x00018c82c718 +[UIView(UIViewAnimationWithBlocks)
> animateWithDuration:delay:options:animations:completion:] :108 (in UIKit)}}
> # {{13 UIKit 0x00018d0ed684 -[UICollectionView
> _updateWithItems:tentativelyForReordering:animator:] :5212 (in UIKit)}}
> # {{14 UIKit 0x00018d0eaf24 -[UICollectionView
> _endItemAnimationsWithInvalidationContext:tentativelyForReordering:animator:]
> :12952 (in UIKit)}}
> # {{15 UIKit 0x00018d0ee894 -[UICollectionView
> _endUpdatesWithInvalidationContext:tentativelyForReordering:animator:] :92
> (in UIKit)}}
> # {{16 UIKit 0x00018d0eeb74 -[UICollectionView
> _performBatchUpdates:completion:invalidationContext:tentativelyForReordering:animator:]
> :384 (in UIKit)}}
> # {{17 UIKit 0x00018d0ee9d4 -[UICollectionView
> _performBatchUpdates:completion:invalidationContext:tentativelyForReordering:]
> :96 (in UIKit)}}
> # {{18 UIKit 0x00018d0ee958 -[UICollectionView
> _performBatchUpdates:completion:invalidationContext:] :84 (in UIKit)}}
> # {{19 UIKit 0x00018c9b70d0 -[UICollectionView
> performBatchUpdates:completion:] :64 (in UIKit)}}
> # {{20 Portal 0x0001025d85ec -[WXRecyclerUpdateController
> performBatchUpdates] WXRecyclerUpdateController.m:168 (in Portal)}}
> # {{21 libdispatch.dylib 0x0001855669e0 }}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (WEEX-266) slider component's infinite attribute doesn't work
[ https://issues.apache.org/jira/browse/WEEX-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-266: -- Assignee: xingZhang (was: Adam Feng) > slider component's infinite attribute doesn't work > -- > > Key: WEEX-266 > URL: https://issues.apache.org/jira/browse/WEEX-266 > Project: Weex > Issue Type: Bug > Components: iOS >Affects Versions: 0.17 >Reporter: alen he >Assignee: xingZhang >Priority: Major > > No matter set the infinite attribute to false or true, the slider always > scroll infinity. > > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (WEEX-265) slider-neighbor组件在IOS上超过四个展示异常
[ https://issues.apache.org/jira/browse/WEEX-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-265: -- Assignee: xingZhang (was: Adam Feng) > slider-neighbor组件在IOS上超过四个展示异常 > -- > > Key: WEEX-265 > URL: https://issues.apache.org/jira/browse/WEEX-265 > Project: Weex > Issue Type: Bug > Components: iOS >Affects Versions: 0.18 > Environment: IOS 11 >Reporter: sunnylin >Assignee: xingZhang >Priority: Major > Labels: slider-neighbor > > 我们在使用slider-neighbor组件时发现，在IOS上，当slider-item超过4个，从第5个开始会重复前4个slider-item的数据。而且，数据的排序是随机的。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-261) Flat GUI NullPointerException fix
[ https://issues.apache.org/jira/browse/WEEX-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-261. Resolution: Fixed > Flat GUI NullPointerException fix > - > > Key: WEEX-261 > URL: https://issues.apache.org/jira/browse/WEEX-261 > Project: Weex > Issue Type: Improvement >Reporter: codefurture >Assignee: Adam Feng >Priority: Trivial > > Flat GUI NullPointerException fix -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-262) Add new interface of Instance to terminate rendering when js bundle download finished.
[ https://issues.apache.org/jira/browse/WEEX-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-262. Resolution: Fixed > Add new interface of Instance to terminate rendering when js bundle download > finished. > > > Key: WEEX-262 > URL: https://issues.apache.org/jira/browse/WEEX-262 > Project: Weex > Issue Type: New Feature >Reporter: ningli >Assignee: Adam Feng >Priority: Major > > We hope to have some chance to process the jsbundle when download finished, > then we will call another interface "renderWithView" to continue rendering. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-244) Weex Android Support W3c Force Api
[ https://issues.apache.org/jira/browse/WEEX-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-244. Resolution: Fixed > Weex Android Support W3c Force Api > -- > > Key: WEEX-244 > URL: https://issues.apache.org/jira/browse/WEEX-244 > Project: Weex > Issue Type: Improvement > Components: Android >Reporter: codefurture >Assignee: zhengshihan >Priority: Trivial > > * > [https://github.com/apache/incubator-weex-site/pull/90/files] > > > [https://developer.mozilla.org/en-US/docs/Web/API/Touch/force] > > * [http://dotwe.org/vue/91b6929f4f9f97a099a30c516dc2db06] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-218) support leftGap and rightGap for cell in waterfall component
[ https://issues.apache.org/jira/browse/WEEX-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-218. Resolution: Fixed > support leftGap and rightGap for cell in waterfall component > - > > Key: WEEX-218 > URL: https://issues.apache.org/jira/browse/WEEX-218 > Project: Weex > Issue Type: Improvement >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > support leftGap and rightGap attributes for cell in waterfall component > try case: [http://dotwe.org/vue/16ca2c8a9b0d7298f67bc0e7a1314c15] > [http://dotwe.org/vue/76712cdd7c3cf665717397b51ee1c60c] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-219) copy action for text component
[ https://issues.apache.org/jira/browse/WEEX-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-219. Resolution: Fixed > copy action for text component > -- > > Key: WEEX-219 > URL: https://issues.apache.org/jira/browse/WEEX-219 > Project: Weex > Issue Type: Improvement > Components: iOS >Reporter: xingZhang >Assignee: xingZhang >Priority: Major > > add copy action for text component > you can specify an attribute disableCopy='true' to enable the copy action by > long press, default is disable. > > try case :[ > http://dotwe.org/vue/77b7d735efaf55d6b84c5c8fb5196bd9|http://dotwe.org/vue/77b7d735efaf55d6b84c5c8fb5196bd9] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-210) Weex Auto Scan Component And Module Discover Mechanism
[ https://issues.apache.org/jira/browse/WEEX-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-210. Resolution: Fixed > Weex Auto Scan Component And Module Discover Mechanism > -- > > Key: WEEX-210 > URL: https://issues.apache.org/jira/browse/WEEX-210 > Project: Weex > Issue Type: Improvement >Reporter: codefurture >Assignee: Adam Feng >Priority: Major > > Weex Auto Component And Module Discover Mechanism, None Need Center Register > Component or Module. Just Use An Customer Config -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-212) When PlaceHolder is empty, should not use rewrite url, it will return bundle url
[ https://issues.apache.org/jira/browse/WEEX-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-212. Resolution: Fixed > When PlaceHolder is empty, should not use rewrite url, it will return bundle > url > > > Key: WEEX-212 > URL: https://issues.apache.org/jira/browse/WEEX-212 > Project: Weex > Issue Type: Improvement >Reporter: codefurture >Assignee: Adam Feng >Priority: Major > Attachments: 粘贴图片.png > > > 粘贴图片.png !image-2018-02-08-17-51-25-153.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-209) Weex Wson Add Benchmark Module And Test Sample
[ https://issues.apache.org/jira/browse/WEEX-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-209. Resolution: Fixed > Weex Wson Add Benchmark Module And Test Sample > -- > > Key: WEEX-209 > URL: https://issues.apache.org/jira/browse/WEEX-209 > Project: Weex > Issue Type: Improvement >Reporter: codefurture >Assignee: Adam Feng >Priority: Major > > Weex Wson Add Benchmark Module And Test Sample -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (WEEX-211) crash in text component on iOS10
[ https://issues.apache.org/jira/browse/WEEX-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-211: -- Assignee: xingZhang (was: Adam Feng) > crash in text component on iOS10 > > > Key: WEEX-211 > URL: https://issues.apache.org/jira/browse/WEEX-211 > Project: Weex > Issue Type: Bug > Components: iOS > Environment: iPad iOS 10.0.2 >Reporter: fjzznjsh >Assignee: xingZhang >Priority: Major > > Exception Type: SIGSEGV > Exception Codes: SEGV_ACCERR at 00 > Crashed Thread: 48 > Thread 48 Name: com.taobao.weex.component > Thread 48 Crashed: > 0 CoreFoundation 0x00018a80e174 CFStringCreateCopy + 28 > 1 CoreText 0x00018d5e0b18 > TCharStreamCFString::TCharStreamCFString(__CFString const*, __CFDictionary > const*) + 60 > 2 CoreText 0x00018d57adf0 > TTypesetter::RelayoutRun(std::__1::tuple void const* (*)(__CTRun const*, __CFString const*, void*), void*, > std::__1::shared_ptr*, unsigned int, unsigned char> > const&, CTRun*) + 220 > 3 CoreText 0x00018d55fe04 > TTypesetter::MakeLineConsistent(std::__1::tuple const*, void const* (*)(__CTRun const*, __CFString const*, void*), void*, > std::__1::shared_ptr*, unsigned int, unsigned char> > const&, TLine&) + 92 > 4 CoreText 0x00018d55fd1c > TTypesetter::FinishLineFill(std::__1::tuple void const* (*)(__CTRun const*, __CFString const*, void*), void*, > std::__1::shared_ptr*, unsigned int, unsigned char> > const&, TLine&, double, double) + 40 > 5 CoreText 0x00018d553248 > CTLineCreateFromLineWithOffset + 172 > 6 UIFoundation 0x0001906e1acc ___NSStringDrawingEngine > + 11296 > 7 UIFoundation 0x0001906e5724 > -[NSAttributedString(NSExtendedStringDrawing) > boundingRectWithSize:options:context:] + 584 > 8 EGame 0x0001007e1d2c -[WXTextComponent > calculateTextHeightWithWidth:] + 116 > 9 EGame 0x0001007df460 ___31-[WXTextComponent > measureBlock]_block_invoke + 96 > 10 EGame 0x0001007e706c _cssNodeMeasure + 72 > 11 EGame 0x00010088d314 _wx_layoutNode + 1572 > 12 EGame 0x00010088d930 _wx_layoutNode + 3136 > 12 EGame 0x00010088d930 _wx_layoutNode + 3136 > 12 EGame 0x00010088d930 _wx_layoutNode + 3136 > 12 EGame 0x00010088d930 _wx_layoutNode + 3136 > 12 EGame 0x00010088d930 _wx_layoutNode + 3136 > 17 EGame 0x00010083aaf8 -[WXCellComponent > _calculateFrameWithSuperAbsolutePosition:gatherDirtyComponents:] + 308 > 18 EGame 0x0001007e78ec -[WXComponent(Layout) > _calculateFrameWithSuperAbsolutePosition:gatherDirtyComponents:] + 524 > 19 EGame 0x000100862c08 -[WXScrollerComponent > _calculateFrameWithSuperAbsolutePosition:gatherDirtyComponents:] + 460 > 18 EGame 0x0001007e78ec -[WXComponent(Layout) > _calculateFrameWithSuperAbsolutePosition:gatherDirtyComponents:] + 524 > 21 EGame 0x00010080466c -[WXComponentManager > _layout] + 324 > 22 EGame 0x0001008044ac -[WXComponentManager > _layoutAndSyncUI] + 28 > 23 EGame 0x000100800b88 -[WXComponentManager > _recursivelyAddComponent:toSupercomponent:atIndex:appendingInTree:] + 860 > 24 EGame 0x00010080080c -[WXComponentManager > addComponent:toSupercomponent:atIndex:appendingInTree:] + 120 > 25 EGame 0x00010087e988 ___42-[WXBridgeContext > registerGlobalFunctions]_block_invoke_2 + 340 > 26 EGame 0x0001007ff714 +[WXComponentManager > _performBlockOnComponentThread:] + 224 > 27 Foundation 0x00018b4166ec > ___NSThreadPerformPerform + 340 > 28 CoreFoundation 0x00018a8de278 > ___CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24 > + 24 > 29 CoreFoundation 0x00018a8ddbc0 ___CFRunLoopDoSources0 + > 524 > 30 CoreFoundation 0x00018a8db7c0 ___CFRunLoopRun + 804 > 24 CoreFoundation 0x00018a80a048 CFRunLoopRunSpecific + > 436 > 4 Foundation 0x00018b318b1c -[NSRunLoop(NSRunLoop) > runMode:beforeDate:] + 304 > 33 EGame 0x0001007ff5f8 -[WXComponentManager > _runLoopThread] + 264 > 6 Foundation 0x00018b41650c ___NSThread_
[jira] [Resolved] (WEEX-208) 两个结构类似的数据合并前，产生数据污染
[ https://issues.apache.org/jira/browse/WEEX-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-208. Resolution: Fixed > 两个结构类似的数据合并前，产生数据污染 > --- > > Key: WEEX-208 > URL: https://issues.apache.org/jira/browse/WEEX-208 > Project: Weex > Issue Type: Bug > Components: Web Renderer >Affects Versions: 0.12 >Reporter: 华逢义 >Assignee: Danz He >Priority: Major > Attachments: Catch(02-07-15-24-02).jpg, Catch367C(02-07-15-24-02).jpg > > Original Estimate: 12h > Remaining Estimate: 12h > > 代码： > > !Catch(02-07-15-24-02).jpg! > LOG: > !Catch367C(02-07-15-24-02).jpg! > > > 数据污染了，合并前并没有任何操作，但是没定义var1["2"]的visibility，仍然被初始化为visibility=2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-18) bubble up event of click in android
[ https://issues.apache.org/jira/browse/WEEX-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-18. --- Resolution: Fixed > bubble up event of click in android > --- > > Key: WEEX-18 > URL: https://issues.apache.org/jira/browse/WEEX-18 > Project: Weex > Issue Type: Improvement > Environment: weex_sdk 0.11 / 0.10 >Reporter: xingjiu >Assignee: Adam Feng >Priority: Major > Labels: android, event > Original Estimate: 672h > Remaining Estimate: 672h > > Binding a click event on child element, when the parent element binding a > long press event. Then just long press at the child element. > Two mistakes occurs: > 1. the parent long press event not be fired. > 2. the child click event fired. > Demo is at http://dotwe.org/weex/a20e3898b3875e04d28ef394509d2088 > I know this is a hard work to resolve it, while we can find out a solution > firstly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-33) Config Ability in weex
[ https://issues.apache.org/jira/browse/WEEX-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-33. --- Resolution: Fixed > Config Ability in weex > -- > > Key: WEEX-33 > URL: https://issues.apache.org/jira/browse/WEEX-33 > Project: Weex > Issue Type: New Feature >Reporter: xingjiu >Assignee: xingZhang >Priority: Major > Original Estimate: 504h > Remaining Estimate: 504h > > Background： > As we know, weex now has NO config module. Every mobile of weex are using the > same config (the config in source code). > More and more module or component requires the ability to sperate one from > each other. > Such as Prefetch, Prerender module. There should be a way to config the how > the module works, like how many items it cound do the prefetch. This config > will be different in different apps. > Solution: > Add a module named of WXConfigModule in weex_sdk, a simple key-value storage > is enough. > API is > void setConfig(String name, Object value) > Object getConfig(String name) > void sync(String name) // get the lastest config from server > void syncAll() > void invalid(String name) // option. invalid a config for once, using in > debug of bugfix scenario > The default implement is calling the config interface. > App like TAOBAO will using orange to sync configs from server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-19) Weex(iOS)，If want to let the frame adjust content's height, you need set frame(0, 0, width, NAN), but it sometime will crash
[
https://issues.apache.org/jira/browse/WEEX-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Feng resolved WEEX-19.
---
Resolution: Fixed
> Weex(iOS)，If want to let the frame adjust content's height, you need set
> frame(0, 0, width, NAN), but it sometime will crash
>
>
> Key: WEEX-19
> URL: https://issues.apache.org/jira/browse/WEEX-19
> Project: Weex
> Issue Type: Bug
> Environment: iOS
>Reporter: yuedong
>Assignee: xingZhang
>Priority: Major
>
> - (void)setFrame:(CGRect)frame
> {
> if (!CGRectEqualToRect(frame, _frame)) {
> _frame = frame;
> WXPerformBlockOnMainThread(^{
> if (_rootView) {
> _rootView.frame = frame;
> WXPerformBlockOnComponentThread(^{
> [self.componentManager rootViewFrameDidChange:frame];
> });
> }
> });
> }
> }
> if the _rootView is not nil, the frame(0, 0, width, NAN) will direct set to
> _rootView, then will crash.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (WEEX-43) Add release job to travis CI
[ https://issues.apache.org/jira/browse/WEEX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-43. - Resolution: Incomplete > Add release job to travis CI > > > Key: WEEX-43 > URL: https://issues.apache.org/jira/browse/WEEX-43 > Project: Weex > Issue Type: Task > Components: Project >Reporter: sospartan >Assignee: Zechang Xie >Priority: Major > > Some changes will make to project's travis config: > * Put commands to `.travis` config use `if` statement, avoid using script > file will make more easier to determine problems. > * Add our release test > * Create a release source tarball > * test build script for source release > * upload daily build artfacts (This will wait until we add snapshot upload > script) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-35) A component open URL got different action on iOS and Android
[ https://issues.apache.org/jira/browse/WEEX-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-35. --- Resolution: Fixed > A component open URL got different action on iOS and Android > > > Key: WEEX-35 > URL: https://issues.apache.org/jira/browse/WEEX-35 > Project: Weex > Issue Type: Bug > Environment: iOS, Android >Reporter: Isken Huang >Assignee: xingZhang >Priority: Major > > iOS: > https://github.com/apache/incubator-weex/blob/master/ios/sdk/WeexSDK/Sources/Component/WXAComponent.m#L63 > Android: > https://github.com/apache/incubator-weex/blob/master/android/sdk/src/main/java/com/taobao/weex/ui/component/WXA.java#L53 > iOS SDK's is when href exist and string length more then 0 to do something. > Android SDK's is when href is not null to do something. This logic should be > the same. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo
[ https://issues.apache.org/jira/browse/WEEX-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-44. --- Resolution: Fixed > Add script to upload snapshot artifact to maven/pods repo > - > > Key: WEEX-44 > URL: https://issues.apache.org/jira/browse/WEEX-44 > Project: Weex > Issue Type: Sub-task > Components: Project >Reporter: sospartan >Assignee: xingZhang >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-45) clearTimeout and clearInterval doesn't work when funId is greater than 127
[ https://issues.apache.org/jira/browse/WEEX-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-45. --- Resolution: Fixed > clearTimeout and clearInterval doesn't work when funId is greater than 127 > -- > > Key: WEEX-45 > URL: https://issues.apache.org/jira/browse/WEEX-45 > Project: Weex > Issue Type: Bug >Reporter: YorkShen >Assignee: YorkShen >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-52) Add auto for ImageQuality
[ https://issues.apache.org/jira/browse/WEEX-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-52. - Resolution: Fixed > Add auto for ImageQuality > - > > Key: WEEX-52 > URL: https://issues.apache.org/jira/browse/WEEX-52 > Project: Weex > Issue Type: New Feature > Components: Android >Reporter: YorkShen >Assignee: YorkShen >Priority: Major > Fix For: 0.15 > > > Add auto for ImageQuality, and the imageAdapter decides the meaning of auto. > The default of quality will be changed to auto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-66) Support FlatGUI
[ https://issues.apache.org/jira/browse/WEEX-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-66. --- Resolution: Fixed > Support FlatGUI > --- > > Key: WEEX-66 > URL: https://issues.apache.org/jira/browse/WEEX-66 > Project: Weex > Issue Type: New Feature >Reporter: YorkShen >Assignee: YorkShen >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-65) Refactor the implementation of resize on image
[ https://issues.apache.org/jira/browse/WEEX-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-65. --- Resolution: Fixed > Refactor the implementation of resize on image > -- > > Key: WEEX-65 > URL: https://issues.apache.org/jira/browse/WEEX-65 > Project: Weex > Issue Type: Improvement >Reporter: YorkShen >Assignee: YorkShen >Priority: Minor > > There is no need that the resize attribute on image relies on > ImageView.scaleType. Make ImageDrawable do all the work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-68) Android timer supports float
[ https://issues.apache.org/jira/browse/WEEX-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-68. --- Resolution: Fixed > Android timer supports float > > > Key: WEEX-68 > URL: https://issues.apache.org/jira/browse/WEEX-68 > Project: Weex > Issue Type: New Feature > Components: Android >Affects Versions: 0.16 >Reporter: YorkShen >Assignee: YorkShen >Priority: Major > Fix For: 0.16 > > > The timer in Android will supports float interval/delay and transform them to > int, as some codes always ignore the doc and pass float value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-73) Add “onPullingDownEnd” Method in WXRefresh component
[ https://issues.apache.org/jira/browse/WEEX-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-73. --- Resolution: Fixed > Add “onPullingDownEnd” Method in WXRefresh component > > > Key: WEEX-73 > URL: https://issues.apache.org/jira/browse/WEEX-73 > Project: Weex > Issue Type: New Feature > Components: Android, iOS >Affects Versions: 0.13 >Reporter: kacakong >Assignee: zhengshihan >Priority: Major > > When the Refresh component is used, the onRefresh is not executed immediately > after the execution of the onPullingDown, but the onRefresh is executed after > the animation execution has completed. Please add a onPullingDownEnd method > to execute before the animation starts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-70) weex pull request rules discuss
[ https://issues.apache.org/jira/browse/WEEX-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-70. - Resolution: Won't Fix > weex pull request rules discuss > --- > > Key: WEEX-70 > URL: https://issues.apache.org/jira/browse/WEEX-70 > Project: Weex > Issue Type: Improvement > Components: Project >Affects Versions: 0.17 >Reporter: Zechang Xie >Assignee: Adam Feng >Priority: Major > > weex pull request rules discuss for better run weex in apache. > give me your suggest. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-71) weex commit and pr log rules discuss
[ https://issues.apache.org/jira/browse/WEEX-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-71. - Resolution: Won't Fix > weex commit and pr log rules discuss > > > Key: WEEX-71 > URL: https://issues.apache.org/jira/browse/WEEX-71 > Project: Weex > Issue Type: Improvement > Components: Project >Affects Versions: 0.17 >Reporter: Zechang Xie >Assignee: Zechang Xie >Priority: Major > Labels: discussion > > weex commit and pr log rules discuss for better running weex in apache -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-77) weex闪退问题
[ https://issues.apache.org/jira/browse/WEEX-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-77. - Resolution: Cannot Reproduce > weex闪退问题 > > > Key: WEEX-77 > URL: https://issues.apache.org/jira/browse/WEEX-77 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.16 >Reporter: bangyuezou >Assignee: zhengshihan >Priority: Major > > 1Caused by: java.lang.ArrayIndexOutOfBoundsException: length=8192; index=8192 > 2at com.android.okhttp.okio.Buffer.writeUtf8(Buffer.java:818) > 3at com.android.okhttp.okio.Buffer.writeUtf8(Buffer.java:793) > 4at > com.android.okhttp.okio.RealBufferedSink.writeUtf8(RealBufferedSink.java:57) > 5at > com.android.okhttp.internal.http.HttpConnection.writeRequest(HttpConnection.java:172) > 6at > com.android.okhttp.internal.http.HttpTransport.writeRequestHeaders(HttpTransport.java:76) > 7at > com.android.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:766) > 8at > com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:463) > 9at > com.android.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:405) > 10at > com.android.okhttp.internal.huc.HttpURLConnectionImpl.getHeaders(HttpURLConnectionImpl.java:162) > 11at > com.android.okhttp.internal.huc.HttpURLConnectionImpl.getHeaderFields(HttpURLConnectionImpl.java:222) > 12at > com.networkbench.agent.impl.instrumentation.NBSHttpURLConnectionExtension.getHeaderFields(SourceFile) > 13at > com.taobao.weex.adapter.DefaultWXHttpAdapter$1.run(DefaultWXHttpAdapter.java) > 14at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) > 15at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) > 16at java.lang.Thread.run(Thread.java:776) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (WEEX-80) component add offset attribute
[ https://issues.apache.org/jira/browse/WEEX-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng closed WEEX-80. - Resolution: Won't Fix > component add offset attribute > --- > > Key: WEEX-80 > URL: https://issues.apache.org/jira/browse/WEEX-80 > Project: Weex > Issue Type: Improvement >Reporter: shenbin >Assignee: Adam Feng >Priority: Major > > in some situation，we do not want sticky element fixed on the top of the > scroll container, but have a offset height from the top。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-83) Image padding properties not works on ios
[ https://issues.apache.org/jira/browse/WEEX-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-83. --- Resolution: Fixed > Image padding properties not works on ios > - > > Key: WEEX-83 > URL: https://issues.apache.org/jira/browse/WEEX-83 > Project: Weex > Issue Type: Bug >Reporter: xingjiu >Assignee: Adam Feng >Priority: Major > Attachments: IMG_4300.png, Screenshot_20171013-154820_[b...@176f60.png > > Original Estimate: 168h > Remaining Estimate: 168h > > Demo here：http://dotwe.org/vue/3cbf678439d909a53513eca8ca52a986 > padding not works at image component on iOS. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-86) Reorganize the structure of documents and website
[ https://issues.apache.org/jira/browse/WEEX-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-86. --- Resolution: Fixed > Reorganize the structure of documents and website > - > > Key: WEEX-86 > URL: https://issues.apache.org/jira/browse/WEEX-86 > Project: Weex > Issue Type: Improvement > Components: Project >Reporter: Hanks Zhang >Assignee: zhengshihan >Priority: Major > > h1. Weex Document Index > + contributing.md > + development-process.md > + who-is-using-weex.md > + releasenote.md > + resources.md > h2. Guide > + index.md > + advanced > + app-architecture.md > + downgrade.md > + page-architecture.md > + path.md > + use-vuex-and-vue-router.md > + extend-android.md > + extend-ios.md > + extend-js-framework.md > + extend-web-render.md > + front-end-frameworks.md > + integrate-devtool-to-android.md > + integrate-devtool-to-ios.md > + integrate-to-your-app.md > + set-up-env.md > + using-rax.md > + using-vue.md > h2. References > + index.md > + android-apis.md > + ios-apis.md > + js-framework-apis.md > + js-service.md > + weex-variable.md > h3. Components > + a.md > + cell.md > + div.md > + image.md > + indicator.md > + input.md > + list.md > + loading.md > + refresh.md > + scroller.md > + slider.md > + switch.md > + text.md > + textarea.md > + video.md > + waterfall.md > + web.md > h3. Modules > + animation.md > + clipboard.md > + dom.md > + globalevent.md > + meta.md > + modal.md > + navigator.md > + picker.md > + storage.md > + stream.md > + websocket.md > + webview.md > h2. WiKi > + color-names.md > + common-events.md > + common-styles.md > + css-units.md > + design-principles.md > + event-bubble.md > + faq.md > + gestures.md > + index.md > + platform-difference.md > + text-styles.md > h2. Tools > + helpers.md > + index.md > + market.md > + toolkit.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-90) Remove The Legacy Weex DSL 1.0 (.we) Front-End Framework
[ https://issues.apache.org/jira/browse/WEEX-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-90. --- Resolution: Fixed > Remove The Legacy Weex DSL 1.0 (.we) Front-End Framework > > > Key: WEEX-90 > URL: https://issues.apache.org/jira/browse/WEEX-90 > Project: Weex > Issue Type: Bug >Reporter: Hanks Zhang >Assignee: Adam Feng >Priority: Major > > Weex DSL 1.0 (.we) front-end framework is inspired by Vue.js 1.0. Since Weex > supports the official Vue.js 2.0 in v0.10.0 [1] at 2017-02-17, the ".we" > framework is deprecated. In order to optimize the performance, stability, and > package size, this legacy framework should be removed from the WeexSDK. > I suggest removing the ".we" framework in the 2018 January release of WeexSDK. > For the projects who are still using the ".we" framework, you can read the > "Migration From .we Framework" [2] and "The Syntax Difference Between .we and > .vue" [3] documents to help you migrate your ".we" project to Vue.js 2.0 > project. But those documents only have Chinese version. > [1] https://github.com/alibaba/weex/releases/tag/v0.10.0 > [2] http://weex-project.io/cn/references/migration/migration-from-weex.html > [3] http://weex-project.io/cn/references/migration/difference.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-93) WXBridgeManager create multiple instances
[ https://issues.apache.org/jira/browse/WEEX-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-93. --- Resolution: Fixed > WXBridgeManager create multiple instances > - > > Key: WEEX-93 > URL: https://issues.apache.org/jira/browse/WEEX-93 > Project: Weex > Issue Type: Improvement > Components: iOS >Affects Versions: 0.16 >Reporter: Shaojun Yang >Assignee: Adam Feng >Priority: Minor > Labels: usability > > *_WXBridgeManager_* has a private class method *_sharedManager_* that only > used in *_[WXBridgeManager jsThread]_*, see > [https://github.com/apache/incubator-weex/blob/release-0.16/ios/sdk/WeexSDK/Sources/Manager/WXBridgeManager.m#L45]. > But *_[WXSDKManager bridgeMgr]_* create its own *_WXBridgeManager_* instance, > is this designed or just left over from the past? Should *_[WXSDKManager > bridgeMgr]_* just use *_[WXBridgeManager sharedManager]_*？ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (WEEX-87) * Fix that moveElement doesn't work when parent is not a list
[ https://issues.apache.org/jira/browse/WEEX-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng resolved WEEX-87. --- Resolution: Fixed > * Fix that moveElement doesn't work when parent is not a list > - > > Key: WEEX-87 > URL: https://issues.apache.org/jira/browse/WEEX-87 > Project: Weex > Issue Type: Bug >Reporter: YorkShen >Assignee: Adam Feng >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
