Re: [DISCUSS] Roadmap proposal for community building

[NetPuter]

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 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,
> documentation, tools, plugins, etc. which are the largest short boards for
> now.
>
> 1. Workflow:
>
> • Discussion, all the things below should be discussed on dev@ or
> Jira issues, discuss BEFORE commit.
>
> • work in-progress
> • feature to be implemented
> • any ideas, either for feature or for community
>
> • Contribution
>
> • make a clearer contribution guide, including how to create
> issues(with a good format), ask or answer questions, join discussions,
> contribute to documentation, contribute to code, etc.
> • add easy-to-solve tags or labels to some issues to attract
> contribution.
>
> • Development
>
> • change branch flow which was mentioned in [1] .
> • define a good commit format, as the commits now are really messy
> • one commit for one issue
>
>
> 2. Documentation
>
> • a complete 0-1 tutorial is badly needed
> • modify documentation style and structure which is in progress [2]
> • encourage EVERYONE to rewrite the documents which are difficult to
> understand and find some native speakers to have a review.
> • add a document evaluation mechanism to indicate the quality of
> documentation.
> • add a who-is-using-weex page in a obvious place.
>
> 3. Plugins
>
> • develop more plugins with interaction ability to community， such as
> rich-text, gesture, animation, etc.
> • create tools to link plugins more easily.
>
> 4. Tools
>
> • improve weex toolkit and devtool's developer experience, get all the
> commands in order, make sure every command has clear flow and error
> handling.
>
>
> If the community has enough "content", the next stage should be "PROMOTE
> OURSELVES", we should try to make connection with developers from Europe
> and America, we can promote our community with the help of Vuejs community.
>
> 1. Writing Blogs, the first blog can be a complete tutorial about Weex,
> followed by some blogs about technical details, one blog each week will be
> excellent at the beginning.
> 2. Use Western Social Media like Twitter, Facebook, etc.
> 3. Other channels like newsletter, meetup, AMA, etc.
>
> If there are no objections, I will create issue for every action and try
> to find appropriate guy to accomplish it. The community building needs
> EVERYONE's help!
> [1] https://issues.apache.org/jira/browse/WEEX-75
> [2] https://issues.apache.org/jira/browse/WEEX-79
>
> Thanks.
> Adam Feng
>



-- 
Best Regards,
NetPuter Lin *»* 

[DISCUSS] Roadmap proposal for community building

[Adam Feng]

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, documentation, 
tools, plugins, etc. which are the largest short boards for now.

1. Workflow:

• Discussion, all the things below should be discussed on dev@ or Jira 
issues, discuss BEFORE commit.

• work in-progress
• feature to be implemented
• any ideas, either for feature or for community

• Contribution

• make a clearer contribution guide, including how to create 
issues(with a good format), ask or answer questions, join discussions, 
contribute to documentation, contribute to code, etc.
• add easy-to-solve tags or labels to some issues to attract 
contribution.

• Development

• change branch flow which was mentioned in [1] .
• define a good commit format, as the commits now are really messy
• one commit for one issue


2. Documentation

• a complete 0-1 tutorial is badly needed
• modify documentation style and structure which is in progress [2]
• encourage EVERYONE to rewrite the documents which are difficult to 
understand and find some native speakers to have a review.
• add a document evaluation mechanism to indicate the quality of 
documentation.
• add a who-is-using-weex page in a obvious place.

3. Plugins

• develop more plugins with interaction ability to community， such as 
rich-text, gesture, animation, etc.
• create tools to link plugins more easily.

4. Tools

• improve weex toolkit and devtool's developer experience, get all the 
commands in order, make sure every command has clear flow and error handling.


If the community has enough "content", the next stage should be "PROMOTE 
OURSELVES", we should try to make connection with developers from Europe and 
America, we can promote our community with the help of Vuejs community.

1. Writing Blogs, the first blog can be a complete tutorial about Weex, 
followed by some blogs about technical details, one blog each week will be 
excellent at the beginning.
2. Use Western Social Media like Twitter, Facebook, etc.
3. Other channels like newsletter, meetup, AMA, etc.

If there are no objections, I will create issue for every action and try to 
find appropriate guy to accomplish it. The community building needs EVERYONE's 
help!
[1] https://issues.apache.org/jira/browse/WEEX-75
[2] https://issues.apache.org/jira/browse/WEEX-79

Thanks.
Adam Feng

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, after all I am trying to achieve an 
elegant implementation of CSS, excluding dummy, heavy, duplicate part of CSS. 
But It makes sense that flex-basis should support and only support percent 
value. For baseline, I think if iOS Framework is able to pass ascent, descent, 
half-leading, top and bottom to layout engine, layout engine itself has no 
problem to manipulate these values.

> 在 2017年10月12日，17:16，xing zhang  写道：
> 
> 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. 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 name of the layout system.

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

[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

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

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

[Adam Feng]

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 
everyone understand the things discussed in the mailing list.

Second,  please show me a demo in http://dotwe.org/vue/ for the issue and tell 
the reproducible steps in detail.

Thanks.
Adam Feng

On 12 Oct 2017, 5:37 PM +0800, wcxwave , wrote:
> Hi Weex Devs,
> Weex用了有一段时间了，目前遇到一个比较怪异的问题。
>
> weex的列表下来刷新，比如:数组的内容在前面插入3条记录a,b,c.
> 新增数据不会在列表前头显示出来。而是在后面显示出来。
> 我的list的cell如下:
>   append="node" :ref="'cell'+index"
>  {{item.number_comment}}  另外如果把page_data.listData的数组切换到新的数组,发现页面上图片不会变换，但文字部分变换了。是不是weex里面的image有cache?
> 问一下，有没有一种机制，可以通知weex强制刷新所有图片？ 
> 我们先前是先对page_data.listData赋值一个空数组，然后开启一个定时器，再赋值新的数组。但这样页面会有一个空白的闪屏。
> 这个问题一直都存在，升级到最新的weex-vue-render的版本也还是存在。  "dependencies": {
>     "caniuse-api": "^1.6.1",
>     "file-loader": "^0.11.1",
>     "qs": "^6.4.0",
>     "url-loader": "^0.5.8",
>     "vue": "^2.1.8",
>     "vue-router": "^2.1.1",
>     "vuex": "^2.1.1",
>     "vuex-router-sync": "^4.0.1",
>     "weex-vue-render": "^0.12.20"
>   },

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

[wcxwave]

Hi Weex Devs,
Weex用了有一段时间了，目前遇到一个比较怪异的问题。

weex的列表下来刷新，比如:数组的内容在前面插入3条记录a,b,c.
新增数据不会在列表前头显示出来。而是在后面显示出来。
我的list的cell如下:


   
   {{item.number_comment}}

另外如果把page_data.listData的数组切换到新的数组,发现页面上图片不会变换，但文字部分变换了。是不是weex里面的image有cache?
问一下，有没有一种机制，可以通知weex强制刷新所有图片？ 
我们先前是先对page_data.listData赋值一个空数组，然后开启一个定时器，再赋值新的数组。但这样页面会有一个空白的闪屏。
这个问题一直都存在，升级到最新的weex-vue-render的版本也还是存在。  "dependencies": {
    "caniuse-api": "^1.6.1",
    "file-loader": "^0.11.1",
    "qs": "^6.4.0",
    "url-loader": "^0.5.8",
    "vue": "^2.1.8",
    "vue-router": "^2.1.1",
    "vuex": "^2.1.1",
    "vuex-router-sync": "^4.0.1",
    "weex-vue-render": "^0.12.20"
  },

Re: Replace Facebook/Yoga with a new implementation.

[xing zhang]

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. 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 name of the layout system.

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 name of the layout system.

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

[Hanks Zhang (JIRA)]

 [ 
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
> 
>
> 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] [Resolved] (WEEX-62) image Component can save image to photo Album or sd card

[xingZhang (JIRA)]

 [ 
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
> 
>
> Key: WEEX-62
> URL: https://issues.apache.org/jira/browse/WEEX-62
> Project: Weex
>  Issue Type: New Feature
>Reporter: xingZhang
>Assignee: xingZhang
>  Labels: features
>
> image component support save image to photo Album or sd card
> design to support it with component Method.
> so the dsl  will be as follow:
>  src="http://www.fresher.ru/manager_content/images2/kadry-veka/big/2-1.jpg; 
> style="width:250px;height:250px;background-color:yellow">
> js: 
>   var image = this.$refs.image;
>   image.save(function(result) {
>console.log(result);
> });  // html5  iOS and Android provide their own component method
> the callback data result format maybe 
>   {
>     "success" : true/false,
>     "errorDesc": "errorDesc" // if the success is false, describe the reason 
> why this action failed.
>   }
> you can try a complete case:
>case:  http://dotwe.org/vue/55b9f0683f9c8bb9e12788626608da4c



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

[xingZhang (JIRA)]

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on WEEX-79:


Github user erha19 closed the pull request at:

https://github.com/apache/incubator-weex/pull/771


> 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] [Commented] (WEEX-78) The ES7 methods should be removed to improve compatibility

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on WEEX-78:


Github user Hanks10100 closed the pull request at:

https://github.com/apache/incubator-weex/pull/770


> 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] [Commented] (WEEX-78) The ES7 methods should be removed to improve compatibility

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on WEEX-78:


Github user Hanks10100 commented on the issue:

https://github.com/apache/incubator-weex/pull/770
  
Already merged. 
https://github.com/apache/incubator-weex/commit/d10be0bcf9624ca0f56fe8f60d646f71ed2f1aa0


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

[erha19 (JIRA)]

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

[erha19 (JIRA)]

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