[
https://issues.apache.org/jira/browse/WEEX-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287236#comment-16287236
]
ASF GitHub Bot commented on WEEX-168:
-
Github user weex-bot commented on the issue:
[
https://issues.apache.org/jira/browse/WEEX-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287217#comment-16287217
]
ASF GitHub Bot commented on WEEX-158:
-
Github user doumafang closed the pull request at:
You can be “added” to mailing list by subscribing :D , see “How to Contribute”
in [1].
[1]
https://github.com/apache/incubator-weex-site/blob/master/source/contributing.md#join-in-discussions
Thanks.
Adam Feng
On 12 Dec 2017, 12:23 AM +0800, vczero , wrote:
> Hi,
> I want to
Hi,I want to use and develop weex. Please add me to email list. Thanks!
-- vczero
Hi,
I want to use and develop weex. Please add me to email list. Thanks!
-- vczero
Hi, all:
We are going to organise the third Weex Conf (first of Apache Weex) in Hangzhou
in mid-January, 2018.
Potential Content:
• 1 day conference
• 7-9 x 40 minute presentations
• Talks on: Apache way, contributions, performance, applications, best
practices, roadmap, etc.
Please share your
[
https://issues.apache.org/jira/browse/WEEX-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285687#comment-16285687
]
ASF GitHub Bot commented on WEEX-169:
-
Github user yuhun-alibaba closed the pull request at:
[
https://issues.apache.org/jira/browse/WEEX-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285658#comment-16285658
]
ASF GitHub Bot commented on WEEX-169:
-
Github user weex-bot commented on the issue:
[
https://issues.apache.org/jira/browse/WEEX-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285657#comment-16285657
]
ASF GitHub Bot commented on WEEX-169:
-
GitHub user yuhun-alibaba opened a pull request:
toretto created WEEX-169:
Summary: fix null pointer crash
Key: WEEX-169
URL: https://issues.apache.org/jira/browse/WEEX-169
Project: Weex
Issue Type: Bug
Reporter: toretto
I think we could take three steps to get the framework type of a js bundle.
1. Parse the URL params, use a special key to specify the framework type.
This will skip the string parsing and save time.
2. Parse the "use weex:vue" or "use weex:rax" in the code string.
3. Parse the // { "Framework":
[
https://issues.apache.org/jira/browse/WEEX-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285642#comment-16285642
]
Adam Feng commented on WEEX-168:
Any details or demos?
> [iOS] AnimationModule needsLayout may show
Is there any way to avoid string parsing, for example, get framework type from
returning value while executing the bundle?
Thanks.
Adam Feng
On 11 Dec 2017, 4:12 PM +0800, Hanks Zhang , wrote:
> The "framework type annotation" is a special syntax written in js bundle to
>
It looks good to me. // { “framework”: “Vue/Rax” } looks tricky, and we cannot
add license disclaimer before it.
One question, how do we handle the backward compatibility issue?
On 11 Dec 2017, at 4:12 PM, Hanks Zhang
> wrote:
The "framework type annotation" is a special syntax written in js bundle to
indicate which framework it is using, such as Vue and Rax. Refer to its
document [1] the annotation looks like:
// { "framework": "Vue" }
or
// { "framework": "Rax" }
It's comment with special format actually,
[
https://issues.apache.org/jira/browse/WEEX-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qz updated WEEX-168:
Summary: [iOS] AnimationModule needsLayout may show incorrect (was: [iOS]
Animation needsLayout may show incorrect)
> [iOS]
[
https://issues.apache.org/jira/browse/WEEX-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
qz updated WEEX-168:
Summary: [iOS] Animation needsLayout may show incorrect (was: Animation
needsLayout may show incorrect)
> [iOS] Animation
qz created WEEX-168:
---
Summary: Animation needsLayout may show incorrect
Key: WEEX-168
URL: https://issues.apache.org/jira/browse/WEEX-168
Project: Weex
Issue Type: Bug
Reporter: qz
18 matches
Mail list logo