Re: 使用clone的WEEX SDK，android studio不会打印jsLog
Hi, This issue is fixing. See more https://issues.apache.org/jira/projects/WEEX/issues/WEEX-51 On Thu, Jul 13, 2017 at 9:54 AM, 黄炳金 <huan...@landicorp.com> wrote: > Hi Weex Team, > I use cloned weex_sdk, it can not print jsLog on Android Studio。 > > But when I use official release sdk just like weex_sdk:0.10.0 or > weex_sdk:0.11.0, Android studio print jsLog normally。 > >How can I set in cloned weex_sdk to open jsLog print on Android > Studio. > >Need Your Help!!! > >I also ask question here : https://segmentfault.com/q/ > 101010133116?_ea=2173819。 > > Thanks a lot!!! > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
[jira] [Resolved] (WEEX-55) Fix contentSize value in scroll event
[ https://issues.apache.org/jira/browse/WEEX-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-55. --- Resolution: Fixed > Fix contentSize value in scroll event > - > > Key: WEEX-55 > URL: https://issues.apache.org/jira/browse/WEEX-55 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.15 > Reporter: sospartan >Assignee: zhengshihan > > The 'contentSize' height is using a assessed value, it will be changed during > scroll by the 'recycler' mechanism. > My patch will use height from layout engine to replace it. It's stable after > layout finished. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Weex Podling Report(Draft)
Thank you John. I think Tancy is during a vacation. On Mon, Jul 10, 2017 at 5:57 AM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi John, * > > I did it... Thanks to Tracy for the draft. > > Regards, Raphael > > > Am .07.2017, 15:14 Uhr, schrieb John D. Ament <johndam...@apache.org>: > > Raphael, >> >> So can you post the report? >> >> John >> >> On 2017-07-07 01:23 (-0400), "Raphael Bircher" <rbircherapa...@gmail.com> >> wrote: >> >>> Hi John >>> >>> Am .07.2017, 05:24 Uhr, schrieb John D. Ament <johndam...@apache.org>: >>> >>> > Ping. Tancy, if you can't post it can someone with access post it >>> > instead? >>> > >>> > Raphael, let me know if you want access to make people contributors. >>> >>> I should have wiki access. >>> >>> Regards, Raphael >>> > >>> > On 2017-07-04 22:27 (-0400), "Raphael Bircher" >>> > <rbircherapa...@gmail.com> wrote: >>> >> Hi Tancy >>> >> >>> >> Do you have access to the Incubator wiki? Else you have to ask for >>> >> access >>> >> on the general@i.a.o >>> >> >>> >> @sospartan goot point. >>> >> >>> >> Regards, Raphael >>> >> >>> >> Am .07.2017, 04:20 Uhr, schrieb sospartan <sospar...@gmail.com>: >>> >> >>> >> > On Wed, Jul 5, 2017 at 10:11 AM, Tancy Ni <ron...@gmail.com> wrote: >>> >> > >>> >> >> Weex is a framework for building Mobile cross-platform high >>> >> performance >>> >> >> UI. >>> >> >> Weex has been incubating since 2016-11-30. >>> >> >> Three most important issues to address in the move towards >>> >> graduation: >>> >> >> 1. Move the whole workflow and infra into Apache (not the >>> codebase >>> >> >> only). >>> >> >> 2. Develop more contributors and committers. >>> >> >> 3. First Release while in Incubator. >>> >> >> 4. Improve the developer's activity in JIRA. >>> >> >> >>> >> >> *## How has the community developed since the last report?* >>> >> >> >>> >> >> - We voted a new committer: Jianfeng Li >>> >> >> - Our Github has growth contributors (110), forks (517), watchers >>> >> (222) >>> >> >> and >>> >> >> stars (3858) >>> >> >> - We have encouraged people to discuss more in the JIRA and dev >>> mail >>> >> >> list. >>> >> >> Up to now, 21 issues are reported on JIRA and 15 of them are >>> >> resovled. >>> >> >> - WebSite Trends Month Active , PV(295160) , UV(39778) , IP(36988), >>> >> New >>> >> >> Unique Visitor(20700) , Session(68747) >>> >> >> >>> >> >> >>> >> > Maybe append our mail list activities. Like Rapheal said, it's grow >>> a >>> >> lot >>> >> > last month. >>> >> > >>> >> > *## How has the project developed since the last report?* >>> >> >> >>> >> >> - Excluding merges, 19 authors have pushed 33 commits to master and >>> >> 240 >>> >> >> commits to all branches. >>> >> >> - This month we have successfully released the 0.12 version. >>> >> >> >>> >> >> *## How would you assess the podling's maturity?* >>> >> >> *Please feel free to add your own commentary.* >>> >> >> >>> >> > [ ] Initial setup >>> >> >> [ ] Working towards first release >>> >> >> [x] Community building >>> >> >> [ ] Nearing graduation >>> >> >> [ ] Other: >>> >> >> Date of last release: >>> >> >> 2017-06-08 >>> >> >> >>> >> >> *## When were the last committers or PPMC members elected?* >>> >> >> - Jianfeng Li, 16 June 2017 >>> >> >> >>> >> >> >>> >> >> --- >>> >> >> Tancy >>> >> >> 2017.7.5 >>> >> >> >>> >> > >>> >> > >>> >> > >>> >> >>> >> >>> >> -- >>> >> My introduction https://youtu.be/Ln4vly5sxYU >>> >> >>> >>> >>> -- >>> My introduction https://youtu.be/Ln4vly5sxYU >>> >>> > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Weex Podling Report（Draft）
On Wed, Jul 5, 2017 at 10:11 AM, Tancy Ni <ron...@gmail.com> wrote: > Weex is a framework for building Mobile cross-platform high performance UI. > Weex has been incubating since 2016-11-30. > Three most important issues to address in the move towards graduation: > 1. Move the whole workflow and infra into Apache (not the codebase only). > 2. Develop more contributors and committers. > 3. First Release while in Incubator. > 4. Improve the developer's activity in JIRA. > > *## How has the community developed since the last report?* > > - We voted a new committer: Jianfeng Li > - Our Github has growth contributors (110), forks (517), watchers (222) and > stars (3858) > - We have encouraged people to discuss more in the JIRA and dev mail list. > Up to now, 21 issues are reported on JIRA and 15 of them are resovled. > - WebSite Trends Month Active , PV(295160) , UV(39778) , IP(36988), New > Unique Visitor(20700) , Session(68747) > > Maybe append our mail list activities. Like Rapheal said, it's grow a lot last month. *## How has the project developed since the last report?* > > - Excluding merges, 19 authors have pushed 33 commits to master and 240 > commits to all branches. > - This month we have successfully released the 0.12 version. > > *## How would you assess the podling's maturity?* > *Please feel free to add your own commentary.* > [ ] Initial setup > [ ] Working towards first release > [x] Community building > [ ] Nearing graduation > [ ] Other: > Date of last release: > 2017-06-08 > > *## When were the last committers or PPMC members elected?* > - Jianfeng Li, 16 June 2017 > > > --- > Tancy > 2017.7.5 > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Refering the community page from the main Website
Maybe 'Get Involved' is better than 'Contribute'. Beside, I think we shall put a mini-version of our release notes/activities in home page too. Our website is way too focus on 'good-looking' than 'developer-friendly'. We should make some changes I think. On Mon, Jul 3, 2017 at 11:17 AM, sospartan <sospar...@gmail.com> wrote: > Hi, > I suggest put a 'Contribute' section at navigation bar right after the > 'services & tools'. > > The ASF logo and Disclaimer is at bottom of every page. But we do need > more talk about 'apache' in home page. > > On Mon, Jul 3, 2017 at 10:33 AM, Raphael Bircher <rbircherapa...@gmail.com > > wrote: > >> Hi all >> >> At the moment, we have no link at https://weex.incubator.apache.org who >> refers to the community page. So if someone want to join the community he >> has a really hard time to find the Mailing list for example >> >> Also we should include the standard apache links like Sponsor site of the >> ASF. >> >> Regards, Raphael >> >> -- >> My introduction https://youtu.be/Ln4vly5sxYU >> > > > > -- > Best Regards! > > sospartan > http://weex.apache.org/ <https://weex-project.io/> > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Refering the community page from the main Website
Hi, I suggest put a 'Contribute' section at navigation bar right after the 'services & tools'. The ASF logo and Disclaimer is at bottom of every page. But we do need more talk about 'apache' in home page. On Mon, Jul 3, 2017 at 10:33 AM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all > > At the moment, we have no link at https://weex.incubator.apache.org who > refers to the community page. So if someone want to join the community he > has a really hard time to find the Mailing list for example > > Also we should include the standard apache links like Sponsor site of the > ASF. > > Regards, Raphael > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Continue like this guys!!
Great! We shall mention we have hit a milestone after last report, first release is done. Glad to hear I am not alone and things is still moving forward. On Mon, Jul 3, 2017 at 10:06 AM, Tancy Ni <ron...@gmail.com> wrote: > Ok, this month I do it。 > > Raphael Bircher <rbircherapa...@gmail.com>于2017年7月3日周一 上午9:46写道： > > > Hi all > > > > I want to say, that we nearly doubled our e-mail traffic in the last > > month. We need to continue our work in open communication and decision > > making, but it is a good start. > > > > I like also, that we have people like to contribute to our community. It > > shows that the peoples are interested in the weex project. I think we > have > > a load of potential. But we have to take the chance and get this > potential > > into the project. > > > > Also we have to fill our podling report. It would be nice if someone > steps > > in (maybe not sospartan). He already does a load. > > > > Regards, Raphael > > > > -- > > My introduction https://youtu.be/Ln4vly5sxYU > > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
[jira] [Assigned] (WEEX-52) Add auto for ImageQuality
[ https://issues.apache.org/jira/browse/WEEX-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan reassigned WEEX-52: - Assignee: YorkShen (was: sospartan) Fix Version/s: 0.15 Component/s: Android > Add auto for ImageQuality > - > > Key: WEEX-52 > URL: https://issues.apache.org/jira/browse/WEEX-52 > Project: Weex > Issue Type: New Feature > Components: Android >Reporter: YorkShen >Assignee: YorkShen > Fix For: 0.15 > > > Add auto for ImageQuality, and the imageAdapter decides the meaning of auto. > The default of quality will be changed to auto -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: 答复: 使用border-radius设置圆形图片的边缘毛刺问题
Great! Feel free to discuss other problems here. I'm suggesting we use english, which is more friendly to developers/users who are not Chinese. Thank you. 2017-06-27 17:49 GMT+08:00 黄炳金 <huan...@landicorp.com>: > 问题找到了， 与我们重写ImageAdapter, 设置的RGB_565有关， Weex代码框架这一块没有问题。 > > > > 谢谢！ > > > > Best Regards! > > Bing.Huang > > > > *发件人:* 黄炳金 > *发送时间:* 2017年6月27日 15:29 > *收件人:* 'dev@weex.incubator.apache.org' > *主题:* 使用border-radius设置圆形图片的边缘毛刺问题 > > > > Hi, > > 请教下，使用border-radius设置圆形图片，边缘会有毛刺。 > > 请问如何解决： > > [image: https://segmentfault.com/img/bVPSOJ?w=231=161] > > > -- > > Best Regards! > > Bing.Huang > -- > > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
[jira] [Commented] (WEEX-34) Update csslayout to Yoga
[ https://issues.apache.org/jira/browse/WEEX-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16064312#comment-16064312 ] sospartan commented on WEEX-34: --- Latest version is 1.5.1 > Update csslayout to Yoga > > > Key: WEEX-34 > URL: https://issues.apache.org/jira/browse/WEEX-34 > Project: Weex > Issue Type: Task > Reporter: sospartan > > Weex bundle old csslayout source code, which is out of date. > The library is renamed to 'yoga'. > In android side, it's provided jcenter artifacts: > > https://bintray.com/facebook/maven/com.facebook.yoga%3Ayoga > latest version is 1.4.2 > After change to remote dependency, source code under > 'android/sdk/src/main/java/com/taobao/weex/dom/flex' could be removed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-40) Divide callNative，support DOM level API
[
https://issues.apache.org/jira/browse/WEEX-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sospartan resolved WEEX-40.
---
Resolution: Fixed
> Divide callNative，support DOM level API
> ---
>
> Key: WEEX-40
> URL: https://issues.apache.org/jira/browse/WEEX-40
> Project: Weex
> Issue Type: Improvement
> Components: Android
>Reporter: kfeagle
> Fix For: 0.14
>
>
> # DOM Operation Top-Level API
> `callNative` Segmentation，support native api as DOM level，it can improve
> performence , because it can reduce js-native communication.
> defalue `callNative` as follow：
> [
> // 0\. {String} document id ，usually app id
> '3',
> // 1\. {Array} task list
> [
> {
> // {String} module name
> module: 'dom',
> // {String} method in module，such as: createBody 、 updateAttrs 、
> removeEvent
> method: 'addElement',
> // {Array} task parameter
> args: [
> '23', // {String} element ref
> ... // other parameter
> ]
> }
> ],
> // 2\. {String} signal ， -1
> '-1'
> ]
> the design follow the standard that the first item is docId, the last item is
> signal. the middle parameter designed by function. you can refer to
> `callAddElement` to design other api
> 1. createBody
> Native provide： `callCreateBody` 。
> function parameter：
> [
> docId,
> // {Element} body
> {
> ref,
> type,
> attr,
> ...
> },
> '-1'
> ]
> 2. addElement
>Native provide： `callAddElement` 。（finished）
>function parameter：
>[
> docId,
> // {String} the element ref will be inserted
> ref,
> // {Element} the element will be inserted
> {
> ref,
> type,
> attr,
> ...
> },
> // {Number} insert index
> index,
> '-1'
> ]
> 3. removeElement
> Native provide： `callRemoveElement` 。
> function parameter：
>[
> docId,
> // {String} the ref will be delete
>ref,
> '-1'
> ]
> 4. moveElement
> Native provide： `callMoveElement` 。
> function parameter：
> [
> docId,
> // {String} the ref will be move
> targetRef,
> // {String} parent ref
> parentRef,
> // {Number} the index will move to
> index,
> '-1'
> ]
> 6. updateAttrs
> Native should provide： `callUpdateAttrs` 。
> function parameter：
> [
> docId,
> // {String} the ref will update
> ref,
> // {Object} new attribute，JSON object
> attrs,
> '-1'
> ]
> 8. updateStyle
> Native should provide： `callUpdateStyle` 。
> function parameter：
> [
> docId,
> // {String} the ref will update
> ref,
> // {Object} new style，JSON object
> attrs,
> '-1'
> ]
> 9. addEvent
> Native should provate： `callAddEvent` 。
> function parameter：
> [
> docId,
> // {String} the ref of element
> ref,
> // {String} event type， click | appear
> eventType,
> '-1'
> ]
> 10. removeEvent
> Native should provide method： `callRemoveEvent` 。
> function parameter：
> [
> docId,
> // {String} the ref of element whose event will remove
> ref,
> // {String} event type， click | appear
> eventType,
> '-1'
> ]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (WEEX-37) list support drag-drop
[ https://issues.apache.org/jira/browse/WEEX-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-37. --- Resolution: Fixed > list support drag-drop > -- > > Key: WEEX-37 > URL: https://issues.apache.org/jira/browse/WEEX-37 > Project: Weex > Issue Type: New Feature > Components: Android > Environment: android/iOS >Reporter: chuyi > Labels: features > Fix For: 0.14 > > Original Estimate: 168h > Remaining Estimate: 168h > > implement drag-drop feature for list > feature: > 1. support both pan and longPress gesture to trigger drag-drop; > 2. support liner/grid layout; > 3. support dragStart/dragEnd event; > 4. support excluded some cells when dragging; > extend attrs: > list: > - draggable: whether draggable or not; > - drag-trigger-type: which gesture type will trigger drag-drop; > cell: > - drag-excluded: whether we should ignore current cell for dragging; > any component: > - drag-anchor: the anchor that will trigger drag-drop -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-48) textarea cursor disappears and can't scroll
[ https://issues.apache.org/jira/browse/WEEX-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-48. --- Resolution: Fixed > textarea cursor disappears and can't scroll > --- > > Key: WEEX-48 > URL: https://issues.apache.org/jira/browse/WEEX-48 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.12 >Reporter: moxun >Assignee: moxun > Fix For: 0.14 > > > textarea's cursor will disappear when the content height is bigger than > component height. > This is caused call `setMovementMethod(null)` on `WXEditText#onSizeChanged`, > it will disable movement and make cursor disappear. > I added the flag `mAllowDisableMovement ` to control whether content can be > movement, default is true and its value can be set by > `WXEditText#setAllowDisableMovement ` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-47) AddRule fail when called 'created' method
[ https://issues.apache.org/jira/browse/WEEX-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-47. --- Resolution: Fixed Fix Version/s: 0.14 > AddRule fail when called 'created' method > - > > Key: WEEX-47 > URL: https://issues.apache.org/jira/browse/WEEX-47 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.14 > Reporter: sospartan >Assignee: zhengshihan > Fix For: 0.14 > > > Demo: http://dotwe.org/vue/d96b6f89aadd1d628111c16a30e80482 > This is caused call 'addRule' before DOM context created in native. The DOM > context is used to created when 'createBody' invoked. > So I have to allow other operations to creating DOM context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-47) AddRule fail when called 'created' method
[ https://issues.apache.org/jira/browse/WEEX-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan reassigned WEEX-47: - Assignee: sospartan (was: zhengshihan) > AddRule fail when called 'created' method > - > > Key: WEEX-47 > URL: https://issues.apache.org/jira/browse/WEEX-47 > Project: Weex > Issue Type: Bug > Components: Android >Affects Versions: 0.14 > Reporter: sospartan >Assignee: sospartan > Fix For: 0.14 > > > Demo: http://dotwe.org/vue/d96b6f89aadd1d628111c16a30e80482 > This is caused call 'addRule' before DOM context created in native. The DOM > context is used to created when 'createBody' invoked. > So I have to allow other operations to creating DOM context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (WEEX-47) AddRule fail when called 'created' method
sospartan created WEEX-47: - Summary: AddRule fail when called 'created' method Key: WEEX-47 URL: https://issues.apache.org/jira/browse/WEEX-47 Project: Weex Issue Type: Bug Components: Android Affects Versions: 0.14 Reporter: sospartan Assignee: zhengshihan Demo: http://dotwe.org/vue/d96b6f89aadd1d628111c16a30e80482 This is caused call 'addRule' before DOM context created in native. The DOM context is used to created when 'createBody' invoked. So I have to allow other operations to creating DOM context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (WEEX-38) Support rotateX and rotateY
[ https://issues.apache.org/jira/browse/WEEX-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-38. --- Resolution: Fixed > Support rotateX and rotateY > --- > > Key: WEEX-38 > URL: https://issues.apache.org/jira/browse/WEEX-38 > Project: Weex > Issue Type: New Feature > Components: Android >Reporter: YorkShen > Fix For: 0.14 > > > Support rotateX and rotateY as specified by > https://developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotateX > and > https://developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotateY -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (WEEX-38) Support rotateX and rotateY
[ https://issues.apache.org/jira/browse/WEEX-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan updated WEEX-38: -- Fix Version/s: 0.14 Component/s: Android > Support rotateX and rotateY > --- > > Key: WEEX-38 > URL: https://issues.apache.org/jira/browse/WEEX-38 > Project: Weex > Issue Type: New Feature > Components: Android >Reporter: YorkShen > Fix For: 0.14 > > > Support rotateX and rotateY as specified by > https://developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotateX > and > https://developer.mozilla.org/en-US/docs/Web/CSS/transform-function/rotateY -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (WEEX-37) list support drag-drop
[ https://issues.apache.org/jira/browse/WEEX-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan updated WEEX-37: -- Fix Version/s: 0.14 Component/s: Android > list support drag-drop > -- > > Key: WEEX-37 > URL: https://issues.apache.org/jira/browse/WEEX-37 > Project: Weex > Issue Type: New Feature > Components: Android > Environment: android/iOS >Reporter: chuyi > Labels: features > Fix For: 0.14 > > Original Estimate: 168h > Remaining Estimate: 168h > > implement drag-drop feature for list > feature: > 1. support both pan and longPress gesture to trigger drag-drop; > 2. support liner/grid layout; > 3. support dragStart/dragEnd event; > 4. support excluded some cells when dragging; > extend attrs: > list: > - draggable: whether draggable or not; > - drag-trigger-type: which gesture type will trigger drag-drop; > cell: > - drag-excluded: whether we should ignore current cell for dragging; > any component: > - drag-anchor: the anchor that will trigger drag-drop -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo
[ https://issues.apache.org/jira/browse/WEEX-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan reassigned WEEX-44: - Assignee: sospartan Component/s: Project > 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: sospartan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Which version shall we release next?
Hi all, As you know, v0.12 is released. I was intended to release v0.13. But v0.13 was finished developing about a month ago. And v0.14 is almost done in few days. So I am confused. Should I just start release v0.14 and skip v0.13? Mentors, how do people deal with circumstances like this? -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io>
[jira] [Assigned] (WEEX-43) Add release job to travis CI
[ https://issues.apache.org/jira/browse/WEEX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan reassigned WEEX-43: - Assignee: sospartan Component/s: Project > 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: sospartan > > 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] [Updated] (WEEX-41) remove some redundant reference of DomObject in input component
[ https://issues.apache.org/jira/browse/WEEX-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan updated WEEX-41: -- Fix Version/s: (was: 0.14) Component/s: Android > remove some redundant reference of DomObject in input component > --- > > Key: WEEX-41 > URL: https://issues.apache.org/jira/browse/WEEX-41 > Project: Weex > Issue Type: Bug > Components: Android > Environment: Android >Reporter: moxun > Fix For: 0.13 > > > Now, some reference of DomObject in AbstractEditComponent#addEvent is > redundant, these are useless and led to some NullPointerException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (WEEX-39) Fix wrong vertical offset on waterfall
[ https://issues.apache.org/jira/browse/WEEX-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan updated WEEX-39: -- Component/s: Android > Fix wrong vertical offset on waterfall > -- > > Key: WEEX-39 > URL: https://issues.apache.org/jira/browse/WEEX-39 > Project: Weex > Issue Type: Bug > Components: Android > Environment: Android >Reporter: moxun > Fix For: 0.14 > > > The `RecyclerView#computeVerticalScrollOffset()` will return wrong value when > use `StaggeredGridLayoutManager`, add property `stable` to control calculated > vertical offset using accumulative `dy` > Property `stable` only effective on android, and will not be public in the > document -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (WEEX-40) Divide callNative，support DOM level API
[
https://issues.apache.org/jira/browse/WEEX-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sospartan updated WEEX-40:
--
Fix Version/s: 0.14
Component/s: Android
> Divide callNative，support DOM level API
> ---
>
> Key: WEEX-40
> URL: https://issues.apache.org/jira/browse/WEEX-40
> Project: Weex
> Issue Type: Improvement
> Components: Android
>Reporter: kfeagle
> Fix For: 0.14
>
>
> # DOM Operation Top-Level API
> `callNative` Segmentation，support native api as DOM level，it can improve
> performence , because it can reduce js-native communication.
> defalue `callNative` as follow：
> [
> // 0\. {String} document id ，usually app id
> '3',
> // 1\. {Array} task list
> [
> {
> // {String} module name
> module: 'dom',
> // {String} method in module，such as: createBody 、 updateAttrs 、
> removeEvent
> method: 'addElement',
> // {Array} task parameter
> args: [
> '23', // {String} element ref
> ... // other parameter
> ]
> }
> ],
> // 2\. {String} signal ， -1
> '-1'
> ]
> the design follow the standard that the first item is docId, the last item is
> signal. the middle parameter designed by function. you can refer to
> `callAddElement` to design other api
> 1. createBody
> Native provide： `callCreateBody` 。
> function parameter：
> [
> docId,
> // {Element} body
> {
> ref,
> type,
> attr,
> ...
> },
> '-1'
> ]
> 2. addElement
>Native provide： `callAddElement` 。（finished）
>function parameter：
>[
> docId,
> // {String} the element ref will be inserted
> ref,
> // {Element} the element will be inserted
> {
> ref,
> type,
> attr,
> ...
> },
> // {Number} insert index
> index,
> '-1'
> ]
> 3. removeElement
> Native provide： `callRemoveElement` 。
> function parameter：
>[
> docId,
> // {String} the ref will be delete
>ref,
> '-1'
> ]
> 4. moveElement
> Native provide： `callMoveElement` 。
> function parameter：
> [
> docId,
> // {String} the ref will be move
> targetRef,
> // {String} parent ref
> parentRef,
> // {Number} the index will move to
> index,
> '-1'
> ]
> 6. updateAttrs
> Native should provide： `callUpdateAttrs` 。
> function parameter：
> [
> docId,
> // {String} the ref will update
> ref,
> // {Object} new attribute，JSON object
> attrs,
> '-1'
> ]
> 8. updateStyle
> Native should provide： `callUpdateStyle` 。
> function parameter：
> [
> docId,
> // {String} the ref will update
> ref,
> // {Object} new style，JSON object
> attrs,
> '-1'
> ]
> 9. addEvent
> Native should provate： `callAddEvent` 。
> function parameter：
> [
> docId,
> // {String} the ref of element
> ref,
> // {String} event type， click | appear
> eventType,
> '-1'
> ]
> 10. removeEvent
> Native should provide method： `callRemoveEvent` 。
> function parameter：
> [
> docId,
> // {String} the ref of element whose event will remove
> ref,
> // {String} event type， click | appear
> eventType,
> '-1'
> ]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (WEEX-41) remove some redundant reference of DomObject in input component
[ https://issues.apache.org/jira/browse/WEEX-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-41. --- Resolution: Fixed > remove some redundant reference of DomObject in input component > --- > > Key: WEEX-41 > URL: https://issues.apache.org/jira/browse/WEEX-41 > Project: Weex > Issue Type: Bug > Environment: Android >Reporter: moxun > Fix For: 0.13, 0.14 > > > Now, some reference of DomObject in AbstractEditComponent#addEvent is > redundant, these are useless and led to some NullPointerException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (WEEX-41) remove some redundant reference of DomObject in input component
[ https://issues.apache.org/jira/browse/WEEX-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan updated WEEX-41: -- Fix Version/s: 0.14 0.13 > remove some redundant reference of DomObject in input component > --- > > Key: WEEX-41 > URL: https://issues.apache.org/jira/browse/WEEX-41 > Project: Weex > Issue Type: Bug > Environment: Android >Reporter: moxun > Fix For: 0.13, 0.14 > > > Now, some reference of DomObject in AbstractEditComponent#addEvent is > redundant, these are useless and led to some NullPointerException -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Weex-cli development
I agree with you. It's always welcomed, a better and easy tool for new user. It's very important to develop our community. I'm not expert in javascript/node, but I think a simple and lightweight tool is much suitable for us, as weex is still young and hunger to develop our users. Tiago, we shall start planing that if on one is against it. After the new tool hit some milestone, we could discuss to integrate to weex-toolkit or just replace it. On Tue, Jun 13, 2017 at 9:36 PM, Tiago Alves <tral...@gmail.com> wrote: > Hello Jerry, > > Yes, I checked the weexpack-android project. I noticed it is very similar > to > cordova-android <https://github.com/apache/cordova-android>. If fact, most > of the weexpack libs (weexpack-create, weexpack-common, weexpack-lib, > weexpack-iOS) are a trimmed version of the cordova-cli. > > My question in the last email was: have you ever considered building > something from scratch? The current project is very complex IMHO, more than > it should be. It is hard to follow and debug. It does lots of things that > makes sense in cordova but not in Weex, and at the same time doesn't do > everything it should do. Also, the code feels a bit outdated. I don't > know... it just feels a bit hacky... > > Please don't read this as a critique of the current work. I think it was a > genius idea to use cordova cli as a starting point. I just want to know if > you want to continue with this path, or if it is a good time to start a new > cli. I will contribute whatever the answer is, I just want to make the most > useful contribution in the long run. > > Thanks > Tiago > > On Tue, 13 Jun 2017 at 01:48 jerry.s <songhaiboh...@gmail.com> wrote: > > > Hi,Tiago: > > > > I think it is good thing if we have scaffold. we have finished some > > one for develop https://github.com/weexteam/generator-weex-plugin < > > https://github.com/weexteam/generator-weex-plugin> > > one for common user with weex > > https://github.com/weexteam/weexpack-android < > > https://github.com/weexteam/weexpack-android> doc > > https://weex.apache.org/guide/tools/toolkit.html < > > https://weex.apache.org/guide/tools/toolkit.html> > > These projects are open source . we are perfecting it , you can join us > > We can discuss it together:-) > > > > Best Regards > > Jerry > > > > > 在 2017年6月12日，下午8:55，Tiago Alves <tral...@gmail.com> 写道： > > > > > > Hi! > > > > > > I have noticed that many people drive away from weex because there is > > still > > > no clear, fully-working path to create a Weex project from scratch. > > > > > > I took a shot at contributing to that part some weeks ago but had to > stop > > > due to lack of time (or skill? :P). > > > > > > This is what I know: > > > > > > - Weex-toolkit (weex's cli) is, in a big part, a copy of the > > cordova-cli > > > implementation; > > > - Weex-toolkit platform add commands just copies a template to the > > > project, and does not make all the transformations that the > cordova-cli > > > does, such as: > > > - change the path names according to the project name; > > > - change the package names/folders in android according to the > > appID; > > > - change some file names according to the appId/bundleID in > > > android/iOS; > > > - change class names and other bits of code in the android/iOS > > > project to match the app name. > > > > > > > > > I would like weex-toolkit add platform commands to create a properly > > > configured project, with the correct name, bundle id, paths, > namespaces, > > > etc. And I am ready to dive into it again! > > > > > > So I have some questions: > > > > > > - Is anyone working on that? Someone I could join in this? Anyone > wants > > > to join me? > > > - Mirroring the cordova implementation seemed a very smart move to > get > > > with something working fast, but now it seems to me that it is an > > > over-engineered solution. Cordova is an old-ish project, and its cli > > > clearly had too many iteractions. I looked into the NativeScript cli > > (tns) > > > and it feels much more modern and fresh. Wouldn't it be a good idea > to > > > start a weex-toolkit from scratch? > > > - I created a vue-cli template for weex ( > > > https://github.com/tralves/weex-vue) that sets some variables and > > > configurations. I think it could be a good solution to have users > > bootstrap > > > the project with the vue-cli they already know and love, and then use > > the > > > weex-toolkit to work with the native and weex details. > > > > > > What are your thoughts? > > > > > > Thanks! > > > Tiago > > > > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
[jira] [Commented] (WEEX-43) Add release job to travis CI
[ https://issues.apache.org/jira/browse/WEEX-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16047683#comment-16047683 ] sospartan commented on WEEX-43: --- https://github.com/apache/incubator-weex/commit/b7813c74b9fcc8ce6107da0148dfff9b8bb86bc1 > Add release job to travis CI > > > Key: WEEX-43 > URL: https://issues.apache.org/jira/browse/WEEX-43 > Project: Weex > Issue Type: Task > Reporter: sospartan > > 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)
Re: Sorry about the CI email.
Raphael, Do you have any document/webpage about the 'moderate' thing? I can help to deal these problems in further. On Tue, Jun 13, 2017 at 1:11 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > No problem, I'll white list the ci mail adress, so the ci mails go to the > list without get moderated. > > Regards, Raphael > > Am .06.2017, 07:00 Uhr, schrieb sospartan <sospar...@apache.org>: > > Hi all, >> I'm testing the CI script. Sorry about the notify email. >> I'll disable notification before push to apache repo. >> >> > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Sorry about the CI email.
Hi all, I'm testing the CI script. Sorry about the notify email. I'll disable notification before push to apache repo. -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io>
[jira] [Updated] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo
[ https://issues.apache.org/jira/browse/WEEX-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan updated WEEX-44: -- Issue Type: Sub-task (was: Task) Parent: WEEX-43 > 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 > Reporter: sospartan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (WEEX-44) Add script to upload snapshot artifact to maven/pods repo
sospartan created WEEX-44: - Summary: 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: Task Reporter: sospartan -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (WEEX-43) Add release job to travis CI
sospartan created WEEX-43: - Summary: Add release job to travis CI Key: WEEX-43 URL: https://issues.apache.org/jira/browse/WEEX-43 Project: Weex Issue Type: Task Reporter: sospartan 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] [Updated] (WEEX-26) v0.12 release note
[ https://issues.apache.org/jira/browse/WEEX-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan updated WEEX-26: -- Summary: v0.12 release note (was: List feature of v0.12 release) > v0.12 release note > -- > > Key: WEEX-26 > URL: https://issues.apache.org/jira/browse/WEEX-26 > Project: Weex > Issue Type: Task > Reporter: sospartan > > I'll use this issue to draft our release note. > Because most of our features were discussed in dev mail list, I'll pick some > major change from it. Hope we can simply link to related JIRA issue next time. > This release note will save to release page in our > website(http://weex.apache.org/releasenote.html). > v0.12 release note(draft) > > - C++ timer by lycool > Discussed in > https://lists.apache.org/thread.html/567c9b19d68ccf3e0d24c1467298ebcd4316ffa524c557a34c6c087f@%3Cdev.weex.apache.org%3E > relate pull > requests:[apache/incubator-weex/pull/228|https://github.com/apache/incubator-weex/pull/228], > > [apache/incubator-weex/pull/232|https://github.com/apache/incubator-weex/pull/232], > > [apache/incubator-weex/pull/221|https://github.com/apache/incubator-weex/pull/221] > - Add scroller/list scroll event in html5 render > android already have this feature in v0.11 > https://github.com/apache/incubator-weex/commit/f50fba8647c8bb6ac522b1a4569a2a2269da1953 > - Enhance accessibility, new `aria-label` & `role` support > [apache/incubator-weex/pull/149|https://github.com/apache/incubator-weex/pull/149] > - Native input/textarea enhancement by kfeagle & misakuo > support `number` data type; support soft keyboard event > - Picker module enhancement > More picker options to customize picker dialog style(background color etc.). > Related pull requests: > [apache/incubator-weex/pull/234|https://github.com/apache/incubator-weex/pull/234], > > [apache/incubator-weex/pull/233|https://github.com/apache/incubator-weex/pull/233] > - Android DOM module refactor > Seperate module code by action, increasing the maintainability. > [apache/incubator-weex/pull/104|https://github.com/apache/incubator-weex/pull/104] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Good project communication 1
Now when travis CI Failed, a mail notification will send to dev@ https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=blobdiff;f=.travis.yml;h=9e0e77d6903263a2372fa92d576b66acb3a87ce4;hp=d0b76756567616a85007ca5962d2cb927d5c9637;hb=8e1cc1f62b6f5689bb91bedb4f20786f2b3e03b6;hpb=c689a8ab731b80519bb1e852cce39b2e54a5c36e On Mon, Jun 12, 2017 at 2:51 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all, > > Am .06.2017, 08:39 Uhr, schrieb sospartan <sospar...@gmail.com>: > > On Mon, Jun 12, 2017 at 1:18 PM, Raphael Bircher <rbircherapa...@gmail.com >> > >> wrote: >> >> Hi all >>> >>> So here is what I understand under a good project communication. >>> >>> All relevant Informations go to the Mailing list. >>> >>> You have not to bring all Informations to the Mailing list. If you for >>> example work together with an other person on a problem. You have not to >>> do >>> this on the ML. You can use Chat of Face to Face discussion. If you would >>> bring all this communication to the Ml, we will have 100 mails per day, >>> with a load of content not interesting for all. The ML get unreadable, >>> and >>> that's the last thing we want. >>> >>> Ho ever, sometimes you get the feeling that you have something the other >>> peoples have to know. Than simply stop the private discussion, and drop a >>> mail to the list. This can be the following: >>> >>> 1) Compiling problems (everyone can run into it) >>> >>> >> We are using travis to run CI. I'll make some change to notify dev@ ML >> whenever it failed. >> >> >> 2) Problems who affects others. >>> 2) Start working at a problem (to avoid double work) >>> 4) End of the problem, with a link to the commit, patch or what ever. >>> >>> >> About the 3 and 4, we use JIRA to document all WIP issues, which will send >> to ML about anything changed or status updated. Is this count? >> > In the Apache terms this is enough, yes. > >> >> >> 5) DECISION MAKING >>> >>> The last part is the most important one. Decisions has to be made in >>> public! There the project has most to work right now! >>> >>> >> The last one is also the most difficult. But we should start now. Let's >> start with bringing all proposal to the mail list. >> > Can someone tell me why this is so difficult for you. Do you know how lazy > consensus works? > > > Regards, Raphael > > > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Good project communication 1
On Mon, Jun 12, 2017 at 1:18 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all > > So here is what I understand under a good project communication. > > All relevant Informations go to the Mailing list. > > You have not to bring all Informations to the Mailing list. If you for > example work together with an other person on a problem. You have not to do > this on the ML. You can use Chat of Face to Face discussion. If you would > bring all this communication to the Ml, we will have 100 mails per day, > with a load of content not interesting for all. The ML get unreadable, and > that's the last thing we want. > > Ho ever, sometimes you get the feeling that you have something the other > peoples have to know. Than simply stop the private discussion, and drop a > mail to the list. This can be the following: > > 1) Compiling problems (everyone can run into it) > We are using travis to run CI. I'll make some change to notify dev@ ML whenever it failed. > 2) Problems who affects others. > 2) Start working at a problem (to avoid double work) > 4) End of the problem, with a link to the commit, patch or what ever. > About the 3 and 4, we use JIRA to document all WIP issues, which will send to ML about anything changed or status updated. Is this count? > 5) DECISION MAKING > > The last part is the most important one. Decisions has to be made in > public! There the project has most to work right now! > The last one is also the most difficult. But we should start now. Let's start with bringing all proposal to the mail list. > Regards, Raphael > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Some initial word as a Mentor
In my opinion, the mentors would tell us something is not right/properly in apache. Or the way we doing something is just not apache way... expect that is documented, which mentors can just send a link from the massive apache doc website. Anyway, I think all contributors/committer should start talk more in here. Then everybody wanna help can join us. On Sun, Jun 11, 2017 at 3:28 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all, > > As you notice, I'm now your mentor. It was requested by you, thank you for > the confidence. But before we start, I want to tell you, how I see my > mentor role. > > My main goal as a mentor here is to get superfluous. If you live as an > Apache project without my help, I did a good job. My job as a mentor is not > to develop weex. My job is just help you, to get into Apache. > > I'm just a mentor, not a chef. In most case my words are not binding for > you. At the moment i have a bit the impression that the project looking at > the mentors as they are leaders. That's not the case. We are all Leaders > here. We all role the project. We dessicate as a community. Thats the big > difference between The ASF and a company. So don't take me too serious. > Don't just copy my idea. If you think this idea is stupid, tell it! and > make a better proposal. > > Thanks a load, and for a good collaboration. > > Regards Raphael > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: I'm Mentor
Welcome ... again! Shall we figure out a plan or something as first step? On Fri, Jun 9, 2017 at 7:49 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all > > I just got added to the mentors. So lets start the work here. > > Regards, Raphael > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: I think we can release now
Finally! First release! I'll send a [RESULT]. Thanks you for the help. On Thu, Jun 8, 2017 at 4:16 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all, > > It looks like the release passed the incubator vote. We have 3 +1 and no > -1. So we can go out. Congatulate guys! > > Regards, Raphael > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: dynamic loading libweexjsc.so
Hi nan, It would be that big after package into apk file. The truth is v0.12 will increase about 1 MB. The JS engine have changed to JSC. On Tue, Jun 6, 2017 at 5:47 PM, nan <qiandua...@qq.com> wrote: > hi all： > > I find the libweexjsc.so increase to 7.21MB at 0.12.0 version. > this is too big for our app，so I want to known can I dynamic loading the > libweexjsc.so file? > and there has any problem？ -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Nightly builds for weex
Hi, Run a RAT and even build android is doable. But the iOS build require MacOS machine. I've already tried the build.apache.org service. They no longer provide mac machine. Currently, I use a local mac mini machine(with jenkins) to run all these jobs. On Tue, Jun 6, 2017 at 3:07 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all > > I believe that weex would profit from nightly builds. They should run a > RAT test and build the project. Apache has the infrastructure to do > something like this. > > What do you think about it. > > Regards, Raphael > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
[RESULT][VOTE]Apache Weex-incubating Release 0.12.0-RC5
Hi all, The vote about releasing 0.12.0-RC5 has passed with 4 +1 binding. Thanks to Tancy Ni, Bobing Ning, Xing Zhang, Jerry S -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io>
Re: [VOTE]Apache Weex-incubating Release 0.12.0-RC5
And this is last RC about v0.12 If this RC fail, we probably should start releasing v0.13 On Fri, Jun 2, 2017 at 3:58 PM, xing zhang <zhangxing610...@gmail.com> wrote: > +1 > > 2017-06-02 15:21 GMT+08:00 jerry.s <songhaiboh...@gmail.com>: > > > +1 Best Wishes! > > > 在 2017年6月2日，下午3:16，宁栗 <ningli...@gmail.com> 写道： > > > > > > +1 > > > > > > 2017-06-02 15:13 GMT+08:00 Tancy Ni <ron...@gmail.com>: > > > > > >> +1 > > >> > > >> sospartan <sospar...@apache.org>于2017年6月2日周五 下午3:07写道： > > >> > > >>> Hi Weex PPMC, > > >>> I'll calling a vote for release Weex-incubating 0.12.0-RC5. > > >>> Fix some issues point out by IPMC. Hope this one will have a > > >>> 'full-green' pass. > > >>> > > >>> > > >>> The tag to be voted upon: > > >>> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > >>> ;a=shortlog;h=refs/tags/0.12.0-rc5 > > >>> > > >>> The commit hash: > > >>> > > >>> https://git-wip-us.apache.org/repos/asf?p=incubator-weex. > > git;a=commit;h= > > >> dcf9a83360b4403ffbdbfb3e168a68d1ff7a2b38 > > >>> > > >>> The source tarball can be found at: > > >>> > > >>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12. > > >> 0-incubating/RC5/ > > >>> > > >>> The fingerprint of key to sign release artifacts: > > >>> 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > >>> > > >>> Release artifacts are signed with the following key: > > >>> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > >>> > > >>> Release note about this version: > > >>> https://issues.apache.org/jira/browse/WEEX-26 > > >>> > > >>> This vote will remain open for at least 72 hours. > > >>> Please vote on releasing this RC. > > >>> > > >>> [ ] +1 approve > > >>> [ ] +0 no opinion > > >>> [ ] -1 disapprove (and reason why) > > >>> > > >>> -- > > >>> Best Regards! > > >>> > > >>> sospartan > > >>> http://weex.apache.org/ <https://weex-project.io> > > >>> > > >> > > > > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
[VOTE]Apache Weex-incubating Release 0.12.0-RC5
Hi Weex PPMC, I'll calling a vote for release Weex-incubating 0.12.0-RC5. Fix some issues point out by IPMC. Hope this one will have a 'full-green' pass. The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git ;a=shortlog;h=refs/tags/0.12.0-rc5 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=dcf9a83360b4403ffbdbfb3e168a68d1ff7a2b38 The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC5/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io>
Re: Build instructions
Yes, currently the steps are complicated. Since it need both iOS, android and nodejs environment. Every single one is hard enough for a new guy who is not familiar with these stack. Also I have include a 'README_RELEASE.md' to explain these. I really don't know how to make these steps easier. A contributing instruction is under 'guide' on the website: http://weex.apache.org/guide/contributing.html On Thu, Jun 1, 2017 at 9:01 AM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all, > > We need better build instructions. Also we need an instruction on the > website, how to join the community. > > Regards, Raphael > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Release of the 0.12.0 version
Thank you anyway. I'll send a [RESULT] later. Raphael Bircher <rbircherapa...@gmail.com>于2017年5月31日 周三上午11:02写道： > Hi all, > > I made a mistake. I proposed a new vote on the RC4. This was not needed. > I'm sorry for that. > > I propose to cancel the second vote. The first vote has enough +1 votes, > so the release should pass. > > Regards, Raphael > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: Release Vote about 0.12 RC4
The binaries were all excluded in this release. In previous release we do include a gradle wrapper jar and v8 library (a .so file). I've double checked this issue in current release. This is no longer a problem. :P On Thu, May 18, 2017 at 5:13 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi Sospartan > > leave it open a little bit longer, remember, many peoples are at the > ApacheCon. > > A question about the release. Is it true that you have a binary tar.gz in > the release folder? under witch license are this binaries? As far as I > know, the normal way under Apache is to host such binaries outside ASF > infrastructure. > > Regards, Raphael > > Am .05.2017, 07:49 Uhr, schrieb sospartan <sospar...@apache.org>: > > Hi Rapheal, >> The vote received 1 +1 binding, and the time is pass 72 hours as I >> declared >> in the first mail. >> Should I announce the vote is failed? Or 1 +1 is enough to pass the >> release >> vote? >> >> > > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Release Vote about 0.12 RC4
Hi Rapheal, The vote received 1 +1 binding, and the time is pass 72 hours as I declared in the first mail. Should I announce the vote is failed? Or 1 +1 is enough to pass the release vote? -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io>
Re: Introduce myself
Welcome. I'm sospartan. As rest of our committers, from china, mostly coding in github, very new to ASF development. When did you join OpenOffice? On Wed, May 17, 2017 at 5:57 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all > > My name is Raphael Bircher. I'm a IPMC Member and I heard your call for > help on the general@i.a.o list. So maybe I can help. I'm from Switzerland > and my "home" project is Apache OpenOffice. If you have questions, just ask. > > Regards Raphael > > -- > My introduction https://youtu.be/Ln4vly5sxYU > -- sospartan Phone:13588488290 HangZhou
[jira] [Commented] (WEEX-26) List feature of v0.12 release
[ https://issues.apache.org/jira/browse/WEEX-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009935#comment-16009935 ] sospartan commented on WEEX-26: --- Lin, As you can see, we are still working on making our first 'apache release'. After figure out these policy-related stuff, we'll release regularly. > List feature of v0.12 release > - > > Key: WEEX-26 > URL: https://issues.apache.org/jira/browse/WEEX-26 > Project: Weex > Issue Type: Task > Reporter: sospartan > > I'll use this issue to draft our release note. > Because most of our features were discussed in dev mail list, I'll pick some > major change from it. Hope we can simply link to related JIRA issue next time. > This release note will save to release page in our > website(http://weex.apache.org/releasenote.html). > v0.12 release note(draft) > > - C++ timer by lycool > Discussed in > https://lists.apache.org/thread.html/567c9b19d68ccf3e0d24c1467298ebcd4316ffa524c557a34c6c087f@%3Cdev.weex.apache.org%3E > relate pull > requests:[apache/incubator-weex/pull/228|https://github.com/apache/incubator-weex/pull/228], > > [apache/incubator-weex/pull/232|https://github.com/apache/incubator-weex/pull/232], > > [apache/incubator-weex/pull/221|https://github.com/apache/incubator-weex/pull/221] > - Add scroller/list scroll event in html5 render > android already have this feature in v0.11 > https://github.com/apache/incubator-weex/commit/f50fba8647c8bb6ac522b1a4569a2a2269da1953 > - Enhance accessibility, new `aria-label` & `role` support > [apache/incubator-weex/pull/149|https://github.com/apache/incubator-weex/pull/149] > - Native input/textarea enhancement by kfeagle & misakuo > support `number` data type; support soft keyboard event > - Picker module enhancement > More picker options to customize picker dialog style(background color etc.). > Related pull requests: > [apache/incubator-weex/pull/234|https://github.com/apache/incubator-weex/pull/234], > > [apache/incubator-weex/pull/233|https://github.com/apache/incubator-weex/pull/233] > - Android DOM module refactor > Seperate module code by action, increasing the maintainability. > [apache/incubator-weex/pull/104|https://github.com/apache/incubator-weex/pull/104] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Source code from other open source projects
I've make changes to LICENSE file and remove src-header in source code from vuejs[1]. John & Taylor, Thanks for point these thing out. I'll read these apache documents... I would have a english degree when weex graduated from incubator. It's more like a massive network, not some documents. BTW, what is 'SGA' stands for? [1] https://github.com/apache/incubator-weex/commit/d19b3565a7c0ffef3a7178d11d85e7277e77ac3f On Wed, May 10, 2017 at 9:52 AM, John D. Ament <johndam...@apache.org> wrote: > On Tue, May 9, 2017 at 12:59 PM P. Taylor Goetz <ptgo...@gmail.com> wrote: > > > On May 9, 2017, at 11:13 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > > > > I am inviting Taylor and John to provide guidance around latest > > requirements. Gentlemen... > > > > Cheers > > Niclas > > > > On Tue, May 9, 2017 at 4:58 PM, sospartan <sospar...@gmail.com> wrote: > > > >> Hi Niclas, > >> We have 3 folder contain source codes from other projects. > >> > >> 1.'android/sdk/src/main/java/com/taobao/weex/dom/flex' > >> 2.'ios/sdk/WeexSDK/Sources/Layout/' > >> > >> These two from 'CSSLayout' project(https://github.com/facebook/yoga > >> raname to yoga later 2016). We haven't change any of them. > >> > > > > As Niclas suggested, if the files are unchanged then just make sure the > > original license header is in place. If you change them later in a > > significant way, add the Apache header. > > > > Just a note - before adding a header to any source file that was not > created here and not part of the original donation, consult with legal on > what to do. > > I'll also note that this sounds partially like the original SGA is invalid, > may be worth a follow up on. (We can talk privately about it if you're not > clear). > > > > > > Then add either add a pointer to the license or the text of the license > in > > your LICENSE file. See here [1] for further guidance. > > > > The commit to the LICENSE file you reference mostly suffices. The only > > thing I would add would be for each license added to LICENSE, make sure > you > > point out exactly which file(s) it applies to. > > > > > > > > > >> 3.'html5/frameworks/legacy/core' > >> Codes inside this folder is based on vuejs. And every file contain > >> both vuejs and weex license header > >> > >> NOTICE already include vuejs and yoga. > >> LICENSE have append these two projects' license by recent commit > >> ( > >> > >> https://github.com/apache/incubator-weex/commit/ > 65314df30a50a17929ecb2297cdbe4009616ddd1 > >> ). > >> > >> Anything else? I don't see much about 'bundled code' beside append them > to > >> LICENSE. > >> > > > > > > I think you are on the right track. Again, the Licensing Howto [2] is a > > pretty good guide for sorting this stuff out. > > > > > From looking at the code, and the code presently in Vuejs, I'm actually > going to say that the current headers are potentially incorrect and we > should be consulting legal on what the correct headers should be. But > since its appropriately licensed its not something that has to be fixed > right this second if its wrong. > > The reason why I'm saying its wrong, is if I look at > https://github.com/vuejs/vue/blob/dev/src/core/instance/state.js (which > I'm > not 100% sure you've derived from) there is no existing header. That > doesn't mean we should add a header. The current trend is to add no > headers, and add a call out in the LICENSE to the appropriate license. > > > > > > -Taylor > > > > [1] http://www.apache.org/dev/licensing-howto.html#permissive-deps > > [2] http://www.apache.org/dev/licensing-howto.html > > > > > > > > > >> > >> On Fri, May 5, 2017 at 1:41 PM, Niclas Hedhman <nic...@hedhman.org> > >> wrote: > >> > >> > That depends on the license of other project. > >> > > >> > If it is under so called permissive licenses, such as Apache, BSD and > >> MIT, > >> > then this is allowed. > >> > > >> > If files are NOT changed, then the license headers remains intact. IF > >> you > >> > modify the files (anything beyond a one-liner), you should ADD the > >> Apache > >> > license header AS WELL. Also, you need to include NOTICE as required > per > >> > license (not always), and the full license text should be added. > >> > > >> > This is kno
[jira] [Commented] (WEEX-33) Config Ability in weex
[ https://issues.apache.org/jira/browse/WEEX-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003920#comment-16003920 ] sospartan commented on WEEX-33: --- -1, This module is no necessary for SDK. You can totally create module in your application project. If these 'prefetch'/ 'prerender' have related interfaces, creating a module would not be take much work. > Config Ability in weex > -- > > Key: WEEX-33 > URL: https://issues.apache.org/jira/browse/WEEX-33 > Project: Weex > Issue Type: New Feature >Reporter: xingjiu > 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.3.15#6346)
Re: Source code from other open source projects
Hi Niclas, We have 3 folder contain source codes from other projects. 1.'android/sdk/src/main/java/com/taobao/weex/dom/flex' 2.'ios/sdk/WeexSDK/Sources/Layout/' These two from 'CSSLayout' project(https://github.com/facebook/yoga raname to yoga later 2016). We haven't change any of them. 3.'html5/frameworks/legacy/core' Codes inside this folder is based on vuejs. And every file contain both vuejs and weex license header NOTICE already include vuejs and yoga. LICENSE have append these two projects' license by recent commit ( https://github.com/apache/incubator-weex/commit/65314df30a50a17929ecb2297cdbe4009616ddd1 ). Anything else? I don't see much about 'bundled code' beside append them to LICENSE. On Fri, May 5, 2017 at 1:41 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > That depends on the license of other project. > > If it is under so called permissive licenses, such as Apache, BSD and MIT, > then this is allowed. > > If files are NOT changed, then the license headers remains intact. IF you > modify the files (anything beyond a one-liner), you should ADD the Apache > license header AS WELL. Also, you need to include NOTICE as required per > license (not always), and the full license text should be added. > > This is known as "bundled with" in the release policy. Please read more > details in http://www.apache.org/legal/release-policy.html > > Cheers > > On Fri, May 5, 2017 at 12:05 PM, sospartan <sospar...@apache.org> wrote: > > > Hi mentors, > > Can we directly use/include source code from other projects? > > For example, the playground app(android/playground/app/ > > src/main/java_zxing) > > using zxing right now. Is this legal as a apache project? > > > > -- > > Best Regards! > > -- > > > > sospartan > > https://weex-project.io > > > > > > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
Re: [DISCUSS]Source Release of Weex
Another script I'll create is use to modify package of android SDK source. From 'com.taobao.*' to 'org.apache.*'. On Fri, May 5, 2017 at 3:59 PM, sospartan <sospar...@apache.org> wrote: > Hi, > The 0.12.0 RC3 is failed again. The committee fellows think there > still lots of problems in our release.We should try hard. > > Since weex project produce **Weex SDK**, the release tarball should > only include files required for building it. > > Mentors, is this a proper way to simplify release? > > So I'll update the release script, everything will be removed except: > > * license related files: LICENSE, NOTICE, DISCLAIMER > * android/ios/html5 SDK source code files: android/sdk, ios/sdk, html5/ > * build related files: package.json, build.gradle, podspec, etc. > * documents for ‘how to build weex SDK from source' and some > necessary scripts. > > There will be no playground app or weex examples scripts. > > Anything else I should bring in, pls let me know. > > > -- > Best Regards! > -- > > sospartan > https://weex-project.io > -- Best Regards! -- sospartan https://weex-project.io
[DISCUSS]Source Release of Weex
Hi, The 0.12.0 RC3 is failed again. The committee fellows think there still lots of problems in our release.We should try hard. Since weex project produce **Weex SDK**, the release tarball should only include files required for building it. Mentors, is this a proper way to simplify release? So I'll update the release script, everything will be removed except: * license related files: LICENSE, NOTICE, DISCLAIMER * android/ios/html5 SDK source code files: android/sdk, ios/sdk, html5/ * build related files: package.json, build.gradle, podspec, etc. * documents for ‘how to build weex SDK from source' and some necessary scripts. There will be no playground app or weex examples scripts. Anything else I should bring in, pls let me know. -- Best Regards! -- sospartan https://weex-project.io
Re: [VOTE]Apache Weex-incubating Release 0.12.0-RC3
This should be 'RC2', since it's the third RC of 0.12.0, after RC0 and RC1. But I make a mistake in last vote in IPMC, already used the name "RC2". So On Fri, Apr 28, 2017 at 4:51 PM, sospartan <sospar...@apache.org> wrote: > Hi Weex PPMC, > I'll calling a vote for release Weex-incubating 0.12.0-RC3. > > The tag to be voted upon: > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > ;a=shortlog;h=refs/tags/0.12.0-rc3 > > The commit hash: > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= > 702d04c4922105069f537afdb4688f808530994d > > The source tarball can be found at: > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0 > -incubating/RC3/ > > The fingerprint of key to sign release artifacts: > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > Release artifacts are signed with the following key: > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > Release note about this version: > https://issues.apache.org/jira/browse/WEEX-26 > > This vote will remain open for at least 72 hours. > Please vote on releasing this RC. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > -- > Best Regards! > -- > > sospartan > https://weex-project.io > -- Best Regards! -- sospartan https://weex-project.io
[VOTE]Apache Weex-incubating Release 0.12.0-RC3
Hi Weex PPMC, I'll calling a vote for release Weex-incubating 0.12.0-RC3. The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git ;a=shortlog;h=refs/tags/0.12.0-rc3 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=702d04c4922105069f537afdb4688f808530994d The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC3/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards! -- sospartan https://weex-project.io
Re: Release
Beside these 3, is there any new conclusions? I'm ready to start RC3.
Like John D.Ament said in general@i.a.o, should I make a new NOTICE, put
every bundled dependencies's license in it ?
On Sun, Apr 23, 2017 at 9:47 AM, Niclas Hedhman <nic...@hedhman.org> wrote:
> After the arguments on general@i.a.o, let's pull this RC and make the
> following changes,
>
> 1. NOTICE file to be renamed. POSSIBLE-NOTICES-FOR-BIN-DIST
>
> 2. The tarball (tar.gz and/or zip) should contain the "incubating" in the
> name. Easiest is to put that in the "version" and make the "version" part
> of the filename, typically apache-weex-${version}.tar.gz
>
> 3. If not too much hassle, root directory inside the tarball has the same
> name as the tarball (without extension).
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://polygene.apache.org - New Energy for Java
>
--
sospartan
Phone:13588488290
HangZhou
Re: [Discuss]Podling Report - May 2017
I'll try my best to digest that. I've removed everything except the release issue. Anyone have anything else to add to that part? Updated: - Weex Weex is a framework for building Mobile cross-platform high performance UI. Weex has been incubating since 2016-11-30. Three most important issues to address in the move towards graduation: 1. Move the whole workflow and infra into Apache (not the codebase only). 2. Develop more contributors and committers. 3. First Release while in Incubator. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? We are worried that only 1 mentor is actively helping us, as this will put more burden on the rest of the Incubator to approve our releases. Especially, most of active committers are not good at dealing with license-related problem. How has the community developed since the last report? * We voted in 3 new committer:TianYi Ma, Tancy and HaiBo Song. * There are 90+ new forks and 700+ new stars since last report. * We have encouraged people to discuss more in the JIRA and dev mail list. Up to now, 30 issues are reported on JIRA and 25 of them are resovled. * We have redirect github's mails to the commits mail list to have a clear overview of our activity in the dev mail list. How has the project developed since the last report? * We are trying to release 0.12 this month. Both two RCs were failed due to the license issue. This is major issue of project. How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [x] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: -XX-XX When were the last committers or PPMC members elected? TianYi Ma, 5 April 2017 Tancy, 18 April 2017 HaiBo Song, 24 April 2017 - On Thu, Apr 27, 2017 at 4:25 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > "Project being developed" is from ASF's point of view is primarily about > "Community" and secondarily about "Releases". Whether there is a new > feature, or some big bug fixed is quite irrelevant, the rest of the ASF > trust the project to handle this. > > I think I can summarize it as; > > The ASF wants to see a bunch of people to work well together, towards > making releases. > > Anything that touches on that might be of interest. Say that you have not > released for a lng time (Polygene is now almost 2 years since last > release), it is good to bring up why, which in Polygene's case is a > combination of "small community", "convert to Java 8 Functional API" (we > had our own before), "incompatibility changes" (want all changes breaking > compatibility in one go) but more technical reasons than that (the rewrite > of serialization subsystem presented many challenges) is not needed. We > will get there... eventually. > > Cheers > Niclas > > > On Thu, Apr 27, 2017 at 4:06 PM, sospartan <sospar...@gmail.com> wrote: > > > The 'technical stuff', you mean the content I put in 'How has the project > > developed'? > > It's really difficult to me to answer that question without these > details. > > > > Updated: > > - > > Weex > > > > Weex is a framework for building Mobile cross-platform high performance > UI. > > > > Weex has been incubating since 2016-11-30. > > > > Three most important issues to address in the move towards graduation: > > > > 1. Move the whole workflow and infra into Apache (not the codebase > only). > > 2. Develop more contributors and committers. > > 3. First Release while in Incubato > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > > aware of? > > > > No > > > > How has the community developed since the last report? > > > > * We voted in 3 new committer:TianYi Ma, Tancy and HaiBo Song. > > * There are 90+ new forks and 700+ new stars since last report. > > * We have encouraged people to discuss more in the JIRA and dev > > mail list.Up to now, 30 issues are reported on JIRA and 25 of them > > is resovled. > >* We have redirect github's mails to the commits mail list to have a > > clear overview of our activity in the dev mail list. > > > > How has the project developed since the last report? > > > > * We are trying to release 0.12.0 this month. Both two RCs were failed > > due > > to the license issue. > > * Current development is focus on enhance preload solution, event > handle > > and > > match up html5 version to
Re: [Discuss]Podling Report - May 2017
The 'technical stuff', you mean the content I put in 'How has the project developed'? It's really difficult to me to answer that question without these details. Updated: - Weex Weex is a framework for building Mobile cross-platform high performance UI. Weex has been incubating since 2016-11-30. Three most important issues to address in the move towards graduation: 1. Move the whole workflow and infra into Apache (not the codebase only). 2. Develop more contributors and committers. 3. First Release while in Incubato Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? * We voted in 3 new committer:TianYi Ma, Tancy and HaiBo Song. * There are 90+ new forks and 700+ new stars since last report. * We have encouraged people to discuss more in the JIRA and dev mail list.Up to now, 30 issues are reported on JIRA and 25 of them is resovled. * We have redirect github's mails to the commits mail list to have a clear overview of our activity in the dev mail list. How has the project developed since the last report? * We are trying to release 0.12.0 this month. Both two RCs were failed due to the license issue. * Current development is focus on enhance preload solution, event handle and match up html5 version to native SDK. * And Vue2.0 adaptation is almost finish, rest of it will end in upcoming version 0.13 How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [x] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: -XX-XX When were the last committers or PPMC members elected? TianYi Ma, 5 April 2017 Tancy, 18 April 2017 HaiBo Song, 24 April 2017 - On Thu, Apr 27, 2017 at 3:32 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > Isn't ICLA cleared up yet? If it is already done, take it off, and put > "First Release while in Incubator" on there. > > I actually think that "developing community" is already strong point, and I > don't think there is much to do in the near future there. > > "We developed 3 new committer" --> "We voted in 3 new committers" (it is > people, not a subsystem ;-) ) > > And in general, no need to mention technical stuff at all. Very few people > care. > > > Cheers > Niclas > > On Thu, Apr 27, 2017 at 2:40 PM, sospartan <sospar...@apache.org> wrote: > > > Hi all, > > Here is the draft for report: > > - > > Weex > > > > Weex is a framework for building Mobile cross-platform high performance > UI. > > > > Weex has been incubating since 2016-11-30. > > > > Three most important issues to address in the move towards graduation: > > > > 1. Move the whole workflow and infra into Apache (not the codebase > only). > > 2. Develop more contributors and committers. > > 3. Clear the ICLA issues. > > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be > > aware of? > > > > No > > > > How has the community developed since the last report? > > > > * We developed 3 new committer:TianYi Ma, Tancy and HaiBo Song. > > * There are 90+ new forks and 700+ new stars since last report. > > * We have encouraged people to discuss more in the JIRA and dev > > mail list.Up to now, 30 issues are reported on JIRA and 25 of them > > is resovled. > >* We have redirect github's mails to the commits mail list to have a > > clear overview of our activity in the dev mail list. > > > > How has the project developed since the last report? > > > > * We are trying to release 0.12.0 this month. Both two RCs were failed > > due > > to the license issue. > > * Current development is focus on enhance preload solution, event > handle > > and > > match up html5 version to native SDK. > > * And Vue2.0 adaptation is almost finish, rest of it will end in > upcoming > > version 0.13 > > > > How would you assess the podling's maturity? > > Please feel free to add your own commentary. > > > > [ ] Initial setup > > [x] Working towards first release > > [ ] Community building > > [ ] Nearing graduation > > [ ] Other: > > > > Date of last release: > > > > -XX-XX > > > > When were the last committers or PPMC members elected? > > TianYi Ma, 5 April 2017 > > Tancy, 18 April 2017 > > HaiBo Song, 24 April 2017 > > > > - > > > > I'd like to hear from all you guys about this report, and how we did this > > month. > > > > -- > > Best Regards! > > -- > > > > sospartan > > https://weex-project.io > > > > > > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
[Discuss]Podling Report - May 2017
Hi all, Here is the draft for report: - Weex Weex is a framework for building Mobile cross-platform high performance UI. Weex has been incubating since 2016-11-30. Three most important issues to address in the move towards graduation: 1. Move the whole workflow and infra into Apache (not the codebase only). 2. Develop more contributors and committers. 3. Clear the ICLA issues. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No How has the community developed since the last report? * We developed 3 new committer:TianYi Ma, Tancy and HaiBo Song. * There are 90+ new forks and 700+ new stars since last report. * We have encouraged people to discuss more in the JIRA and dev mail list.Up to now, 30 issues are reported on JIRA and 25 of them is resovled. * We have redirect github's mails to the commits mail list to have a clear overview of our activity in the dev mail list. How has the project developed since the last report? * We are trying to release 0.12.0 this month. Both two RCs were failed due to the license issue. * Current development is focus on enhance preload solution, event handle and match up html5 version to native SDK. * And Vue2.0 adaptation is almost finish, rest of it will end in upcoming version 0.13 How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [x] Working towards first release [ ] Community building [ ] Nearing graduation [ ] Other: Date of last release: -XX-XX When were the last committers or PPMC members elected? TianYi Ma, 5 April 2017 Tancy, 18 April 2017 HaiBo Song, 24 April 2017 - I'd like to hear from all you guys about this report, and how we did this month. -- Best Regards! -- sospartan https://weex-project.io
Re: Podling Report Reminder - May 2017
Does this report require contain any different content than regular month report? I'll post the draft of this report in dev@ . On Thu, Apr 27, 2017 at 10:23 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > For the record, this should be the first report on a quarterly schedule. > > On Thu, Apr 27, 2017 at 8:41 AM, <johndam...@apache.org> wrote: > > > Dear podling, > > > > This email was sent by an automated system on behalf of the Apache > > Incubator PMC. It is an initial reminder to give you plenty of time to > > prepare your quarterly board report. > > > > The board meeting is scheduled for Wed, 17 May 2017, 10:30 am PDT. > > The report for your podling will form a part of the Incubator PMC > > report. The Incubator PMC requires your report to be submitted 2 weeks > > before the board meeting, to allow sufficient time for review and > > submission (Wed, May 03). > > > > Please submit your report with sufficient time to allow the Incubator > > PMC, and subsequently board members to review and digest. Again, the > > very latest you should submit your report is 2 weeks prior to the board > > meeting. > > > > Thanks, > > > > The Apache Incubator PMC > > > > Submitting your Report > > > > -- > > > > Your report should contain the following: > > > > * Your project name > > * A brief description of your project, which assumes no knowledge of > > the project or necessarily of its field > > * A list of the three most important issues to address in the move > > towards graduation. > > * Any issues that the Incubator PMC or ASF Board might wish/need to be > > aware of > > * How has the community developed since the last report > > * How has the project developed since the last report. > > * How does the podling rate their own maturity. > > > > This should be appended to the Incubator Wiki page at: > > > > https://wiki.apache.org/incubator/May2017 > > > > Note: This is manually populated. You may need to wait a little before > > this page is created from a template. > > > > Mentors > > --- > > > > Mentors should review reports for their project(s) and sign them off on > > the Incubator wiki page. Signing off reports shows that you are > > following the project - projects that are not signed may raise alarms > > for the Incubator PMC. > > > > Incubator PMC > > > > > > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
Re: commits@
I have created a new PR #281 https://github.com/apache/incubator-weex/pull/281 Niclas Hedhman <nic...@hedhman.org>于2017年4月22日 周六下午3:38写道： > Can someone make some "noise" on GitHub, such as comment on PR, create a PR > or similar? > > infra@ has redirected to comm...@weex.apache.org for these notifications > and asking for a confirmation. > > Thanks > Niclas > > > On Wed, Apr 19, 2017 at 11:50 AM, Niclas Hedhman <nic...@hedhman.org> > wrote: > > > https://issues.apache.org/jira/browse/INFRA-13922 > > > > On Tue, Apr 18, 2017 at 9:06 PM, Niclas Hedhman <nic...@hedhman.org> > > wrote: > > > >> I am pretty sure we can ask infra@ to move it. > >> > >> On Tue, Apr 18, 2017 at 6:44 PM, sospartan <sospar...@apache.org> > wrote: > >> > >>> Agreed. I used to think these mails are fixed into dev@ > >>> > >>> On Tue, Apr 18, 2017 at 5:56 PM, Niclas Hedhman <nic...@hedhman.org> > >>> wrote: > >>> > >>> > Gang, > >>> > I would like to propose that the GitHub "pull request" and "issue" > >>> mails > >>> > are directed to the commits@ list, rather than the dev@ list. > >>> > > >>> > Due to the RTC these mail is dominating the dev@ list and it is not > >>> easy > >>> > to > >>> > get an overview of what is actually being discussed in the community, > >>> and > >>> > any newcomer is likely to ignore it all, as the volume is frankly too > >>> high. > >>> > > >>> > WDYAT? > >>> > > >>> > Cheers > >>> > -- > >>> > Niclas Hedhman, Software Developer > >>> > http://polygene.apache.org - New Energy for Java > >>> > > >>> > >>> > >>> > >>> -- > >>> Best Regards! > >>> -- > >>> > >>> sospartan > >>> https://weex-project.io > >>> > >> > >> > >> > >> -- > >> Niclas Hedhman, Software Developer > >> http://polygene.apache.org - New Energy for Java > >> > > > > > > > > -- > > Niclas Hedhman, Software Developer > > http://polygene.apache.org - New Energy for Java > > > > > > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
Re: Use builds.apache.org service to build weex
Thanks! On Fri, Apr 21, 2017 at 3:23 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > I have added you to the group > > $> modify_appgroups.pl hudson-jobadmin --add=sospartan > > However, I am not sure whether that is enough or not to set up a project. > Let me know, if you need something else... > > Cheers > Niclas > > On Fri, Apr 21, 2017 at 2:53 PM, sospartan <sospar...@apache.org> wrote: > > > > Dear mentors, > > May I request the permission to use builds.apache.org, the apache > jenkins > > service. I'd like to use it to build weex binary daily and run our > > integration test. > > Weex's integration test require emulator which is very sensitive to > > environment. Currently it's not stable with travis. I hope > builds.apache.org > > can help this. > > > > According to wiki > https://cwiki.apache.org/confluence/display/INFRA/Jenkins, > > should I ask here or in general@incubator? > > > > -- > > Best Regards! > > > > sospartan > > https://weex-project.io > > > > > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
Use builds.apache.org service to build weex
Dear mentors, May I request the permission to use builds.apache.org, the apache jenkins service. I'd like to use it to build weex binary daily and run our integration test. Weex's integration test require emulator which is very sensitive to environment. Currently it's not stable with travis. I hope builds.apache.org can help this. According to wiki https://cwiki.apache.org/confluence/display/INFRA/Jenkins, should I ask here or in general@incubator? -- Best Regards! sospartan https://weex-project.io
Re: Proposal of Flatten view for Weex Android
This will be great to android performance. Besides these algorithms you mentioned, I think another big issue is decouple 'view' to component. We always think there will be a 'view' correspond with a component/node, and implementations are depend on that all over the place. See view-related methods in 'WXComponent', these need tons of work. And this will be a big change to our core architecture. But I like this idea after all, this will be huge improvement in most common scenes. On Wed, Apr 19, 2017 at 5:46 PM, 申远 <shenyua...@gmail.com> wrote: > The figure in the previous in case image download error. > > 在 2017年4月19日，17:26，申远 <shenyua...@gmail.com> 写道： > > As it is known to all that the view hierarchy in android should be reduce > as much as possible. The deeper the view hierarchy is, the worse the > android app performance . But the front-end engineer is often unaware of > the view hierarchy in weex until he/she asked android developer for help. > > I'd like to propose a mechanism for solving the above problem. > > The main problem of deep view hierarchy is that the implementation of view > is expensive and costs lost of CPU/Memory. The cost of a view is basically > linear to the length of view hierarchy. It is also unnecessary to create > view for some components, like and as they mostly draw > nothing but the objects Weex framework provides. There is no reason we > waste limited mobile resource to create view in such scenario. > > Suppose the following component structure is given, the view hierarchy > will be the same to the component hierarchy, where there is at least 10 > views(if there is no children in slider and no wrapper view for slider) and > the height of the tree is 5. > <屏幕快照 2017-04-19 16.59.09.png> > With Flatten mechanism enable, the view hierarchy will looks like below > with 2 views and the height of view tree is 3. Note, only rounded-rect is > marked as view, oval will be marked as a custom drawCommand. > <屏幕快照 2017-04-19 17.08.29.png> > > The above solution is faced with following issues. > 1. A deterministic algorithm is needed for telling whether a component > node will be transformed to view or drawCommand. > 2. "Promote to view" and "Downgrade to drawCommand" mechanisms are needed. > As one may add a gesture to Div D, in which case it is not a drawCommand > anymore and should be promoted to view. Also, one may remove gesture from a > view, in which case it should be downgrade to drawCommand. > 3. As the flatten mechanism is seamless to front-end developer and may > contains potential bugs, a "flatten mechanism enabled" flag should be put > in WxInstance and set to false default. I'd like to think flatten mechanism > as an experimental performance feature not a default behavior. > 4. The detail of deterministic algorithm and "Promote to view" and > "Downgrade to drawCommand" mechanisms is not clear yet. I just hope the big > picture is right, there may be flaws in the Flatten view solution as all > other experimental features are. > > I'd like to hear advice from other android/weex developer. > -- > > > Best regards, > > York Shen > > > -- sospartan Phone:13588488290 HangZhou
[jira] [Commented] (WEEX-19) Weex(iOS)，If want to let the frame adjust content's height, you need set frame(0, 0, width, NAN), but it sometime will crash
[
https://issues.apache.org/jira/browse/WEEX-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15973986#comment-15973986
]
sospartan commented on WEEX-19:
---
Has any updates on this?
ping [~cxfeng]
> Weex(iOS)，If want to let the frame adjust content's height, you need set
> frame(0, 0, width, NAN), but it sometime will crash
>
>
> Key: WEEX-19
> URL: https://issues.apache.org/jira/browse/WEEX-19
> Project: Weex
> Issue Type: Bug
> Environment: iOS
>Reporter: yuedong
>
> - (void)setFrame:(CGRect)frame
> {
> if (!CGRectEqualToRect(frame, _frame)) {
> _frame = frame;
> WXPerformBlockOnMainThread(^{
> if (_rootView) {
> _rootView.frame = frame;
> WXPerformBlockOnComponentThread(^{
> [self.componentManager rootViewFrameDidChange:frame];
> });
> }
> });
> }
> }
> if the _rootView is not nil, the frame(0, 0, width, NAN) will direct set to
> _rootView, then will crash.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (WEEX-26) List feature of v0.12 release
[ https://issues.apache.org/jira/browse/WEEX-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-26. --- Resolution: Fixed > List feature of v0.12 release > - > > Key: WEEX-26 > URL: https://issues.apache.org/jira/browse/WEEX-26 > Project: Weex > Issue Type: Task > Reporter: sospartan > > I'll use this issue to draft our release note. > Because most of our features were discussed in dev mail list, I'll pick some > major change from it. Hope we can simply link to related JIRA issue next time. > This release note will save to release page in our > website(http://weex.apache.org/releasenote.html). > v0.12 release note(draft) > > - C++ timer by lycool > Discussed in > https://lists.apache.org/thread.html/567c9b19d68ccf3e0d24c1467298ebcd4316ffa524c557a34c6c087f@%3Cdev.weex.apache.org%3E > relate pull > requests:[apache/incubator-weex/pull/228|https://github.com/apache/incubator-weex/pull/228], > > [apache/incubator-weex/pull/232|https://github.com/apache/incubator-weex/pull/232], > > [apache/incubator-weex/pull/221|https://github.com/apache/incubator-weex/pull/221] > - Add scroller/list scroll event in html5 render > android already have this feature in v0.11 > https://github.com/apache/incubator-weex/commit/f50fba8647c8bb6ac522b1a4569a2a2269da1953 > - Enhance accessibility, new `aria-label` & `role` support > [apache/incubator-weex/pull/149|https://github.com/apache/incubator-weex/pull/149] > - Native input/textarea enhancement by kfeagle & misakuo > support `number` data type; support soft keyboard event > - Picker module enhancement > More picker options to customize picker dialog style(background color etc.). > Related pull requests: > [apache/incubator-weex/pull/234|https://github.com/apache/incubator-weex/pull/234], > > [apache/incubator-weex/pull/233|https://github.com/apache/incubator-weex/pull/233] > - Android DOM module refactor > Seperate module code by action, increasing the maintainability. > [apache/incubator-weex/pull/104|https://github.com/apache/incubator-weex/pull/104] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: commits@
Agreed. I used to think these mails are fixed into dev@ On Tue, Apr 18, 2017 at 5:56 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > Gang, > I would like to propose that the GitHub "pull request" and "issue" mails > are directed to the commits@ list, rather than the dev@ list. > > Due to the RTC these mail is dominating the dev@ list and it is not easy > to > get an overview of what is actually being discussed in the community, and > any newcomer is likely to ignore it all, as the volume is frankly too high. > > WDYAT? > > Cheers > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- Best Regards! -- sospartan https://weex-project.io
[GitHub] incubator-weex pull request #258: * [test] change CI emulator sdk version
Github user sospartan closed the pull request at: https://github.com/apache/incubator-weex/pull/258 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[VOTE] Release of Apache Weex (incubating) 0.12.0-RC1
Hi Weex PPMC, I'm calling this vote to release Apache Weex 0.12.0-RC1. The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex. git;a=shortlog;h=refs/tags/0.12.0-rc1 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex. git;a=commit;h=9ac0c82443e65b1c9d8a2714fea6b9a5b8af9907 The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC1/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards! -- sospartan https://weex-project.io
Re: [VOTE] Release of Apache Weex (incubating) 0.12.0-RC0
My pleasure to help that.
I've make some changes to include test code and xml file
https://github.com/apache/incubator-weex/commit/951f65492f2b37cd90bbac9fd0c30ba5866cc189
And I create a script under 'scripts' folder, you can run
'./scripts/rat-scan.sh' to validate our src-header, the exclude rule is in
‘scripts/rat-ant-build.xml'.
I'll call another vote (for RC1) after I fix the 'NOTICE' file with
dependencies.
On Sat, Apr 15, 2017 at 9:30 AM, Niclas Hedhman <nic...@hedhman.org> wrote:
> Ok, thanks for taking time to answer my concerns. I withdraw the veto (the
> GPL concern).
> I recommend cutting a new release with the changes made, but will not block
> if you decide to push this release out anyway. Repacking should be quick
> and automatic...
>
> Cheers
>
> On Sat, Apr 15, 2017 at 9:03 AM, sospartan <sospar...@gmail.com> wrote:
>
> > These weex-* project is removable, theoretically speaking. We put these
> in
> > dependency for building javascript library more
> > convenient to use. It's kind of like a all-in-one javascript template
> > framework.
> > If you suggest moving these project to weex incubating project too, I
> think
> > we can discuss that, more things need to be settle. But for the next
> > release I'll suggest keep current way.
> >
> > The 'animationjs' we use from here https://www.npmjs.com/package/
> > animationjs
> >
> > flow-types; I mean these file can be generated by 'flow-type' tool, were
> > not manual code by us. For saving the time build it, we put it in code
> repo
> > in advance.
> > @Danz can we remove these files? Put it in .gitignore then you can keep
> use
> > these file in you local environment.
> >
> >
> >
> > On Fri, Apr 14, 2017 at 4:54 PM, Niclas Hedhman <nic...@hedhman.org>
> > wrote:
> >
> > > Well, the weexteam projects are listed as direct dependencies...
> > >
> > > "dependencies": {
> > > "animationjs": "^0.1.5",
> > > "core-js": "^2.4.0",
> > > "cubicbezier": "^0.1.1",
> > > "envd": "^0.1.1",
> > > "httpurl": "^0.1.1",
> > > "lazyimg": "^0.1.5",
> > > "modals": "^0.1.6",
> > > "query-string": "^4.2.3",
> > > "scroll-to": "0.0.2",
> > > "semver": "^5.1.0",
> > > "weex-components": "^0.2.0",
> > > "weex-picker": "^0.1.0",
> > > "weex-rax-framework": "0.1.7",
> > > "weex-styler":"0.1.8",
> > > "weex-vue-framework": "2.1.8-weex.1"
> > > },
> > >
> > > So, sorry if I don't see that as "not core parts of weex but some
> > > derivative projects."
> > >
> > > animationJs ; my apologies. What showed up in my google search was
> > > https://github.com/lathoub/AnimationJS.
> > >
> > > flow-types; Not sure what you mean. Please elaborate.
> > >
> > >
> > > On Fri, Apr 14, 2017 at 3:24 PM, sospartan <sospar...@gmail.com>
> wrote:
> > >
> > > > I'll check every dependency, includes npm dependencies in
> package.json/
> > > > dependencies import by android's gradle or dependencies imported by
> > > ios's
> > > > Pod, and update the NOTICE file.
> > > >
> > > > The weex-* project are side project maintain by weex or related
> teams.
> > > I'll
> > > > check licenses of these projects. These projects are not core parts
> of
> > > weex
> > > > but some derivative projects.
> > > >
> > > > I'll update other file type like XML/Shell scripts to have a proper
> src
> > > > header.
> > > >
> > > > Files under 'flow-typed/' are generated to help run lint against js
> > code.
> > > > It's not 'source code'. Including js file under android and ios SDK's
> > > > assets (android/sdk/assets,etc.)
> > > > @Niclas How do we deal these generate file?
> > > >
> > > > 'animationjs' is a library maintained by Danz He. I'm notice this
> > library
> > > > is MIT, not GPL.
> > > >
> > > >
> > > > On Fri, Apr 14, 2017 at 10:48 AM, Niclas Hedhman <nic...@hedhman.org
> >
> > > > wrote:
> > > >
> > >
[jira] [Reopened] (WEEX-21) Fix license problem
[ https://issues.apache.org/jira/browse/WEEX-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan reopened WEEX-21: --- As mentor point out in [VOTE] for release 0.12.0 RC, still lots of license problem need to be fix. > Fix license problem > --- > > Key: WEEX-21 > URL: https://issues.apache.org/jira/browse/WEEX-21 > Project: Weex > Issue Type: Task > Reporter: sospartan >Priority: Blocker > > I found our source code had some license issue. These should be fixed before > we have our first release. > I'll create subtask to describe it. > These task may involve a lot code modification, we should discuss before we > proceed any further. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: [VOTE] Release of Apache Weex (incubating) 0.12.0-RC0
Dear 余星, Pls use english to join discuss in this mail list. If you want feedback a problem, pls start a new thread. On Fri, Apr 14, 2017 at 11:08 AM, 余星 <644978...@qq.com> wrote: > 是在android 情况下的。 > https://segmentfault.com/q/101009063524 > apache 这个提问方式不熟悉，不知道怎么弄，在segmentfault也提了个问题 > > > > > -- 原始邮件 -- > 发件人: "sospartan"<sospar...@gmail.com>; > 发送时间: 2017年4月14日(星期五) 中午11:05 > 收件人: "dev"<dev@weex.incubator.apache.org>; > 主题: Re: [VOTE] Release of Apache Weex (incubating) 0.12.0-RC0 > > > > I've review all major source code and replace with apache src-header： > android .java file under 'android' > ios .m & .h file under 'ios' > html5 .js file under 'html5' > > I'll create JIRA issues to follow up these problems. > > On Fri, Apr 14, 2017 at 10:48 AM, Niclas Hedhman <nic...@hedhman.org> > wrote: > > > -1 ( VETO - dependency on GPL code) > > > > > > The NOTICE file contains notices about 5 dependencies, but the list of > > dependencies in package.json is much bigger, and I would assume that most > > of them are released under a license that requires attribution. > > > > Also, what is the relationship with the weex-* dependencies? Looking at > > weex-picker, it doesn't seem to be released with the same rigor as is > > expected from Apache projects, such as not stating the license terms and > > not respecting notices of dependencies. > > > > Why are these projects not part of Apache Weex (incubating)? > > > > Furthermore, it is not only .java files that are expected to have the > > license headers. We expect that in every source file that allows for > > comments. And it is missing all over the place, such as javascripts, XML > > files, build files, shell script files and so on. > > > > In the incubator-weex-1f7ed88/flow-typed/npm directory, which is some > type > > of "replacements" for other things. What is this, because some of those > > stubs are for GPL'd code, so I want to have a clear understanding of what > > is going on here... > > > > > > HOLD THE PRESSES; animationjs is listed in package.json as a dependency, > > and used in html5/render/browser/extend/components/slider/carrousel.js. > > This is GPL'd code and is viral, meaning that Weex is REQUIRED to be > GPL'd > > as well, which ASF don't allow. > > > > What disturbs me right now, because this is the second thing I picked at > > random. SO how many more unacceptable dependencies do we have in Weex, > > especially considering the transitive dependencies via the > weexteam/weex-* > > projects? > > > > > > So, this RC CAN NOT BE RELEASED, and I will block until a full review of > > all dependencies have been done (and if I am doing the review, it will > take > > months) > > > > > > Niclas > > > > > > On Thu, Apr 13, 2017 at 6:24 PM, sospartan <sospar...@apache.org> wrote: > > > > > Hi Weex PPMC, > > > > > > I'm calling this vote to release Apache Weex 0.12.0-RC0. > > > > > > The tag to be voted upon: > > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > > ;a=shortlog;h=refs/tags/0.12.0-rc0 > > > > > > The commit hash: > > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > > ;a=commit;h=1f7ed8880cf0938ba079b57aa2dc46ee484983d2 > > > > > > The source tarball can be found at: > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0 > > > -incubating/RC0/ > > > > > > The fingerprint of key to sign release artifacts: > > > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > > > > > Release artifacts are signed with the following key: > > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > > > > > Release note about this version: > > > https://issues.apache.org/jira/browse/WEEX-26 > > > > > > This vote will remain open for at least 72 hours. > > > Please vote on releasing this RC. > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove (and reason why) > > > > > > > > > -- > > > Best Regards! > > > -- > > > > > > sospartan > > > https://weex-project.io > > > > > > > > > > > -- > > Niclas Hedhman, Software Developer > > http://polygene.apache.org - New Energy for Java > > > > > > -- > sospartan > Phone:13588488290 > HangZhou > -- Best Regards! -- sospartan https://weex-project.io
Re: [VOTE] Release of Apache Weex (incubating) 0.12.0-RC0
I've review all major source code and replace with apache src-header： android .java file under 'android' ios .m & .h file under 'ios' html5 .js file under 'html5' I'll create JIRA issues to follow up these problems. On Fri, Apr 14, 2017 at 10:48 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > -1 ( VETO - dependency on GPL code) > > > The NOTICE file contains notices about 5 dependencies, but the list of > dependencies in package.json is much bigger, and I would assume that most > of them are released under a license that requires attribution. > > Also, what is the relationship with the weex-* dependencies? Looking at > weex-picker, it doesn't seem to be released with the same rigor as is > expected from Apache projects, such as not stating the license terms and > not respecting notices of dependencies. > > Why are these projects not part of Apache Weex (incubating)? > > Furthermore, it is not only .java files that are expected to have the > license headers. We expect that in every source file that allows for > comments. And it is missing all over the place, such as javascripts, XML > files, build files, shell script files and so on. > > In the incubator-weex-1f7ed88/flow-typed/npm directory, which is some type > of "replacements" for other things. What is this, because some of those > stubs are for GPL'd code, so I want to have a clear understanding of what > is going on here... > > > HOLD THE PRESSES; animationjs is listed in package.json as a dependency, > and used in html5/render/browser/extend/components/slider/carrousel.js. > This is GPL'd code and is viral, meaning that Weex is REQUIRED to be GPL'd > as well, which ASF don't allow. > > What disturbs me right now, because this is the second thing I picked at > random. SO how many more unacceptable dependencies do we have in Weex, > especially considering the transitive dependencies via the weexteam/weex-* > projects? > > > So, this RC CAN NOT BE RELEASED, and I will block until a full review of > all dependencies have been done (and if I am doing the review, it will take > months) > > > Niclas > > > On Thu, Apr 13, 2017 at 6:24 PM, sospartan <sospar...@apache.org> wrote: > > > Hi Weex PPMC, > > > > I'm calling this vote to release Apache Weex 0.12.0-RC0. > > > > The tag to be voted upon: > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > ;a=shortlog;h=refs/tags/0.12.0-rc0 > > > > The commit hash: > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > ;a=commit;h=1f7ed8880cf0938ba079b57aa2dc46ee484983d2 > > > > The source tarball can be found at: > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0 > > -incubating/RC0/ > > > > The fingerprint of key to sign release artifacts: > > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > > > Release artifacts are signed with the following key: > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > > > Release note about this version: > > https://issues.apache.org/jira/browse/WEEX-26 > > > > This vote will remain open for at least 72 hours. > > Please vote on releasing this RC. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > > > -- > > Best Regards! > > -- > > > > sospartan > > https://weex-project.io > > > > > > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
[GitHub] incubator-weex pull request #264: Dev
Github user sospartan closed the pull request at: https://github.com/apache/incubator-weex/pull/264 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-weex pull request #264: Dev
GitHub user sospartan opened a pull request: https://github.com/apache/incubator-weex/pull/264 Dev This PR will not merge. Just use CI to find android potential break changes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/incubator-weex dev Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/264.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #264 commit 47d4bc09f8d7166ae48082480948ba3e2d51bb17 Author: acton393 <zhangxing610...@gmail.com> Date: 2017-03-31T04:03:08Z * [ios] fix compiler complains commit aef6c58a4553cab0915655d7da4f1d61254be3ca Author: å 彦 <yuan...@users.noreply.github.com> Date: 2017-03-31T05:25:26Z * [jsfm] update rax framework to latest commit 65ed28eba98fe0a22ac403e1636115df97372384 Author: sospartan <sospar...@apache.org> Date: 2017-03-31T05:51:33Z * [test] support android get element by id commit d8c36f458711d209b79f04d83f8fa505a5b80125 Author: sospartan <sospar...@apache.org> Date: 2017-03-31T06:14:01Z * [test] update CI commit cf2d9b3c1b36078872c7f981129899b3cfaae1a4 Author: acton393 <zhangxing610...@gmail.com> Date: 2017-03-31T06:17:46Z Merge remote-tracking branch 'upstream/0.12-dev' into 0.12-dev commit a1c51cef203ca954be13e42f43f26c61d4a636ba Author: sospartan <sospar...@apache.org> Date: 2017-03-31T06:28:04Z * [test] fix CI commit b5ae07c7e410cb95acb413fa916a0613e307de8e Author: MrRaindrop <tekk...@gmail.com> Date: 2017-03-31T06:35:28Z + [html5] test for vue-render. commit 1375a6a13356f340aacb7eca0cef5e4f718cf107 Author: MrRaindrop <tekk...@gmail.com> Date: 2017-03-31T06:38:50Z * [html5] remove unused dependencies. commit ed80d3d150089964e2ed72e86f2adcb66336f02e Author: cxfeng <cxf...@apache.org> Date: 2017-03-31T06:45:44Z Merge branch '0.12-dev' of https://git-wip-us.apache.org/repos/asf/incubator-weex into 0.12-dev commit 82ff96d989504b932f744e421bb59cec2e6955f4 Author: MrRaindrop <tekk...@gmail.com> Date: 2017-03-31T07:13:15Z * [html5] fix dangerfile. commit 342fca2e21ef6265a7b88322f9b1d94124c9ce59 Author: sospartan <sospar...@apache.org> Date: 2017-03-31T07:20:37Z * [test] update test commit b74c338f7de2068567b118d74f2fb05e1c8a58e9 Author: sospartan <sospar...@apache.org> Date: 2017-03-31T07:27:37Z Merge branch '0.11-dev' into 0.12-dev commit 22819909797700cf68d9cded1f076e78d214c3e9 Author: xkli <569664...@qq.com> Date: 2017-03-31T08:15:45Z * [android] update support tablet commit 71bf802ff72a50736dc1e2630d051a6adb6e70f6 Author: xkli <569664...@qq.com> Date: 2017-03-31T08:16:22Z Merge branch '0.12-dev' into 0.12-dev-pad * 0.12-dev: (158 commits) * [test] update test * [ios] fix compiler complains * [html5] clear logs. * [html5] fix danger.js * [html5] update * [html5] true to ignore. * [html5] add flow ignore paths to danger.js * [html5] fix lint & add flow check for building vue-render. * [html5] add flow-type supported. * [html5] use warning tip. * [html5] fix modules. * [html5] fix path. * [html5] support @appear.native for compatiblitiy with weex native. * [html5] fix postcss config for vue-loader. * [html5] fix scroll direction of event.contentOffset.y * [html5] update * [html5] add comp-dom map for readme. * [html5] fix v-model binding for textarea. * [html5] hyphenate static style. * [html5] fix indicator's zIndex. ... commit 9c97d35e780e62c7ea678a983fa426ec914bf8d1 Author: MrRaindrop <tekk...@gmail.com> Date: 2017-03-31T08:29:47Z * [html5] fix soucemap with flow. commit 5312427202b1fffd034bbe41409fa10433c12dd3 Author: éé£ <cxf...@apache.org> Date: 2017-03-31T08:45:57Z Merge remote-tracking branch 'upstream/0.12-dev' into ios-feature-composite commit 9dd78d4a311d37c3f8ec322b822f14653275eb2c Author: acton393 <zhangxing610...@gmail.com> Date: 2017-03-31T09:20:19Z Merge remote-tracking branch 'upstream/0.12-dev' into 0.12-dev commit fed56d4bbf685c91e8321002d46b34fe367846c6 Author: MrRaindrop <tekk...@gmail.com> Date: 2017-03-31T09:31:37Z * [html5] update build & test config. commit 58fd3fe79a327ca84f694d54eaa69374ca0817af Author: sospartan <sospar...@apache.org> Date: 2017-03-31T09:41:58Z Merge branch '0.11-dev' of https://git-wip-us.apache.org/repos/asf/incubator-weex; branch 'dev-web-test' of http://github.com/MrRaindrop/incubator-weex into 0.11-dev This closes #202 commit 92cf074449bfad0dea3ce3ecee2be89218444f08 Author: Yun Dong <yundong...@gmail.com> Date: 2017-03-31T09:43:39Z * [site
[VOTE] Release of Apache Weex (incubating) 0.12.0-RC0
Hi Weex PPMC, I'm calling this vote to release Apache Weex 0.12.0-RC0. The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=shortlog;h=refs/tags/0.12.0-rc0 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=1f7ed8880cf0938ba079b57aa2dc46ee484983d2 The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC0/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards! -- sospartan https://weex-project.io
Re: Forward to our first release (0.12)
Never mind, I do have the permission to create directory. On Thu, Apr 13, 2017 at 2:09 PM, sospartan <sospar...@gmail.com> wrote: > Hi Niclas, > > The 'https://dist.apache.org/repos/dist/dev/incubator/weex' folder is not > exist yet, should I ask infra to create one? > > On Tue, Apr 11, 2017 at 12:06 PM, Niclas Hedhman <nic...@hedhman.org> > wrote: > >> The "Release Early, Release Often" is a great slogan to capture the >> concept >> that putting something in people's hands will spur further interest and >> grow the contributor base, as users want to fix problems that they may >> encounter. The more frequent the releases, the more confidence users get >> that fixes will reach them via the official channel, which encourages >> contributing back. >> >> Niclas >> >> On Tue, Apr 11, 2017 at 11:47 AM, sospartan <sospar...@apache.org> wrote: >> >> > Hi all, >> > Let plan our first apache release. Since 0.11 still have some license >> > problem, I'll suggest we skip that and choice 0.12 as our first version. >> > >> > I'd like hear from your guys about this. >> > >> > I'm volunteer to take 'release manager' for this version, and I'll >> figure >> > out how to release in apacheway. >> > >> > "Release Early, Release Often" , as mentor Niclas told me, hope we would >> > have our first release at the end of this month. >> > >> > >> > -- >> > Best Regards! >> > -- >> > >> > sospartan >> > https://weex-project.io >> > >> >> >> >> -- >> Niclas Hedhman, Software Developer >> http://polygene.apache.org - New Energy for Java >> > > > > -- > sospartan > Phone:13588488290 > HangZhou > -- sospartan Phone:13588488290 HangZhou
Re: Forward to our first release (0.12)
Hi Niclas, The 'https://dist.apache.org/repos/dist/dev/incubator/weex' folder is not exist yet, should I ask infra to create one? On Tue, Apr 11, 2017 at 12:06 PM, Niclas Hedhman <nic...@hedhman.org> wrote: > The "Release Early, Release Often" is a great slogan to capture the concept > that putting something in people's hands will spur further interest and > grow the contributor base, as users want to fix problems that they may > encounter. The more frequent the releases, the more confidence users get > that fixes will reach them via the official channel, which encourages > contributing back. > > Niclas > > On Tue, Apr 11, 2017 at 11:47 AM, sospartan <sospar...@apache.org> wrote: > > > Hi all, > > Let plan our first apache release. Since 0.11 still have some license > > problem, I'll suggest we skip that and choice 0.12 as our first version. > > > > I'd like hear from your guys about this. > > > > I'm volunteer to take 'release manager' for this version, and I'll figure > > out how to release in apacheway. > > > > "Release Early, Release Often" , as mentor Niclas told me, hope we would > > have our first release at the end of this month. > > > > > > -- > > Best Regards! > > -- > > > > sospartan > > https://weex-project.io > > > > > > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
[GitHub] incubator-weex issue #195: fix method onActivityResult bug,resultCode is err...
Github user sospartan commented on the issue: https://github.com/apache/incubator-weex/pull/195 pls create PR based on same branch. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-weex pull request #258: * [test] change CI emulator sdk version
GitHub user sospartan opened a pull request: https://github.com/apache/incubator-weex/pull/258 * [test] change CI emulator sdk version Test CI You can merge this pull request into a Git repository by running: $ git pull https://github.com/sospartan/incubator-weex 0.12.0-test-android-emulator Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/258.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #258 commit 2c4d66954957aa56560d495f2ae48af847b850ab Author: sospartan <sospar...@apache.org> Date: 2017-04-12T08:42:13Z * [test] change CI emulator sdk version --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-weex pull request #254: 0.12 dev test
GitHub user sospartan opened a pull request: https://github.com/apache/incubator-weex/pull/254 0.12 dev test test CI You can merge this pull request into a Git repository by running: $ git pull https://github.com/sospartan/incubator-weex 0.12-dev-test Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-weex/pull/254.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #254 commit 24e8ba07a18fbaa457e45137806fa437f2993ca9 Author: sospartan <sospar...@apache.org> Date: 2017-04-12T07:34:58Z * [test] update elem by id testcase commit 64b08576b6e916dcc8f4c87d5917f8073fc4d38e Author: sospartan <sospar...@apache.org> Date: 2017-04-12T07:35:05Z Merge branch '0.12-dev' of https://git-wip-us.apache.org/repos/asf/incubator-weex into 0.12-dev --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Skip testcases
Hi, I've update test script by https://github.com/apache/incubator-weex/commit/953c6071b4f21c25f9649aa32d026ab6ae6bd0d9 Please notice, now we can skip testcase for specific platform, by add '@ignore-[platform' to testcase name. Like I did in that commit https://github.com/apache/incubator-weex/commit/953c6071b4f21c25f9649aa32d026ab6ae6bd0d9#diff-00680fad5e6b534b2e7be1162e49f8eaL35 Testcase name include '@ignore-android'/'@ignore-ios'/'@ignore-web' will be skipped when 'run.sh' executing. -- Best Regards! -- sospartan https://weex-project.io
[jira] [Updated] (WEEX-26) List feature of v0.12 release
[ https://issues.apache.org/jira/browse/WEEX-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan updated WEEX-26: -- Description: I'll use this issue to draft our release note. Because most of our features were discussed in dev mail list, I'll pick some major change from it. Hope we can simply link to related JIRA issue next time. This release note will save to release page in our website(http://weex.apache.org/releasenote.html). v0.12 release note(draft) - C++ timer by lycool Discussed in https://lists.apache.org/thread.html/567c9b19d68ccf3e0d24c1467298ebcd4316ffa524c557a34c6c087f@%3Cdev.weex.apache.org%3E relate pull requests:[apache/incubator-weex/pull/228|https://github.com/apache/incubator-weex/pull/228], [apache/incubator-weex/pull/232|https://github.com/apache/incubator-weex/pull/232], [apache/incubator-weex/pull/221|https://github.com/apache/incubator-weex/pull/221] - Add scroller/list scroll event in html5 render android already have this feature in v0.11 https://github.com/apache/incubator-weex/commit/f50fba8647c8bb6ac522b1a4569a2a2269da1953 - Enhance accessibility, new `aria-label` & `role` support [apache/incubator-weex/pull/149|https://github.com/apache/incubator-weex/pull/149] - Native input/textarea enhancement by kfeagle & misakuo support `number` data type; support soft keyboard event - Picker module enhancement More picker options to customize picker dialog style(background color etc.). Related pull requests: [apache/incubator-weex/pull/234|https://github.com/apache/incubator-weex/pull/234], [apache/incubator-weex/pull/233|https://github.com/apache/incubator-weex/pull/233] - Android DOM module refactor Seperate module code by action, increasing the maintainability. [apache/incubator-weex/pull/104|https://github.com/apache/incubator-weex/pull/104] was: I'll use this issue to draft our release note. Because most of our features were discussed in dev mail list, I'll pick some major change from it. Hope we can simply link to related JIRA issue next time. This release note will save to release page in our website(http://weex.apache.org/releasenote.html). v0.12 release note(draft) - C++ timer by lycool Discussed in https://lists.apache.org/thread.html/567c9b19d68ccf3e0d24c1467298ebcd4316ffa524c557a34c6c087f@%3Cdev.weex.apache.org%3E relate pull requests:[apache/incubator-weex/pull/228|https://github.com/apache/incubator-weex/pull/228], [apache/incubator-weex/pull/232|https://github.com/apache/incubator-weex/pull/232], [apache/incubator-weex/pull/221|https://github.com/apache/incubator-weex/pull/221] - Add scroller/list scroll event in html5 render android already have this feature in v0.11 https://github.com/apache/incubator-weex/commit/f50fba8647c8bb6ac522b1a4569a2a2269da1953 - Enhance accessibility, new `aria-label` & `role` support [apache/incubator-weex/pull/149|https://github.com/apache/incubator-weex/pull/149] - Native input/textarea enhancement by kfeagle & misakuo support `number` data type; support soft keyboard event - Picker module enhancement More picker options to customize picker dialog style. Related pull requests: [apache/incubator-weex/pull/234|https://github.com/apache/incubator-weex/pull/234], [apache/incubator-weex/pull/233|https://github.com/apache/incubator-weex/pull/233] > List feature of v0.12 release > - > > Key: WEEX-26 > URL: https://issues.apache.org/jira/browse/WEEX-26 > Project: Weex > Issue Type: Task >Reporter: sospartan > > I'll use this issue to draft our release note. > Because most of our features were discussed in dev mail list, I'll pick some > major change from it. Hope we can simply link to related JIRA issue next time. > This release note will save to release page in our > website(http://weex.apache.org/releasenote.html). > v0.12 release note(draft) > > - C++ timer by lycool > Discussed in > https://lists.apache.org/thread.html/567c9b19d68ccf3e0d24c1467298ebcd4316ffa524c557a34c6c087f@%3Cdev.weex.apache.org%3E > relate pull > requests:[apache/incubator-weex/pull/228|https://github.com/apache/incubator-weex/pull/228], > > [apache/incubator-weex/pull/232|https://github.com/apache/incubator-weex/pull/232], > > [apache/incubator-weex/pull/221|https://github.com/apache/incubator-weex/pull/221] > - Add scroller/list scroll event in html5 render > android already have this feature in v0.11 > https://github.com/apache/incubator-weex/commit/f50fba8647c8bb6ac522b1a4569a2a2269da1953 > - Enhance accessibility, new `aria-label` & `role` support > [apache/incubator-weex/pull/149|https://github.com/apache/incubator-weex/pull/149] &
[GitHub] incubator-weex pull request #232: replace Java WxTimerModule with C++ setTim...
Github user sospartan commented on a diff in the pull request:
https://github.com/apache/incubator-weex/pull/232#discussion_r110834606
--- Diff:
android/sdk/src/main/java/com/taobao/weex/bridge/WXBridgeManager.java ---
@@ -1069,7 +1072,10 @@ public void invokeExecJS(String instanceId, String
namespace, String function,
.append("function:").append(function);
if(logTaskDetail)
mLodBuilder.append("
tasks:").append(WXJsonUtils.fromObjectToJSONString(args));
- WXLogUtils.d(mLodBuilder.substring(0));
+
+ //WXLogUtils.d(mLodBuilder.substring(0));
--- End diff --
Just remove it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[jira] [Created] (WEEX-26) List feature of v0.12 release
sospartan created WEEX-26: - Summary: List feature of v0.12 release Key: WEEX-26 URL: https://issues.apache.org/jira/browse/WEEX-26 Project: Weex Issue Type: Task Reporter: sospartan I'll use this issue to draft our release note. Because most of our features were discussed in dev mail list, I'll pick some major change from it. Hope we can simply link to related JIRA issue next time. This release note will save to release page in our website(http://weex.apache.org/releasenote.html). v0.12 release note(draft) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Forward to our first release (0.12)
Hi all, Let plan our first apache release. Since 0.11 still have some license problem, I'll suggest we skip that and choice 0.12 as our first version. I'd like hear from your guys about this. I'm volunteer to take 'release manager' for this version, and I'll figure out how to release in apacheway. "Release Early, Release Often" , as mentor Niclas told me, hope we would have our first release at the end of this month. -- Best Regards! -- sospartan https://weex-project.io
[jira] [Resolved] (WEEX-21) Fix license problem
[ https://issues.apache.org/jira/browse/WEEX-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-21. --- Resolution: Fixed > Fix license problem > --- > > Key: WEEX-21 > URL: https://issues.apache.org/jira/browse/WEEX-21 > Project: Weex > Issue Type: Task > Reporter: sospartan >Priority: Blocker > > I found our source code had some license issue. These should be fixed before > we have our first release. > I'll create subtask to describe it. > These task may involve a lot code modification, we should discuss before we > proceed any further. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (WEEX-24) NOTICE file need update
[ https://issues.apache.org/jira/browse/WEEX-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-24. --- Resolution: Fixed > NOTICE file need update > --- > > Key: WEEX-24 > URL: https://issues.apache.org/jira/browse/WEEX-24 > Project: Weex > Issue Type: Sub-task > Reporter: sospartan > > This single file modification should not be big problem. > Just remove old alibaba notice and add apache required. > http://www.apache.org/dev/licensing-howto.html#mod-notice -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: How to implement post request in Native Android with weex-hackernews example
hi,
axios is a 'Promise based HTTP client for the browser and node.js', you can
not use it in weex native. Weex provide stream module do the same thing.
See more here http://weex.apache.org/references/modules/stream.html
On Mon, Apr 10, 2017 at 7:48 PM, 友夏 <840590...@qq.com> wrote:
> Hi,
> The following code can be run in browser, but has no responce when i
> packaged it in apk with android mobile phone.
> Does axios not support Native Android ?
>
> Thanks
>
> youxia
>
>
> import axios from 'axios';
> var querystring = require('querystring');
>
> ...
>
> var this_page = this;
> var params = {username:'username1'};
> var paramsStr = querystring.stringify(params)
>
> axios.post('https://www.aganinfo.com/ag/dazhai/posttest.do',
> paramsStr
> )
> .then(function (response) {
> this_page.result = "OK";
> })
> .catch(function (response) {
> this_page.result = "ERR";
> });
--
Best Regards!
--
sospartan
https://weex-project.io
[jira] [Resolved] (WEEX-23) iOS src-header
[ https://issues.apache.org/jira/browse/WEEX-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-23. --- Resolution: Fixed > iOS src-header > --- > > Key: WEEX-23 > URL: https://issues.apache.org/jira/browse/WEEX-23 > Project: Weex > Issue Type: Sub-task > Reporter: sospartan > > iOS src-header contains a (alibaba)copyright notice and the license need > modify too according to http://www.apache.org/legal/src-headers.html#headers -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (WEEX-21) Fix license problem
[ https://issues.apache.org/jira/browse/WEEX-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan reopened WEEX-21: --- NOTICE file still need update > Fix license problem > --- > > Key: WEEX-21 > URL: https://issues.apache.org/jira/browse/WEEX-21 > Project: Weex > Issue Type: Task > Reporter: sospartan >Priority: Blocker > > I found our source code had some license issue. These should be fixed before > we have our first release. > I'll create subtask to describe it. > These task may involve a lot code modification, we should discuss before we > proceed any further. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (WEEX-25) All js source code do not have any license header
[ https://issues.apache.org/jira/browse/WEEX-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-25. --- Resolution: Fixed > All js source code do not have any license header > - > > Key: WEEX-25 > URL: https://issues.apache.org/jira/browse/WEEX-25 > Project: Weex > Issue Type: Sub-task > Reporter: sospartan > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (WEEX-22) android src-header
[ https://issues.apache.org/jira/browse/WEEX-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-22. --- Resolution: Fixed > android src-header > --- > > Key: WEEX-22 > URL: https://issues.apache.org/jira/browse/WEEX-22 > Project: Weex > Issue Type: Sub-task > Reporter: sospartan > > android java file src-header is using a long version apache license, should > be changed to http://www.apache.org/legal/src-headers.html#headers said. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (WEEX-21) Fix license problem
[ https://issues.apache.org/jira/browse/WEEX-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sospartan resolved WEEX-21. --- Resolution: Fixed I've fixed these in https://github.com/apache/incubator-weex/commit/255e589bd9056f372df5f498937cecb84b99bcaa > Fix license problem > --- > > Key: WEEX-21 > URL: https://issues.apache.org/jira/browse/WEEX-21 > Project: Weex > Issue Type: Task > Reporter: sospartan >Priority: Blocker > > I found our source code had some license issue. These should be fixed before > we have our first release. > I'll create subtask to describe it. > These task may involve a lot code modification, we should discuss before we > proceed any further. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] incubator-weex pull request #143: * [android] slider improvement
Github user sospartan commented on a diff in the pull request:
https://github.com/apache/incubator-weex/pull/143#discussion_r107616417
--- Diff: test/scripts/components/slider-infinite.test.js ---
@@ -0,0 +1,38 @@
+'use strict';
+
+var _ = require('macaca-utils');
+var assert = require('chai').assert
+var wd = require('weex-wd')
+var path = require('path');
+var os = require('os');
+var util = require("../util.js");
+
+describe('slider infinite scroll', function () {
+ this.timeout(util.getTimeoutMills());
+ var driver = util.createDriver(wd);
+
+ before(function () {
+return util.init(driver)
+ .get('wxpage://' + util.getDeviceHost() +'/slider-infinite.js')
+
.waitForElementByXPath('//div/text[1]',util.getGETActionWaitTimeMills(),1000)
+ });
+
+ after(function () {
+ return util.quit(driver);
+ })
+
+
+ it('#1 waiting for auto play', () => {
+return driver
+.sleep(5000)
+.elementByXPath('//div/text')
+.text()
+.then((text)=>{
+var parts = text.split("-");
+assert.equal(parts[0], 1);
+assert.equal(parts[2] == 1, false);
--- End diff --
There is a [assert API](http://chaijs.com/api/assert/) 'notEqual' too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] incubator-weex issue #155: * [android] input & textarea improvement
Github user sospartan commented on the issue: https://github.com/apache/incubator-weex/pull/155 The code seems fine to me. But the event is called 'keyboardevent' literally? The '-event' look like unnecessary. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-weex pull request #234: * [android] single picker improvement
Github user sospartan commented on a diff in the pull request:
https://github.com/apache/incubator-weex/pull/234#discussion_r110518677
--- Diff:
android/sdk/src/main/java/com/taobao/weex/appfram/pickers/WXPickersModule.java
---
@@ -361,6 +402,98 @@ public void onClick(DialogInterface dialog, int which)
{
callback.invoke(ret);
}
})
-.show();
+.setCustomTitle(makeTitleView(mWXSDKInstance.getContext(),
options))
+.create();
+
+if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
+dialog.create();
--- End diff --
What's this about? Better have comments here.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
