[GitHub] incubator-weex pull request #97: remove unnecessary nested frameLayout in em...

GitHub user Rowandjj opened a pull request: https://github.com/apache/incubator-weex/pull/97 remove unnecessary nested frameLayout in embed @sospartan You can merge this pull request into a Git repository by running: $ git pull https://github.com/Rowandjj/incubator-weex

[GitHub] incubator-weex issue #81: * [jsfm] upgrade rax to 0.2.3

Github user fkysly commented on the issue: https://github.com/apache/incubator-weex/pull/81 This change has been included in the pr #96 . --- 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

[GitHub] incubator-weex pull request #96: * [jsfm] merge jsfm-feature-0.19

GitHub user fkysly opened a pull request: https://github.com/apache/incubator-weex/pull/96 * [jsfm] merge jsfm-feature-0.19 jsfm v0.19.14 revert rax to 0.1.0 update vue to 2.2.1-weex.1 You can merge this pull request into a Git repository by running: $ git pull

[GitHub] incubator-weex pull request #95: * [jsfm] merge jsfm-feature-0.19

Github user fkysly closed the pull request at: https://github.com/apache/incubator-weex/pull/95 --- 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

[GitHub] incubator-weex pull request #94: * [ios] bugfix incorrect code

Github user asfgit closed the pull request at: https://github.com/apache/incubator-weex/pull/94 --- 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

[GitHub] incubator-weex pull request #94: * [ios] bugfix incorrect code

GitHub user acton393 opened a pull request: https://github.com/apache/incubator-weex/pull/94 * [ios] bugfix incorrect code You can merge this pull request into a Git repository by running: $ git pull https://github.com/acton393/incubator-weex dev Alternatively you can review

[GitHub] incubator-weex pull request #86: * [doc] Update some examples.

Github user asfgit closed the pull request at: https://github.com/apache/incubator-weex/pull/86 --- 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

[GitHub] incubator-weex pull request #80: Fix some grammatical issues on the English ...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-weex/pull/80 --- 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

[GitHub] incubator-weex pull request #71: * [doc] Update GitHub link, change from ali...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-weex/pull/71 --- 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

Re: Workflow?

Everyone who contributes to Weex should be a committer, yes. We recommend that 2-3 patches is enough for new projects. And most projects have a "low barrier of entry". All contributions beyond simple typos and one/two-liner bug fixes, needs to have an Individual Contributor License Agreement

Re: Workflow?

You mean every body in at least our current develop team should/will have a 'committer' permission? I agree with you that CTR is ideal model when our project has 'enough' eyeballs and tests. But for now, I'm still worrying about the quality. Most of us, including me, have a really bad old habit:

Re: Support all top-level DOM APIs in Vue 2

Not me, this need some C++/C-guys to work this out. I don't speak C any longer. On Sun, Mar 12, 2017 at 7:10 PM, Adam Feng wrote: > Seems to be amazing. @sospartan do you have any plan to do this? Or > anyone volunteer? > > On 2017年3月11日 +0800 AM1:03, 大诗胸

Re: Support all top-level DOM APIs in Vue 2

Seems to be amazing. @sospartan do you have any plan to do this? Or anyone  volunteer? On 2017年3月11日 +0800 AM1:03, 大诗胸 , wrote: > The answer is yes. We can access java native object in ndk, and ndk can > access V8 javascript object. It's a lot of work to convert to each

Re: Workflow?

Here is the reason why we decided do RTC: We wanna make sure every modification is reviewed by another people. And avoid commit any feature without discuss with teammate. We use this to minimize the low-level bug. We do realize RTC will slow down the development，but we think it will be worth