[GitHub] incubator-weex-site issue #86: Update extend-android.md

[Hanks10100]

Github user Hanks10100 commented on the issue:

https://github.com/apache/incubator-weex-site/pull/86
  
Thanks for your contribution, please use Engish in the commit log. The 
"修改文案" may not be needed.


---

[GitHub] incubator-weex-site pull request #84: correct the href of the link named "co...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-weex-site/pull/84


---

[GitHub] incubator-weex-site pull request #87: Update who-is-using-weex style to supp...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-weex-site/pull/87


---

[GitHub] incubator-weex-site pull request #83: Update users.yml

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-weex-site/pull/83


---

[GitHub] incubator-weex-site pull request #87: Update who-is-using-weex style to supp...

[erha19]

GitHub user erha19 opened a pull request:

https://github.com/apache/incubator-weex-site/pull/87

Update who-is-using-weex style to support download link

Update who-is-using-weex style to support download link

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/erha19/incubator-weex-site master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-weex-site/pull/87.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 #87


commit 3209f4ce1f0777377572b20eac448d3e1123312b
Author: erha19 
Date:   2018-03-01T05:55:01Z

Update who-is-using-weex style to support download link




---

[GitHub] incubator-weex-site pull request #86: Update extend-android.md

[James-dai]

GitHub user James-dai opened a pull request:

https://github.com/apache/incubator-weex-site/pull/86

Update extend-android.md

修改文案

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/James-dai/incubator-weex-site patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-weex-site/pull/86.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 #86


commit 8cec6a9e9af4b6f7ae077491676eb05ad0c14a31
Author: James-dai 
Date:   2018-03-01T05:50:38Z

Update extend-android.md

修改文案




---

[GitHub] incubator-weex-site pull request #85: delete redundant English original

[AlbertXiao1994]

GitHub user AlbertXiao1994 opened a pull request:

https://github.com/apache/incubator-weex-site/pull/85

delete redundant English original

delete the original which is ignored in translation, and complete the 
corresponding words in Chinese

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/AlbertXiao1994/incubator-weex-site patch-3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-weex-site/pull/85.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 #85


commit 34e2dcee71460e2feaa1d4d603c589879c01ccb2
Author: Albert 
Date:   2018-03-01T03:31:10Z

delete redundant English original

delete the original which is ignored in translation, and complete the 
corresponding words in Chinese




---

[GitHub] incubator-weex-site pull request #83: Update users.yml

[tryao]

GitHub user tryao opened a pull request:

https://github.com/apache/incubator-weex-site/pull/83

Update users.yml

mod sinazc ios address

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/tryao/incubator-weex-site patch-3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-weex-site/pull/83.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 #83


commit d393378666ed7870393a0bd4c74ae45101871a2e
Author: 唐荣尧 <975872179@...>
Date:   2018-03-01T02:17:38Z

Update users.yml

mod sinazc ios address




---

[jira] [Commented] (WEEX-222) Sticky header in waterfall is not sticky

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on WEEX-222:
-

GitHub user gubaojian reopened a pull request:

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

[WEEX-222][android] Sticky header in waterfall is not sticky

[WEEX-222][android] Sticky header in waterfall is not sticky

http://dotwe.org/vue/8336befdb83e87f127a86f2cfb5a3324

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gubaojian/incubator-weex 
release-0.18-fix-waterfall-sticky

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-weex/pull/1041.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 #1041


commit 5ce93c7fdeaacf35c7adf5bdeaeacdc0bf474cc9
Author: jianbai.gbj 
Date:   2018-02-26T12:30:55Z

[WEEX-222][android] Sticky header in waterfall is not sticky




> Sticky header in waterfall is not sticky
> 
>
> Key: WEEX-222
> URL: https://issues.apache.org/jira/browse/WEEX-222
> Project: Weex
>  Issue Type: Bug
>  Components: Android
>Affects Versions: 0.18
> Environment: Playground App Android
>Reporter: biaomingzhong
>Assignee: zhengshihan
>Priority: Critical
>
> * Just upgrade weex_sdk to 0.18.0. But the sticky header is not sticky in 
> playground app.
>  * [DotWe link is official waterfall 
> example|http://dotwe.org/vue/7a9195643e9e8da352b0d879cdbe68c0]
>  * I have tried this waterfall example in Taobao app. Scan result has same 
> problem that the sticky header is not sticky.
>  * But I downgrade to SDK 0.17. It works.



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

[jira] [Commented] (WEEX-222) Sticky header in waterfall is not sticky

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on WEEX-222:
-

Github user gubaojian closed the pull request at:

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


> Sticky header in waterfall is not sticky
> 
>
> Key: WEEX-222
> URL: https://issues.apache.org/jira/browse/WEEX-222
> Project: Weex
>  Issue Type: Bug
>  Components: Android
>Affects Versions: 0.18
> Environment: Playground App Android
>Reporter: biaomingzhong
>Assignee: zhengshihan
>Priority: Critical
>
> * Just upgrade weex_sdk to 0.18.0. But the sticky header is not sticky in 
> playground app.
>  * [DotWe link is official waterfall 
> example|http://dotwe.org/vue/7a9195643e9e8da352b0d879cdbe68c0]
>  * I have tried this waterfall example in Taobao app. Scan result has same 
> problem that the sticky header is not sticky.
>  * But I downgrade to SDK 0.17. It works.



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

[GitHub] incubator-weex-site pull request #82: Add usage of breakpoint

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-weex-site/pull/82


---

[GitHub] incubator-weex-site pull request #82: Add usage of breakpoint

[erha19]

GitHub user erha19 opened a pull request:

https://github.com/apache/incubator-weex-site/pull/82

Add usage of breakpoint

Add usage of breakpoint

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/erha19/incubator-weex-site master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-weex-site/pull/82.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 #82


commit b798c3bfc2257afe4877f52c29e05e03868c67c6
Author: erha19 
Date:   2018-02-28T12:22:34Z

Add usage of breakpoint




---

[GitHub] incubator-weex-site pull request #81: Update toolkit document

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-weex-site/pull/81


---

[GitHub] incubator-weex-site pull request #81: Update toolkit document

[erha19]

GitHub user erha19 opened a pull request:

https://github.com/apache/incubator-weex-site/pull/81

Update toolkit document

Changes:
- Update toolkit document
- Update the title of weex-toolkit document on the menu

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/erha19/incubator-weex-site master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-weex-site/pull/81.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 #81


commit 6a25af33952c56afa9045168658b2e35f8d3774b
Author: erha19 
Date:   2018-02-28T11:58:45Z

Update toolkit document

commit 6a0db884b87a3b785a81168bd92ca4493f9d6ee6
Author: erha19 
Date:   2018-02-28T11:59:14Z

Update the title of weex-toolkit document




---

[jira] [Commented] (WEEX-226) WXModuleManager add new callback named onNewIntent()

[codefurture (JIRA)]

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

codefurture commented on WEEX-226:
--

great works, you commit an pull request, we will review the code and merge this 
commit

> WXModuleManager add new callback named onNewIntent()
> 
>
> Key: WEEX-226
> URL: https://issues.apache.org/jira/browse/WEEX-226
> Project: Weex
>  Issue Type: Improvement
>  Components: Android
>Affects Versions: 0.18
>Reporter: 华逢义
>Assignee: zhengshihan
>Priority: Major
> Attachments: image-2018-02-27-08-48-07-120.png, 
> image-2018-02-27-08-48-59-494.png, image-2018-02-27-08-49-36-808.png
>
>
> As android NFC need use onNewIntent() in Module as callback to get the 
> RFIDTag.We need add onNewIntent() in WXModuleManager to support NFC plugin 
> development
> !image-2018-02-27-08-47-13-700.png!
> !image-2018-02-27-08-48-07-120.png!
> !image-2018-02-27-08-48-59-494.png!
> !image-2018-02-27-08-49-36-808.png!



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

Re: Regarding plans to take weex global

[Adam Feng]

Hi Varun

Thanks for your plan. It’s exciting to see you contribute a strength to Weex . 
People like you are extraordinary needed to bring diversity into the project.

The plan is quite reasonable,  we have improved the documentation a little last 
year(adding more detail explanation and examples),  it’s a little bit difficult 
for us to write English documents since most of the contributors are Chinese. 
So it will be really helped if users can go through the English documents and 
report/fix issues for them. And the idea of  creating videos for basic training 
is good, let the community know if you have any problems about the materials.

I may add, too, that if a lot of vuejs developers are choosing between Weex and 
Nativescript,  how about writing an article to compare them from users’ 
viewpoint, just be neutral and let us know what can be improved, it will be 
better if we can compare more cross-platform frameworks such as React Native, 
flutter, etc.

Let’s go big with weex!

Thanks.
Adam Feng

On 28 Feb 2018, 3:51 PM +0800, Varun Sobti , 
wrote:
> Hello Everyone,
>
> I'm Varun Sobti, working as frontend lead with Paytm India.
>
> I’ve been exploring a lot about presence of weex and native script as these
> are the only 2 options available for vuejs. I figured out some problems
> that other engineers face, which stops them for using weex for production
> apps.
>
> I want to help expand it's reach globally and below points can be
> considered as the plan of action:
>
> 1. Fix documentation. Make it more acceptable.
> 2. Ease of initiating a new app.
> 3. Creating a strong community where some of us are readily available to
> help and unblock others in case of any issue.
> 4. Creating videos for basic training and How-n-Why.
>
> Please feel free to suggest any changes.
>
> There may be a lot of thing that are already in progress. Please do share
> details so that we all can be on the same page.
>
> I look forward to connecting with you all. Let’s go big with weex and make
> sure it reaches and appeals as many engineers as possible.
>
>
> Thanks,
> Varun

Re: Regarding plans to take weex global

[Varun Sobti]

Thanks Hanks.

I agree to all your points and it is really important to start with English
documentation changes.

Please let me know when we can have a quick call. It'll be helpful to
understand how I can start making changes to English documentation.

In parallel, we can also create a group on engineers among us, who are
willing to contribute and help resolve any queries in the community.
Thoughts?


Thanks,
Varun

On Wed, Feb 28, 2018 at 2:08 PM, Hanks Zhang  wrote:

> Awesome! Looking forward to your sharing! I also realized that Weex did not
> do well in the community, especially in the English world. It would be very
> helpful for worldwide developers to getting started with weex.
>
> I am also planning to write some articles to introduce Weex to the
> beginners. We really should share the development progress of Weex more
> frequently.
>
> Best Regards,
> Hanks
>
> 2018-02-28 15:51 GMT+08:00 Varun Sobti :
>
> > Hello Everyone,
> >
> > I'm Varun Sobti, working as frontend lead with Paytm India.
> >
> > I’ve been exploring a lot about presence of weex and native script as
> these
> > are the only 2 options available for vuejs. I figured out some problems
> > that other engineers face, which stops them for using weex for production
> > apps.
> >
> > I want to help expand it's reach globally and below points can be
> > considered as the plan of action:
> >
> > 1. Fix documentation. Make it more acceptable.
> > 2. Ease of initiating a new app.
> > 3. Creating a strong community where some of us are readily available to
> > help and unblock others in case of any issue.
> > 4. Creating videos for basic training and How-n-Why.
> >
> > Please feel free to suggest any changes.
> >
> > There may be a lot of thing that are already in progress. Please do share
> > details so that we all can be on the same page.
> >
> > I look forward to connecting with you all. Let’s go big with weex and
> make
> > sure it reaches and appeals as many engineers as possible.
> >
> >
> > Thanks,
> > Varun
> >
>

Re: Regarding plans to take weex global

[Hanks Zhang]

Awesome! Looking forward to your sharing! I also realized that Weex did not
do well in the community, especially in the English world. It would be very
helpful for worldwide developers to getting started with weex.

I am also planning to write some articles to introduce Weex to the
beginners. We really should share the development progress of Weex more
frequently.

Best Regards,
Hanks

2018-02-28 15:51 GMT+08:00 Varun Sobti :

> Hello Everyone,
>
> I'm Varun Sobti, working as frontend lead with Paytm India.
>
> I’ve been exploring a lot about presence of weex and native script as these
> are the only 2 options available for vuejs. I figured out some problems
> that other engineers face, which stops them for using weex for production
> apps.
>
> I want to help expand it's reach globally and below points can be
> considered as the plan of action:
>
> 1. Fix documentation. Make it more acceptable.
> 2. Ease of initiating a new app.
> 3. Creating a strong community where some of us are readily available to
> help and unblock others in case of any issue.
> 4. Creating videos for basic training and How-n-Why.
>
> Please feel free to suggest any changes.
>
> There may be a lot of thing that are already in progress. Please do share
> details so that we all can be on the same page.
>
> I look forward to connecting with you all. Let’s go big with weex and make
> sure it reaches and appeals as many engineers as possible.
>
>
> Thanks,
> Varun
>

Re: 回复： 【Discussion】 More enhanced about component

[Adam Feng]

Great proposal for weex-web communication!

Please be careful about the consistency between iOS and Android on web-native 
bridge, injecting global function may only be available on iOS.  So I suggest 
Tw93 and misakuo  have a more detailed discussion on the implementation before 
kicking off.




Thanks.
Adam Feng

On 28 Feb 2018, 2:09 PM +0800, 汤威 , wrote:
> @Hanks ZhangThank you very much for your advice. I also believe that use the 
> MessageEvent is more appropriate, I will modify the implementation.
>
>
> About the implementation of the Android platform, I'll give it a try. @misakuo
>
>
> -- 原始邮件 --
> 发件人: "Hanks Zhang";
> 发送时间: 2018年2月28日(星期三) 中午12:14
> 收件人: "dev";
>
> 主题: Re: 【Discussion】 More enhanced about  component
>
>
>
> +1. I think it could be very helpful to achieve the communication between
> weex pages and web pages.
>
> By the way, the exposed API should be consistent with web standards. Using
> "postMessage" and "addEventListener" is OK, but the "notify" event is
> specific by weex which is not standard. I think it's a good opportunity to
> amend it, use the MessageEvent is more appropriate. It was designed for
> cross-document messaging. https://www.w3.org/TR/webmessaging/#web-messaging
>
> 2018-02-28 12:03 GMT+08:00 misakuo :
>
> > It is a great idea to add two-way communication channel to web component, I
> > can help provide the implementation of the Android platform.
> > Render the html source is also a useful feature, it makes us easier to
> > achieve some complex typesetting like rich text.
> > very good proposal.
> >
> > 2018-02-28 11:37 GMT+08:00 汤威 :
> >
> > > Hi, I'm Tw93 (侑夕) from Fliggy, I'd like to discuss the enhancements about
> > > component, let it take over where we can't implement through weex.
> > >
> > >
> > > Target
> > >
> > >  is used to display web content that specified by src attribute in
> > > weex page,We also can use webview module to control WebView behavior such
> > > as goBack, goForward and reload.
> > >
> > > But it's not enough in most businesses，I think a more enhanced web
> > > component should have the following:
> > >
> > >
> > > Support to send messages from Weex to a html in component.
> > >
> > >
> > > Support to send messages from a html in component to Weex.
> > >
> > >
> > > Support to render html source.
> > >
> > >
> > > Previously, component was an island that only rendered a remote url, but
> > > enabled it to communicate through the context native to the webView. Then
> > > I'm going to describe the solution that I came up with.
> > >
> > >
> > > My solution
> > >
> > >
> > > Code
> > >
> > > Weex iOS:
> > >
> > > https://github.com/tw93/incubator-weex/blob/ios-
> > > feature-enhanced-web/ios/sdk/WeexSDK/Sources/Component/WXWebComponent.m
> > >
> > >
> > >
> > > Weex Vue Demo:
> > >
> > > http://dotwe.org/vue/f0c7d877fb6b0e9b661aa4f53a652793
> > >
> > >
> > > Demo Bundle JS
> > >
> > >
> > > Web End
> > >
> > >
> > >
> > >
> > > Demo && Theory
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Details
> > >
> > >
> > > Support to send messages from Weex to a html in component.
> > >
> > > Native：
> > >
> > > - (void)notifyWebview:(NSDictionary *) data { NSString *json =
> > > [WXUtility JSONString:data]; NSString *code = [NSString
> > > stringWithFormat:@"(function(){var evt=null;var data=%@;if(typeof
> > > CustomEvent==='function'){evt=new CustomEvent('notify',{detail:
> > > data})}else{evt=document.createEvent('CustomEvent');
> > > evt.initCustomEvent('notify',true,true,data)}document.
> > dispatchEvent(evt)}())",
> > > json]; [_jsContext evaluateScript:code]; }
> > >
> > > How to use：
> > >
> > > // Weex const webview = weex.requireModule('webview');
> > > webview.notifyWebview(this.$refs.webview, "message"); // Web
> > > document.addEventListener('notify',function(e){ console.log(e.detail)
> > > },false)
> > >
> > >
> > > Support to send messages from a html in component to Weex.
> > >
> > >
> > > Native：
> > >
> > > _jsContext[@"postMessage"] = ^(JSValue *data){ [weakSelf
> > fireEvent:@"notify"
> > > params:[data toDictionary]]; };
> > >
> > > How to use：
> > >
> > > // Weex  // Web
> > > window.postMessage(message, targetOrigin, false);
> > >
> > >
> > > Support to render html source.
> > >
> > >
> > > Native:
> > >
> > > [_webview loadHTMLString:_source baseURL:nil];
> > >
> > > How to use:
> > >
> > >  > >
> > > Welcome to put forward any suggestion about the solution or other
> > > requirements for the component.
> > >
> > > After that, I'm going to submit a pr. Thanks！

[jira] [Assigned] (WEEX-229) weex web weex-vue-render1.0.x text components value attribute not effective

[Hanks Zhang (JIRA)]

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

Hanks Zhang reassigned WEEX-229:


Assignee: Danz He  (was: Adam Feng)

> weex web weex-vue-render1.0.x text components value attribute not effective 
> 
>
> Key: WEEX-229
> URL: https://issues.apache.org/jira/browse/WEEX-229
> Project: Weex
>  Issue Type: Bug
>Reporter: fengwuxp
>Assignee: Danz He
>Priority: Major
>
> example
>  code :
>  ``
>  result:
> ` `
> use cdn js
>  
>  src="//h5.m.taobao.com/js/trip/weex-ui/weex-vue-render-next.min.js">
> devDependencies list:
> {{"vue": "^2.5.3", }}
> {{"vue-loader": "^12.2.2",}}
> {{ "vue-router": "^3.0.1", }}
> {{"vue-template-compiler": "^2.5.3", }}
> {{"webpack": "^3.8.1", }}
> {{"webpack-cli": "^2.0.9", }}
> {{"webpack-dev-server": "^3.0.0",}}
> {{ "weex-loader": "~0.5.3", }}
> {{"weex-ui": "^0.4.0", }}
> {{"weex-vue-framework": "^2.5.13-weex.5",}}
> {{ "weex-vue-loader": "~0.4.2",}}
> {{ "weex-vue-precompiler": "^0.1.17", }}
> {{"weex-vue-render": "^1.0.17",}}



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