[jira] [Assigned] (WEEX-43) Add release job to travis CI

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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-35) A component open URL got different action on iOS and Android

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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-18) bubble up event of click in android

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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] [Assigned] (WEEX-79) Modify document website style of weex.

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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-70) weex pull request rules discuss

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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-51) The console APIs doesn't work on Android

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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-45) clearTimeout and clearInterval doesn't work when funId is greater than 127

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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-63) Android refactor lines

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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-81) shadow render wrong

2017-10-12 Thread Adam Feng (JIRA)

 [ 
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-81) shadow render wrong

2017-10-12 Thread Adam Feng (JIRA)

[ 
https://issues.apache.org/jira/browse/WEEX-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Commented] (WEEX-75) [Vote] change weex branch flow

2017-09-27 Thread Adam Feng (JIRA)

[ 
https://issues.apache.org/jira/browse/WEEX-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-77) weex闪退问题

2017-10-09 Thread Adam Feng (JIRA)

[ 
https://issues.apache.org/jira/browse/WEEX-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Resolved] (WEEX-76) Update "Set Up Development Environment" English Document

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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] [Resolved] (WEEX-60) support perspective for rotate in 3d dimension

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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] [Assigned] (WEEX-36) Fix problems in 0.12 RC3

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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 

[jira] [Assigned] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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 
> > 

[jira] [Assigned] (WEEX-43) Add release job to travis CI

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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] [Resolved] (WEEX-67) ios SDK 0.13.0

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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] [Closed] (WEEX-34) Update csslayout to Yoga

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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] [Assigned] (WEEX-64) Upgrade to API 25

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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] [Resolved] (WEEX-31) weex support Event Bubbling

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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-72) English document in "Set Up Development Environment" need to be updated

2017-10-07 Thread Adam Feng (JIRA)

 [ 
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] [Assigned] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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-49) add osName to weex.config.env

2017-10-11 Thread Adam Feng (JIRA)

 [ 
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] [Commented] (WEEX-88) BOOL arguments cannot be received correctly by component's method in 32-bit iOS devices

2017-10-24 Thread Adam Feng (JIRA)

[ 
https://issues.apache.org/jira/browse/WEEX-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-168) [iOS] AnimationModule needsLayout may show incorrect

2017-12-11 Thread Adam Feng (JIRA)

[ 
https://issues.apache.org/jira/browse/WEEX-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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-89) View with linear gradient could not render its border radius correctly

2017-10-25 Thread Adam Feng (JIRA)

[ 
https://issues.apache.org/jira/browse/WEEX-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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] [Resolved] (WEEX-166) StreamModule Improve Avoid JSON Convertor Double Twice

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-166.

Resolution: Fixed

> StreamModule Improve Avoid JSON Convertor Double Twice
> --
>
> Key: WEEX-166
> URL: https://issues.apache.org/jira/browse/WEEX-166
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> StreamModule Improve Avoid JSON Convertor Double Twice



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-167) Input Changed not fired when same with default value set

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-167.

Resolution: Fixed

> Input Changed  not fired when same with default value set
> -
>
> Key: WEEX-167
> URL: https://issues.apache.org/jira/browse/WEEX-167
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> Input Changed  not fired when same with default value set



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-165) WXParallax Move To Weex SDK

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-165.
--
Resolution: Fixed

> WXParallax Move To Weex SDK
> ---
>
> Key: WEEX-165
> URL: https://issues.apache.org/jira/browse/WEEX-165
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> WXParallax Move To Weex SDK



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-161) DURATION lost should not throw exception when toast, modal arguments improve

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-161.

Resolution: Fixed

> DURATION lost should not throw exception when toast, modal  arguments improve
> -
>
> Key: WEEX-161
> URL: https://issues.apache.org/jira/browse/WEEX-161
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> DURATION lost should not throw exception when toast



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-168) [iOS] AnimationModule needsLayout may show incorrect

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-168.

Resolution: Fixed

> [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
(v7.6.3#76005)


[jira] [Resolved] (WEEX-228) ShouldStopPropagation Use ShortName StopPropagation

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-228.

Resolution: Fixed

> ShouldStopPropagation Use ShortName  StopPropagation 
> -
>
> Key: WEEX-228
> URL: https://issues.apache.org/jira/browse/WEEX-228
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> ShouldStopPropagation Use ShortName  StopPropagation 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-220) recycle-list horizontal layout support loadmore event

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-220.

Resolution: Fixed

> recycle-list horizontal layout support loadmore event
> -
>
> Key: WEEX-220
> URL: https://issues.apache.org/jira/browse/WEEX-220
> Project: Weex
>  Issue Type: Improvement
>Reporter: ZhongZhendong
>Assignee: Adam Feng
>Priority: Major
>
> recycle-list horizontal scroll direction support `loadmore` event



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-303) [Android] fix nullPoint

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-303.
--
Resolution: Fixed

> [Android] fix nullPoint
> ---
>
> Key: WEEX-303
> URL: https://issues.apache.org/jira/browse/WEEX-303
> Project: Weex
>  Issue Type: Bug
>  Components: Android
>Reporter: peihan
>Assignee: Adam Feng
>Priority: Major
>
> fix nullPointException on multithreading case。



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-107) Android Transition Animation Supported

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-107.

Resolution: Fixed

> Android Transition Animation Supported
> --
>
> Key: WEEX-107
> URL: https://issues.apache.org/jira/browse/WEEX-107
> Project: Weex
>  Issue Type: New Feature
>  Components: Android
>Affects Versions: 0.16
>Reporter: codefurture
>Assignee: zhengshihan
>Priority: Major
>
> css transition supported on android platform: 
> https://www.w3.org/TR/css3-transitions/ 
> related issues: https://github.com/alibaba/weex/issues/2269
> weex dotwe example:
> 1、http://dotwe.org/vue/e04a6324a2deef1032d4b8b3c29da49f
> 2、http://dotwe.org/vue/46591927e77a9a23b2f8307ffb3df68f
> 3、http://dotwe.org/vue/e04a6324a2deef1032d4b8b3c29da49f
> 4、http://dotwe.org/vue/293fcc14e68c6b2771f0216648d56504
> 5、http://dotwe.org/vue/4891c9221ddfc0f910b9fd2b2f80bd35
> 6、http://dotwe.org/vue/a67c19f29d0cae4dd72c5bd772e90e84
> 7、http://dotwe.org/vue/293fcc14e68c6b2771f0216648d56504



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-109) Scroller list recycler Supported scrollstart and scrollend Event

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-109.

Resolution: Fixed

> Scroller list recycler Supported scrollstart and scrollend Event
> 
>
> Key: WEEX-109
> URL: https://issues.apache.org/jira/browse/WEEX-109
> Project: Weex
>  Issue Type: New Feature
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Minor
>
> 1、Scroller Supported scrollStart and scrollEnd Event



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-106) add instanceId to performance dict

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-106.

Resolution: Fixed

> add instanceId to performance dict
> --
>
> Key: WEEX-106
> URL: https://issues.apache.org/jira/browse/WEEX-106
> Project: Weex
>  Issue Type: New Feature
>  Components: iOS
>Affects Versions: 0.17
>Reporter: Zechang Xie
>Assignee: Adam Feng
>Priority: Major
>
> add instanceId to performance dict, that we can differentiate instance 
> exactly。
> Then we can do something like this:
> 1. get `instanceId` when deal with performance
> 2. upload performance with `instanceId`



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-160) Weex Transition Improvement for high frequency

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-160.

Resolution: Fixed

> Weex Transition Improvement for high frequency 
> ---
>
> Key: WEEX-160
> URL: https://issues.apache.org/jira/browse/WEEX-160
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> Weex Transition Improvement for high frequency 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-163) fix security weaknesses

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-163.

Resolution: Fixed

>  fix security weaknesses
> 
>
> Key: WEEX-163
> URL: https://issues.apache.org/jira/browse/WEEX-163
> Project: Weex
>  Issue Type: Bug
>Reporter: toretto
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-159) Weex Support Style Diff when update, exclude un effect layout params,

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-159.

Resolution: Fixed

> Weex Support Style Diff when update, exclude un effect  layout params,
> --
>
> Key: WEEX-159
> URL: https://issues.apache.org/jira/browse/WEEX-159
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> Weex Support Style Diff when update, exclude un effect  layout params,



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-207) statistics jsf init status

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-207.

Resolution: Fixed

> statistics jsf init status
> --
>
> Key: WEEX-207
> URL: https://issues.apache.org/jira/browse/WEEX-207
> Project: Weex
>  Issue Type: Bug
>Reporter: toretto
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-216) WXAnimation Fix Memory Leak and performance improve

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-216.

Resolution: Fixed

> WXAnimation Fix Memory Leak and performance improve
> ---
>
> Key: WEEX-216
> URL: https://issues.apache.org/jira/browse/WEEX-216
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> WXAnimation Fix Memory Leak and performance improve



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (WEEX-116) It seems vue doesn't support instance property in weex.

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-116:
--

Assignee: Hanks Zhang  (was: Adam Feng)

> It seems vue doesn't support instance property in weex.
> ---
>
> Key: WEEX-116
> URL: https://issues.apache.org/jira/browse/WEEX-116
> Project: Weex
>  Issue Type: Bug
>Reporter: Edward Zhang
>Assignee: Hanks Zhang
>Priority: Critical
> Attachments: error.png
>
>
> I want to transplant Onsen UI to weex environment. official site is below:
> https://onsen.io/
> BUT, I met some errors while i running code. It is ok to webpack my app. BUT 
> when I serve it in browser, i suppose vue do not support instance property. 
> some snippets below:
> in main.js
> {code:javascript}
> new Vue({
>   el: '#root',
>   render: h => h(AppNavigator),
>   store: new Vuex.Store(storeLike),
>   beforeCreate: function() {
> // Shortcut for Material Design
> Vue.prototype.$md = this.$ons.platform.isAndroid();  //look this line:  
> Vue.prototype.$md can not assign value to it.
>   }
> });
> {code}
> in AppSplitter.vue
> {code:html}
> 
>   
> 
>width="260px"
> :swipe-target-width="$md && 25"  
> //$md is undefined here.
> :animation="$md ? 'overlay' : 'reveal'"   
> //$md is undefined here.
> :open.sync="isOpen"
>   >
> 
>   
>   
> 
>   
> 
>   
> 
> {code}
> Error information is right below in the attachment. Does anyone tell me why? 
> And anyone who would like to help me. You can clone my github project: 
> https://github.com/Edward-Roshan/Weex-Onsen
> Does Anyone just help me to launch it?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-123) waterfall flow supported span merge

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-123.
--
Resolution: Fixed

> waterfall flow supported span merge
> ---
>
> Key: WEEX-123
> URL: https://issues.apache.org/jira/browse/WEEX-123
> Project: Weex
>  Issue Type: New Feature
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> waterfall flow supported span merge



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-113) New Touch Dispatch Mechanism And Bubble Sync Method

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-113.

Resolution: Fixed

> New Touch Dispatch Mechanism  And Bubble Sync Method
> 
>
> Key: WEEX-113
> URL: https://issues.apache.org/jira/browse/WEEX-113
> Project: Weex
>  Issue Type: New Feature
>  Components: Android, iOS
>Affects Versions: 0.17
>Reporter: codefurture
>Assignee: zhengshihan
>Priority: Major
>
> New Touch Dispatch Mechanism  And Bubble Sync Method 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-162) When Cell Position Changed , outOfVisibleRange not accurate, item.getCellPositionINScollable() get wrong position

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-162.

Resolution: Fixed

> When Cell Position Changed , outOfVisibleRange not accurate, 
> item.getCellPositionINScollable() get wrong position
> -
>
> Key: WEEX-162
> URL: https://issues.apache.org/jira/browse/WEEX-162
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> When Cell Position Changed , outOfVisibleRange not accurate, 
> item.getCellPositionINScollable() get wrong positionuse  instead.
>  boolean outOfVisibleRange = !ViewCompat.isAttachedToWindow(view);



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-175) Weex List View Supported pagingEnabled attribute

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-175.
--
Resolution: Fixed

> Weex List View Supported pagingEnabled attribute
> 
>
> Key: WEEX-175
> URL: https://issues.apache.org/jira/browse/WEEX-175
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> Weex List View Supported pagingEnabled attribute



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-171) using another flag to determine whether open devtool or not

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-171.

Resolution: Fixed

> using another flag to determine whether open devtool or not
> ---
>
> Key: WEEX-171
> URL: https://issues.apache.org/jira/browse/WEEX-171
> Project: Weex
>  Issue Type: Improvement
>Reporter: chuyi
>Assignee: Adam Feng
>Priority: Minor
>
> using another flag to determine whether open devtool or not。
> currently,we can't open devtool if WXEnvironment#isApkDebuggable is false。but 
> in some situation, we need to open it. so we need another flag.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-169) fix null pointer crash

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-169.

Resolution: Fixed

> fix null pointer crash
> --
>
> Key: WEEX-169
> URL: https://issues.apache.org/jira/browse/WEEX-169
> Project: Weex
>  Issue Type: Bug
>Reporter: toretto
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-170) WXTemplateList width should use realpx instead of viewport and post add cell archive better performance

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-170.

Resolution: Fixed

> WXTemplateList  width should use realpx instead of viewport and post add cell 
> archive better performance
> 
>
> Key: WEEX-170
> URL: https://issues.apache.org/jira/browse/WEEX-170
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Minor
>
> WXTemplateList  width should use realpx instead of viewport 
> and post add cell archive better performance, reduce waste layout when list 
> size change



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (WEEX-276) weex list data lost when I pull down to load more then pull up to refresh

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-276:
--

Assignee: codefurture  (was: Adam Feng)

> weex list data lost when I pull down to load more then pull up to refresh
> -
>
> Key: WEEX-276
> URL: https://issues.apache.org/jira/browse/WEEX-276
> Project: Weex
>  Issue Type: Bug
>  Components: Android
> Environment: android 设备,supportLibVersion 大于 "26.1.0",如26.1.0 / 
> 27.0.1 都有问题
>Reporter: zhuyifei
>Assignee: codefurture
>Priority: Critical
>
> weex list 
> 上拉加载更多然后下拉刷新出现数据丢失,稳定重显。经过排查,发现跟supportLibVersion相关,回退到25.2.0版本就没问题了,高于26.1.0就会稳定出现。
> 附上android demo https://github.com/yifei8/android-weex



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-278) Android中readerByUrl的默认超时为3秒,请开放设置接口

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-278.
--
Resolution: Fixed

Please use Engilish, thanks.

> Android中readerByUrl的默认超时为3秒,请开放设置接口
> ---
>
> Key: WEEX-278
> URL: https://issues.apache.org/jira/browse/WEEX-278
> Project: Weex
>  Issue Type: Improvement
>  Components: Android
>Affects Versions: 0.12, 0.13, 0.14, 0.15, 0.16, 0.17, 0.18
>Reporter: chen wu
>Assignee: Adam Feng
>Priority: Major
> Fix For: 0.18
>
>
> 在android中,网络访问js,
> DefaultWXHttpAdapter默认超时3秒,可不可以发开这个设置通过配置进行修改



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (WEEX-287) weex run ios报错

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-287:
--

Assignee: erha19  (was: Adam Feng)

> weex run ios报错
> --
>
> Key: WEEX-287
> URL: https://issues.apache.org/jira/browse/WEEX-287
> Project: Weex
>  Issue Type: Bug
>Reporter: tom
>Assignee: erha19
>Priority: Major
>
> Error:Error: Command failed: pod update
> env: illegal option -- u
> usage: env [-i] [name=value ...] [utility [argument ...]]
> env: illegal option -- u
> usage: env [-i] [name=value ...] [utility [argument ...]]
> at ChildProcess.exithandler (child_process.js:273:12)
>  at ChildProcess.emit (events.js:180:13)
>  at maybeClose (internal/child_process.js:936:16)
>  at Socket.stream.socket.on (internal/child_process.js:353:11)
>  at Socket.emit (events.js:180:13)
>  at Pipe._handle.close [as _onclose] (net.js:541:12)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-277) iOS 上 WXTextInputView,长按 出现 menuController ,点击删除(“delete”)出现crash

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-277.

Resolution: Fixed

> iOS 上 WXTextInputView,长按 出现 menuController ,点击删除(“delete”)出现crash
> -
>
> Key: WEEX-277
> URL: https://issues.apache.org/jira/browse/WEEX-277
> Project: Weex
>  Issue Type: Bug
>Reporter: jsonmess
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-126) scripturl will have no value in some way,we need use pageName instead

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-126.

Resolution: Fixed

> scripturl will have no value in some way,we need use pageName instead
> -
>
> Key: WEEX-126
> URL: https://issues.apache.org/jira/browse/WEEX-126
> Project: Weex
>  Issue Type: Bug
>Reporter: Zechang Xie
>Assignee: Adam Feng
>Priority: Major
>
> scripturl will have no value in some way,we need use pageName instead:
> 1.  compatible old logic;
> 2.  use instance.pageName as default for front user.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-125) iOS Transition Animation Support

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-125.

Resolution: Fixed

> iOS Transition Animation Support
> 
>
> Key: WEEX-125
> URL: https://issues.apache.org/jira/browse/WEEX-125
> Project: Weex
>  Issue Type: New Feature
>Reporter: qz
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-130) WSON High Performance Binary Data Format Supported

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-130.

Resolution: Fixed

> WSON High Performance Binary Data Format Supported
> --
>
> Key: WEEX-130
> URL: https://issues.apache.org/jira/browse/WEEX-130
> Project: Weex
>  Issue Type: New Feature
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> WSON High Performance Binary Data Format Supported



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-127) Use HashSet Instead of array, because some app not contains arrayset

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-127.

Resolution: Fixed

> Use HashSet Instead of array, because  some app not contains arrayset
> -
>
> Key: WEEX-127
> URL: https://issues.apache.org/jira/browse/WEEX-127
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Minor
>
> Use HashSet Instead of array, because  some app not contains arrayset



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-186) List Sticky Header Keep When Data Clear

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-186.

Resolution: Fixed

> List Sticky Header Keep When Data Clear
> ---
>
> Key: WEEX-186
> URL: https://issues.apache.org/jira/browse/WEEX-186
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> List Sticky Header Keep When Data Clear, Should Remove Sticky Header。



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-184) Weex Android Playground Demo Show

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-184.

Resolution: Fixed

> Weex Android Playground Demo Show
> -
>
> Key: WEEX-184
> URL: https://issues.apache.org/jira/browse/WEEX-184
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Minor
>
> Weex Android Playground Demo Show



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-177) scroll to element offset has none affect when none touch

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-177.

Resolution: Fixed

> scroll to element offset has none affect when none touch
> 
>
> Key: WEEX-177
> URL: https://issues.apache.org/jira/browse/WEEX-177
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> scroll to element offset has none affect when none touch



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-179) List View Component supported show scrollbar options

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-179.

Resolution: Fixed

> List View Component supported show scrollbar options
> 
>
> Key: WEEX-179
> URL: https://issues.apache.org/jira/browse/WEEX-179
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> List View Component supported show scrollbar options



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (WEEX-260) Support setting color about

2018-05-14 Thread Adam Feng (JIRA)

[ 
https://issues.apache.org/jira/browse/WEEX-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474184#comment-16474184
 ] 

Adam Feng commented on WEEX-260:


Greate contribution!

> Support setting color about 
> 
>
> Key: WEEX-260
> URL: https://issues.apache.org/jira/browse/WEEX-260
> Project: Weex
>  Issue Type: Improvement
>  Components: iOS
>Reporter: Apache Spark
>Assignee: Adam Feng
>Priority: Major
>
> h2. Better layout: 
> [https://gist.github.com/tw93/cd9d847b16854af13e49d996dc853a05|http://example.com/]
> h2. Background
>  * Currently, the component in Weex only support the default green color, But 
> many times the business needs to set color for the theme tone of the product, 
> So needs to support setting the color.
> h2. New Support && Demo
>  * tintColor: Background color when the switch is turned on.
>  * onTintColor: Border color and background color on Android when the switch 
> is turned off.
>  * thumbTintColor: Color of the foreground switch grip.
> |iOS|Web|
> |!https://gw.alipayobjects.com/zos/rmsportal/echgZhufHYAqYQSSSyKJ.gif|width=240!|!https://gw.alipayobjects.com/zos/rmsportal/zlyOBlQnVbloIizCdWKU.gif|width=240!|
> h2. How to Use
>  thumb-tint-color="#FF7703"
> tint-color="#850B0B"
> checked="true">
> h2. My solution
> h3. Code
>  * Weex iOS:
>  ** 
> [WXSwitchComponent.m|https://github.com/tw93/incubator-weex/blob/ios-feature-switch/ios/sdk/WeexSDK/Sources/Component/WXSwitchComponent.m]
>  * Weex Web:
>  ** 
> [switch/index.js|https://github.com/tw93/weex-vue-render/blob/master/src/components/switch/index.js]
>  ** 
> [switch/index.css|https://github.com/tw93/weex-vue-render/blob/master/src/components/switch/style.css]
>  * Weex Vue Demo:
>  ** [http://dotwe.org/vue/99a13cce5a429c7b9bce9bea24253935]
>  ** [Demo Bundle 
> JS|http://dotwe.org/raw/dist/99a13cce5a429c7b9bce9bea24253935.bundle.wx]
> h3. Details
> h4. iOS
> It can be overwritten with the 
> {{onTintColor}}、{{thumbTintColor}}、{{tintColor}} attributes of 
> {{switchView}}, as well as the job of updating the attributes.
> ...
> _switchView.onTintColor = _onTintColor;
> _switchView.thumbTintColor = _thumbTintColor;
> _switchView.tintColor = _tintColor;
> h4. Web
> Override the corresponding CSS styles.
> Welcome to put forward any suggestion about the solution or other 
> requirements for the component, Thanks!
> h2.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-253) WXScroller Handler should use mainLooper ensure main thread

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-253.

Resolution: Fixed

> WXScroller Handler should use mainLooper ensure main thread
> ---
>
> Key: WEEX-253
> URL: https://issues.apache.org/jira/browse/WEEX-253
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Minor
> Attachments: 圖片.png
>
>
> WXScroller Handler should use mainLooper ensure main thread



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (WEEX-284) supporting of gif pictures in Andriod platform

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-284:
--

Assignee: YorkShen  (was: Adam Feng)

> supporting of gif pictures in Andriod platform
> --
>
> Key: WEEX-284
> URL: https://issues.apache.org/jira/browse/WEEX-284
> Project: Weex
>  Issue Type: Wish
>  Components: Android
>Affects Versions: 0.18
>Reporter: Curry_Chen
>Assignee: YorkShen
>Priority: Major
>   Original Estimate: 5h
>  Remaining Estimate: 5h
>
> supporting of gif pictures in Andriod platform



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-199) Add Global Switch Control Wson on or off

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-199.

Resolution: Fixed

> Add Global Switch Control Wson on or off
> 
>
> Key: WEEX-199
> URL: https://issues.apache.org/jira/browse/WEEX-199
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Trivial
>
> Add Global Switch Control Wson on or off
>  
> public static void updateGlobalConfig(String config){
>  if(TextUtils.isEmpty(config)){
>  config = "none";
>  }
>  if(!TextUtils.equals(config, globalConfig)){
>  globalConfig = config;
>  WXEnvironment.getCustomOptions().put(GLOBAL_CONFIG_KEY, globalConfig);
>  Runnable runnable = new Runnable() {
>  @Override
>  public void run() {
>  if(mBridgeManager != null){
>  if(mBridgeManager.isJSFrameworkInit()){
>  if(mBridgeManager.mWXBridge instanceof WXBridge) {
>  final WXBridge bridge = (WXBridge) mBridgeManager.mWXBridge;
>  bridge.updateGlobalConfig(globalConfig);
>  }
>  }
>  }
>  if(globalConfig.contains("wson_off")){
>  WXJsonUtils.USE_WSON = false;
>  }else{
>  WXJsonUtils.USE_WSON = true;
>  }
>  }
>  };
>  if(mBridgeManager != null && mBridgeManager.isJSFrameworkInit()){
>  mBridgeManager.post(runnable);
>  }else{
>  runnable.run();
>  }
>  }
> }



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-174) TemplateList Support Lifecycle and statefull component

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-174.

Resolution: Fixed

> TemplateList Support Lifecycle and statefull component
> --
>
> Key: WEEX-174
> URL: https://issues.apache.org/jira/browse/WEEX-174
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> TemplateList Support Lifecycle and statefull component



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-206) fix x86 so cannot run

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-206.

Resolution: Fixed

> fix x86 so cannot run
> -
>
> Key: WEEX-206
> URL: https://issues.apache.org/jira/browse/WEEX-206
> Project: Weex
>  Issue Type: Bug
>Reporter: toretto
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-205) Weex Android Weekly Bug Fix

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-205.

Resolution: Fixed

> Weex Android Weekly Bug Fix
> ---
>
> Key: WEEX-205
> URL: https://issues.apache.org/jira/browse/WEEX-205
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> Weex Weekly Bug Fix
> 1、when shouldStopProgation not set, advanced event should be fired as old 
> behavior
> 2、list support disable prefetch att, to control prefrech



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-198) FastJSON Parse Will Convert double to BigDecimal. which is not right

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-198.

Resolution: Fixed

> FastJSON Parse Will Convert double to BigDecimal.  which is not right
> -
>
> Key: WEEX-198
> URL: https://issues.apache.org/jira/browse/WEEX-198
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> FastJSON Parse Will Convert double to BigDecimal, wson will do check when 
> number is in double, use double instead of bigdecimal. keep javascript get 
> number type



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (WEEX-255) importing `sass` file into `js` does not register styles

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-255:
--

Assignee: erha19  (was: Adam Feng)

> importing `sass` file into `js` does not register styles
> 
>
> Key: WEEX-255
> URL: https://issues.apache.org/jira/browse/WEEX-255
> Project: Weex
>  Issue Type: Bug
> Environment: Weex: v1.2.9
>  - weexpack : v1.1.6
>  - weex-builder : v0.3.14
>  - weex-previewer : v1.4.6
> Env: web
>Reporter: Tuqire hussain
>Assignee: erha19
>Priority: Major
>
> h3. *Overview*
> In our app, we are currently using `tachyons` for our CSS 
> ([http://tachyons.io/).] I was hoping to import tachyons directly into 
> `entry.js` so they could be used within all components, but this isn't 
> working. Even though the app compiles and runs when I run `yarn dev`, the css 
> has not been registered. Code is below:
> {code:javascript}
> import '../node_modules/tachyons/css/tachyons.min.css'
> import store from './store'
> import '@/helpers/atom-components'
> import router from './router'
> import App from './index'
> new Vue(Vue.util.extend({ el: '#root', store, router }, App))
> router.push('/')
> /* global Vue */
> /* eslint-disable no-new */
> // new Vue(Vue.util.extend({ el: '#root', router }, App)){code}
>  
> Can someone help with this please?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (WEEX-254) Have to manually copy files from src into .temp

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-254:
--

Assignee: erha19  (was: Adam Feng)

> Have to manually copy files from src into .temp
> ---
>
> Key: WEEX-254
> URL: https://issues.apache.org/jira/browse/WEEX-254
> Project: Weex
>  Issue Type: Bug
> Environment: Weex Version: v1.2.9
> - weexpack : v1.1.6
> - weex-builder : v0.3.14
> - weex-previewer : v1.4.6
> Env: web
>Reporter: Tuqire hussain
>Assignee: erha19
>Priority: Major
>
> *Overview*
> I initialised a new project with `weex create`. When running `yarn dev`, I am 
> finding that weex does not always copy all the files from `src` into `.temp` 
> folder, meaning I have to manually do this myself. Is this expected behaviour?
> h3. *Steps to Reproduce*
> 1. Init a new project (`weex create new-app`)
> 2. Run `yarn dev` in terminal, and open web view of app
> 3. Add new files to `src` and reference them in `src/entry.js`
> 4. app throws error as files were not copied over and therefore are not found



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-312) globalEvent使用不了

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-312.
--
Resolution: Fixed

Please use English, thanks.

> globalEvent使用不了
> ---
>
> Key: WEEX-312
> URL: https://issues.apache.org/jira/browse/WEEX-312
> Project: Weex
>  Issue Type: Bug
>  Components: Android
>Affects Versions: 0.18
>Reporter: fudongrong
>Assignee: Adam Feng
>Priority: Major
> Attachments: 1524735866(1).jpg, 1524735903(1).jpg
>
>
> 我按照官方的globalEvent的使用方法,在安卓端进行支持,但是一直进不去addEventListener方法,导致mGlobalEvents里是空的,所以callbacks
>  = null,导致js中并没有收到回调。



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-63) Android refactor lines

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-63.
-
Resolution: Fixed

> 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
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-196) fix ios unregisterServiceScript method with service name

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-196.
--
Resolution: Fixed

> fix ios unregisterServiceScript method with service name
> 
>
> Key: WEEX-196
> URL: https://issues.apache.org/jira/browse/WEEX-196
> Project: Weex
>  Issue Type: Bug
>  Components: iOS
>Reporter: laibin
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-194) Scroller Show Refresh Header When Long Touch on Click event cell

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-194.

Resolution: Fixed

> Scroller Show Refresh Header When Long Touch on Click event cell
> 
>
> Key: WEEX-194
> URL: https://issues.apache.org/jira/browse/WEEX-194
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> http://dotwe.org/vue/2310b3f85589a0453054fba62f092551



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-197) WXScroller Add Child NullPointerException

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-197.

Resolution: Fixed

> WXScroller Add Child NullPointerException
> -
>
> Key: WEEX-197
> URL: https://issues.apache.org/jira/browse/WEEX-197
> Project: Weex
>  Issue Type: Bug
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Major
>
> WXScroller Add Child NullPointerException。 ErrorStack  Trace:
> Process Name: 'com.wudaokou.hippo' 
> Thread Name: 'WeeXDomThread' 
> Back traces starts.
> java.lang.NullPointerException: Attempt to invoke virtual method 'int 
> com.taobao.weex.ui.component.WXComponent.getLayoutTopOffsetForSibling()' on a 
> null object reference
>  at com.taobao.weex.ui.component.WXScroller.addChild(WXScroller.java:293)
>  at com.taobao.weex.ui.component.WXVContainer.addChild(WXVContainer.java:268)
>  at 
> com.taobao.weex.dom.action.AbstractAddElementAction.generateComponentTree(AbstractAddElementAction.java:67)
>  at 
> com.taobao.weex.dom.action.AbstractAddElementAction.generateComponentTree(AbstractAddElementAction.java:67)
>  at 
> com.taobao.weex.dom.action.AddElementAction.createComponent(AddElementAction.java:63)
>  at 
> com.taobao.weex.dom.action.AbstractAddElementAction.addDomInternal(AbstractAddElementAction.java:119)
>  at 
> com.taobao.weex.dom.action.AddElementAction.executeDom(AddElementAction.java:99)
>  at com.taobao.weex.dom.WXDomManager.executeAction(WXDomManager.java:184)
>  at com.taobao.weex.dom.WXDomHandler.handleMessage(WXDomHandler.java:76)
>  at 
> com.taobao.weex.common.WXThread$SafeCallback.handleMessage(WXThread.java:73)
>  at android.os.Handler.dispatchMessage(Handler.java:98)
>  at android.os.Looper.loop(Looper.java:158)
>  at android.os.HandlerThread.run(HandlerThread.java:61)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-191) Cell Weex Site Document Update

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-191.

Resolution: Fixed

> Cell Weex Site Document Update
> --
>
> Key: WEEX-191
> URL: https://issues.apache.org/jira/browse/WEEX-191
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Minor
>
> Cell Weex Site Document Update



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-192) Weex Document List

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-192.

Resolution: Fixed

> Weex Document List
> --
>
> Key: WEEX-192
> URL: https://issues.apache.org/jira/browse/WEEX-192
> Project: Weex
>  Issue Type: Improvement
>Reporter: codefurture
>Assignee: Adam Feng
>Priority: Minor
>
> Weex Document List



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-269) add T3D api support

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-269.

Resolution: Fixed

> add T3D api support
> ---
>
> Key: WEEX-269
> URL: https://issues.apache.org/jira/browse/WEEX-269
> Project: Weex
>  Issue Type: New Feature
>Reporter: toretto
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-275) Android 打包 apk vue数据绑定

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-275.
--
Resolution: Fixed

Please use Engilish, thanks.

> Android 打包 apk  vue数据绑定
> ---
>
> Key: WEEX-275
> URL: https://issues.apache.org/jira/browse/WEEX-275
> Project: Weex
>  Issue Type: Bug
> Environment: win10 开发
>Reporter: purplebuterfly
>Assignee: Adam Feng
>Priority: Major
>  Labels: Android, apk, vue
> Attachments: newap1p.apk
>
>
> 本人刚学 按照教程 weex creat 生成项目 修改helloword。vue文件
>  
>  
>  

[jira] [Resolved] (WEEX-99) The setViewport method in WXMetaModule is ASYN right now which makes weexInstance.viewportWidth setted after view created.

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-99.
---
Resolution: Fixed

> The setViewport method in WXMetaModule is ASYN right now which makes 
> weexInstance.viewportWidth setted after view created.
> --
>
> Key: WEEX-99
> URL: https://issues.apache.org/jira/browse/WEEX-99
> Project: Weex
>  Issue Type: Bug
>  Components: iOS
>Reporter: myeveryheart
>Assignee: Adam Feng
>Priority: Major
> Attachments: 粘贴图片.png, 粘贴图片1.png, 粘贴图片2.png, 粘贴图片3.png
>
>
> The meta module can be used to declare meta information for a single page, 
> such as the viewport of the container.
> It provides a method 'setViewport' to change the viewport of the page.
> But the method is ASYN right now which makes weexInstance.viewportWidth 
> setted after view created.
> The bug is in iOS and Android.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (WEEX-150) Implement AppShell for iOS

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-150:
--

Assignee: xingZhang  (was: Adam Feng)

> Implement AppShell for iOS
> --
>
> Key: WEEX-150
> URL: https://issues.apache.org/jira/browse/WEEX-150
> Project: Weex
>  Issue Type: Sub-task
>  Components: iOS
>Reporter: Jonathan Dong
>Assignee: xingZhang
>Priority: Major
>
> Implement AppShell basic features for iOS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-145) Crash in WXScrollerComponent scrollViewDidScroll,Collection was mutated while being enumerated

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-145.

Resolution: Fixed

> Crash in WXScrollerComponent scrollViewDidScroll,Collection was mutated while 
> being enumerated
> --
>
> Key: WEEX-145
> URL: https://issues.apache.org/jira/browse/WEEX-145
> Project: Weex
>  Issue Type: Bug
>  Components: iOS
> Environment: OS Version:  iPhone OS 10.3.3
>Reporter: lihui
>Assignee: Adam Feng
>Priority: Major
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> we use scroll component and parallax in our page. When we pull to refresh, 
> sometime we got a crash. The stack like this :
> Exception Type:  SIGABRT
> Exception Codes: #0 at 0x1828d5014
> Triggered by Thread:  0
> Application Specific Information:
> *** Terminating app due to uncaught exception 'NSGenericException', reason: 
> '*** Collection  was mutated while being 
> enumerated.'
> Last Exception Backtrace:
> 0   CoreFoundation  0x0001838dafe0 __exceptionPreprocess 
> :124 (in CoreFoundation)
> 1   libobjc.A.dylib 0x00018233c538 _objc_exception_throw 
> :56 (in libobjc.A.dylib)
> 2   CoreFoundation  0x0001838daa30 
> __NSFastEnumerationMutationHandler :128 (in CoreFoundation)
> 3   Foundation  0x0001842cd3cc -[NSConcreteHashTable 
> countByEnumeratingWithState:objects:count:] :72 (in Foundation)
> 4   Youku4iPhoneWithoutExtension0x000101936e88 -[WXScrollerComponent 
> scrollViewDidScroll:] WXScrollerComponent.m:551 (in 
> Youku4iPhoneWithoutExtension)
> 5   Youku4iPhoneWithoutExtension0x0001019a99d0 -[WXListComponent 
> scrollViewDidScroll:] WXListComponent.m:630 (in Youku4iPhoneWithoutExtension)
> 6   UIKit   0x000189d1e46c 
> -[UIScrollView(UIScrollViewInternal) _notifyDidScroll] :76 (in UIKit)
> 7   UIKit   0x000189a2a84c -[UIScrollView 
> setContentOffset:] :436 (in UIKit)
> 8   Youku4iPhoneWithoutExtension0x00010174ba90 
> -[UIScrollView(UTViewExposure) utexposure_setContentOffset:] :40 (in 
> Youku4iPhoneWithoutExtension)
> 9   UIKit   0x000189ae11dc -[UITableView 
> setContentOffset:] :272 (in UIKit)
> 10  Youku4iPhoneWithoutExtension0x0001019a5b2c -[WXTableView 
> setContentOffset:] WXListComponent.m:63 (in Youku4iPhoneWithoutExtension)
> 11  UIKit   0x000189bbbaa0 
> -[UIScrollViewScrollAnimation setProgress:] :284 (in UIKit)
> 12  UIKit   0x000189bbb790 -[UIAnimator(Static) 
> _advanceAnimationsOfType:withTimestamp:] :280 (in UIKit)
> 13  QuartzCore  0x000186aed5dc 
> CA::Display::DisplayLinkItem::dispatch(unsigned long long) :44 (in QuartzCore)
> 14  QuartzCore  0x000186aed48c 
> CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long 
> long, unsigned long long) :436 (in QuartzCore)
> 15  IOKit   0x000183b47b9c 0x000183b42000 + 
> 23452
> 16  CoreFoundation  0x000183871960 __CFMachPortPerform 
> :180 (in CoreFoundation)
> 17  CoreFoundation  0x000183889ae4 
> __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ :56 (in 
> CoreFoundation)
> 18  CoreFoundation  0x000183889284 __CFRunLoopDoSource1 
> :436 (in CoreFoundation)
> 19  CoreFoundation  0x000183886d98 __CFRunLoopRun :1752 
> (in CoreFoundation)
> 20  CoreFoundation  0x0001837b6da4 _CFRunLoopRunSpecific 
> :424 (in CoreFoundation)
> 21  GraphicsServices0x000185221074 _GSEventRunModal :100 
> (in GraphicsServices)
> 22  UIKit   0x000189a71c9c _UIApplicationMain 
> :208 (in UIKit)
> 23  Youku4iPhoneWithoutExtension0x0001000f948c main main.m:24 (in 
> Youku4iPhoneWithoutExtension)
> 24  libdyld.dylib   0x0001827c559c _start :4 (in 
> libdyld.dylib)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-215) recycle-list scroll orientation support

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-215.

Resolution: Fixed

> recycle-list scroll orientation support
> ---
>
> Key: WEEX-215
> URL: https://issues.apache.org/jira/browse/WEEX-215
> Project: Weex
>  Issue Type: Improvement
>Reporter: ZhongZhendong
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-213) expose handler for WXStorageModule in iOS

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-213.
--
Resolution: Fixed

> expose handler for WXStorageModule in iOS
> -
>
> Key: WEEX-213
> URL: https://issues.apache.org/jira/browse/WEEX-213
> Project: Weex
>  Issue Type: Improvement
>Reporter: Hao Junhua
>Assignee: Adam Feng
>Priority: Major
>
> Android has done this feature



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-217) WXTransform should not crash while parsing 'translate(0)' on iOS

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-217.

Resolution: Fixed

> WXTransform should not crash while parsing 'translate(0)' on iOS
> 
>
> Key: WEEX-217
> URL: https://issues.apache.org/jira/browse/WEEX-217
> Project: Weex
>  Issue Type: Bug
>  Components: iOS
>Reporter: Gabriel Li
>Assignee: Adam Feng
>Priority: Major
>  Labels: crash, css, translate
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> According to the latest published W3C specification about [CSS 
> Transforms|https://www.w3.org/TR/css-transforms-1/)]:
> {code:java}
> translate() = translate(  [,  ]? )
> specifies a 2D translation by the vector [tx, ty], where tx is the first 
> translation-value parameter and ty is the optional second translation-value 
> parameter. If  is not provided, ty has zero as a value.
> {code}
> , _translate(tx)_ is equal to _translate(tx, 0)_. In the previous _version of 
> Weex_, we removed the array length check in method [WXTransform 
> parseTranslate:]
> {code:java}
> - (void)parseTranslate:(NSArray *)value
> {
>     [self parseTranslatex:@[value[0]]];
>     [self parseTranslatey:@[value[1]]];
> }{code}
> so if the parser encounters a '_translate(0)_', the array contains only one 
> single value inside, parseTranslate will fetch the element at index 1 from 
> the array, which causes a typical _out-of-bounds_ exception, and lead to an 
> app crash eventually.
> As we known in many js packing procedures, '_translate(x, 0)_' will be 
> compressed/minified to the form 'translate\(x\)', Weex should avoid such 
> inconsistent implementations and conforms the W3C specifications.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-214) weex debug error,AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "npm install"

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-214.

Resolution: Fixed

> weex debug error,AssertionError [ERR_ASSERTION]: Chromium revision is not 
> downloaded. Run "npm install"
> ---
>
> Key: WEEX-214
> URL: https://issues.apache.org/jira/browse/WEEX-214
> Project: Weex
>  Issue Type: Bug
>Reporter: linshao...@meizu.com
>Assignee: Adam Feng
>Priority: Major
> Attachments: a.png, c.png, d.png
>
>
> {color:#FF}1.执行weex debug 的时候,提示{color}
> This command need to install weex-debugger. Installing...
> ERROR: Failed to download Chromium r515411! Set 
> "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download.
> Error: Download failed: server returned code 302. URL: 
> https://npm.taobao.org/mirrors/chromium-browser-snapshots/Linux_x64/515411/chrome-linux.zip
>  at ClientRequest.https.get.response 
> (/home/linshaoyou/.xtoolkit/node_modules/weex-debugger/node_modules/puppeteer/utils/ChromiumDownloader.js:198:21)
>  at Object.onceWrapper (events.js:315:30)
>  at emitOne (events.js:116:13)
>  at ClientRequest.emit (events.js:211:7)
>  at HTTPParser.parserOnIncomingClient (_http_client.js:551:21)
>  at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23)
>  at TLSSocket.socketOnData (_http_client.js:440:20)
>  at emitOne (events.js:116:13)
>  at TLSSocket.emit (events.js:211:7)
>  at addChunk (_stream_readable.js:263:12)
> npm ERR! code ELIFECYCLE
> npm ERR! errno 1
> npm ERR! puppeteer@0.13.0 install: `node install.js`
> npm ERR! Exit status 1
> npm ERR! 
> npm ERR! Failed at the puppeteer@0.13.0 install script.
> npm ERR! This is probably not a problem with npm. There is likely additional 
> logging output above.
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/linshaoyou/.npm/_logs/2018-02-10T09_29_52_739Z-debug.log
> 17:29:53 : Error: fatal error!
>  
> {color:#FF}2.set PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1后重新执行weex 
> debug,报下面的错误{color}
> AssertionError [ERR_ASSERTION]: Chromium revision is not downloaded. Run "npm 
> install"
>  
> {color:#FF}3.自动打开的浏览器,看不到二维码如附件所示{color}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (WEEX-240) sandbox feature and size of so

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng resolved WEEX-240.

Resolution: Fixed

> sandbox feature and size of so
> --
>
> Key: WEEX-240
> URL: https://issues.apache.org/jira/browse/WEEX-240
> Project: Weex
>  Issue Type: New Feature
>Reporter: toretto
>Assignee: Adam Feng
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (WEEX-285) android集成到现有app,abifilters里有armeabi-v7a报错

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng closed WEEX-285.
--
Resolution: Fixed

Please use Engilish, thanks.

> android集成到现有app,abifilters里有armeabi-v7a报错
> -
>
> Key: WEEX-285
> URL: https://issues.apache.org/jira/browse/WEEX-285
> Project: Weex
>  Issue Type: Bug
>  Components: Android
>Affects Versions: 0.18
>Reporter: fudongrong
>Assignee: Adam Feng
>Priority: Major
> Attachments: FFPP8IBNM){`5...@3a50pt.png, GER2BB05Q12~@]t7bn...@h.png
>
>
> 当app/build.gradle中包含armeabi-v7a时,具体配置如下:
> ndk {
> abiFilters "armeabi-v7a","x86", "armeabi", "mips"
> }
> 将会报错,报错内容详见附件,大意为weex初始化失败。
> 去掉armeabi-v7a就不会报错,但是不知道去掉后会不会对现有功能有影响,我应该怎么办呢?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (WEEX-331) 在手机oppo R11中weex image组件无法渲染高度超过10000px的图片

2018-05-14 Thread Adam Feng (JIRA)

 [ 
https://issues.apache.org/jira/browse/WEEX-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Feng reassigned WEEX-331:
--

Assignee: codefurture  (was: Adam Feng)

> 在手机oppo R11中weex image组件无法渲染高度超过1px的图片
> --
>
> Key: WEEX-331
> URL: https://issues.apache.org/jira/browse/WEEX-331
> Project: Weex
>  Issue Type: Bug
>  Components: Android
>Reporter: 廖柏林
>Assignee: codefurture
>Priority: Blocker
> Attachments: 图片无法渲染.jpg
>
>
> 使用image组件加载高度超过1px的图片时,图片加载并获得宽高之后并没有显示出来,出现满屏的空白。
> 手机: oppo r11
> 系统: 安卓
> demo: http://dotwe.org/vue/65f567cbb0ab11cb999c23f073fcbe5c
> 经测试,weex playground app 也有此问题,期待回复!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


  1   2   3   >