[jira] [Resolved] (WEEX-79) Modify document website style of weex.

[ https://issues.apache.org/jira/browse/WEEX-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] erha19 resolved WEEX-79. Resolution: Fixed > Modify document website style of weex. > -- > >

[jira] [Closed] (WEEX-79) Modify document website style of weex.

[ https://issues.apache.org/jira/browse/WEEX-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] erha19 closed WEEX-79. -- > Modify document website style of weex. > -- > > Key: WEEX-79 >

[jira] [Commented] (WEEX-78) The ES7 methods should be removed to improve compatibility

[ https://issues.apache.org/jira/browse/WEEX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201544#comment-16201544 ] ASF GitHub Bot commented on WEEX-78: Github user Hanks10100 commented on the issue:

[jira] [Commented] (WEEX-78) The ES7 methods should be removed to improve compatibility

[ https://issues.apache.org/jira/browse/WEEX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201545#comment-16201545 ] ASF GitHub Bot commented on WEEX-78: Github user Hanks10100 closed the pull request at:

[jira] [Commented] (WEEX-79) Modify document website style of weex.

[ https://issues.apache.org/jira/browse/WEEX-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201546#comment-16201546 ] ASF GitHub Bot commented on WEEX-79: Github user erha19 closed the pull request at:

[jira] [Resolved] (WEEX-78) The ES7 methods should be removed to improve compatibility

[ https://issues.apache.org/jira/browse/WEEX-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanks Zhang resolved WEEX-78. - Resolution: Resolved > The ES7 methods should be removed to improve compatibility > -

[jira] [Resolved] (WEEX-54) [proposal] Support to detect the feature compatibility of weex

[ https://issues.apache.org/jira/browse/WEEX-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanks Zhang resolved WEEX-54. - Resolution: Resolved > [proposal] Support to detect the feature compatibility of weex > -

[jira] [Resolved] (WEEX-32) weex-vue-framework add services mechanism

[ https://issues.apache.org/jira/browse/WEEX-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanks Zhang resolved WEEX-32. - Resolution: Resolved > weex-vue-framework add services mechanism > -

[jira] [Resolved] (WEEX-49) add osName to weex.config.env

[ https://issues.apache.org/jira/browse/WEEX-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xingZhang resolved WEEX-49. --- Resolution: Fixed > add osName to weex.config.env > - > > Key: WEEX-4

[jira] [Resolved] (WEEX-62) image Component can save image to photo Album or sd card

[ https://issues.apache.org/jira/browse/WEEX-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xingZhang resolved WEEX-62. --- Resolution: Fixed > image Component can save image to photo Album or sd card > --

[jira] [Resolved] (WEEX-51) The console APIs doesn't work on Android

[ https://issues.apache.org/jira/browse/WEEX-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanks Zhang resolved WEEX-51. - Resolution: Fixed > The console APIs doesn't work on Android > > >

Replace Facebook/Yoga with a new implementation.

Dear all, I’m considering replacing Facebook/Yoga to a new layout system based on Google/Flexbox due to Facebook’s additional patent issue. Besides, this new layout system will provide some new css style like order, etc. Any advise for the new layout system? PS: I need some advise about the na

Re: Replace Facebook/Yoga with a new implementation.

Should we consider about layout percent unit, flex-shrink, flex-grow, flexBasis, and baseline in align-Items ? 2017-10-12 16:54 GMT+08:00 申远 : > Dear all, > > I’m considering replacing Facebook/Yoga to a new layout system based on > Google/Flexbox due to Facebook’s additional patent issue. Beside

weex的列表能否强制刷新数据

Hi Weex Devs, Weex用了有一段时间了，目前遇到一个比较怪异的问题。 weex的列表下来刷新，比如:数组的内容在前面插入3条记录a,b,c. 新增数据不会在列表前头显示出来。而是在后面显示出来。 我的list的cell如下: {{item.number_comment}} 另外如果把page_data.listData的数组切换到新的数组,发现页面上图片不会变换，但文字部分变换了。是不是weex里面的image有cache? 问一

Re: weex的列表能否强制刷新数据

First of all,  please use English,  as diversity is important for the community. I know this is difficult, especially since most of the developers are Chinese, probably with limited English fluency  like me... But we still need to try our best to get the discussion in English,  in order to make

[jira] [Created] (WEEX-81) shadow render wrong

jackyking created WEEX-81: - Summary: shadow render wrong Key: WEEX-81 URL: https://issues.apache.org/jira/browse/WEEX-81 Project: Weex Issue Type: Bug Components: iOS Reporter:

[jira] [Commented] (WEEX-81) shadow render wrong

[ https://issues.apache.org/jira/browse/WEEX-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16201832#comment-16201832 ] Adam Feng commented on WEEX-81: --- [~acton393] please have a look at the box-shadow issue > sha

[jira] [Assigned] (WEEX-81) shadow render wrong

[ https://issues.apache.org/jira/browse/WEEX-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Feng reassigned WEEX-81: - Assignee: xingZhang (was: Adam Feng) > shadow render wrong > --- > > Key: W

Re: Replace Facebook/Yoga with a new implementation.

flex-grow is already supported by flex shorthand, and it’s possible to support flex-shrink in later version. While, flex-basis is the same as main size which is supported already except for percent value. I think support percent unit is a huge, duplicate and unnecessary work for most CSS style,

[DISCUSS] Roadmap proposal for community building

Hi, all: I think it's important to have a roadmap to change the present situation in community and diversity. I have written a proposal for the follow-on community building. Please have a review and any advice is welcome:D. The first stage should be "DO BETTER", improving the workflow, documentat

Re: [DISCUSS] Roadmap proposal for community building

I think another project from alibaba is a great example: eggjs/egg . There are many things can learn from it. Such as make github issues as stackoverflow, RFC before doing, etc.. 2017-10-13 12:17 GMT+08:00 Adam Feng : > Hi, all: > I think it's important to have a roa

Re: [DISCUSS] Roadmap proposal for community building

Cheers! According to my observation, our documents and tools are often questioned in the community. If we do improve that, developers can use weex more easily and it can also inspire the community. I'm reorganizing the structure of our documents and website. Considering that our developers are va