[
https://issues.apache.org/jira/browse/WEEX-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009913#comment-16009913
]
ASF GitHub Bot commented on WEEX-27:
------------------------------------
GitHub user Rowandjj opened a pull request:
https://github.com/apache/incubator-weex/pull/343
+ [android] support prerender
introduction :
https://issues.apache.org/jira/browse/WEEX-27?jql=project%20%3D%20WEEX%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Major%20ORDER%20BY%20key%20DESC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Rowandjj/incubator-weex
android-feature-prerender-interface
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-weex/pull/343.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 #343
----
commit 140390719dc73a62a16f377f8c1498fa8f78b367
Author: Rowandjj <[email protected]>
Date: 2017-05-14T04:36:11Z
+ [android] init prerender
----
> Prerender
> ---------
>
> Key: WEEX-27
> URL: https://issues.apache.org/jira/browse/WEEX-27
> Project: Weex
> Issue Type: New Feature
> Environment: Android, iOS, (not Html5)
> Reporter: xingjiu
> Attachments: TB12RlEQFXXXXccXFXXXXXXXXXX.jpg
>
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> In order to impove the page open speed, we have intro many ways, such as
> js-bundle prefetch.
> Now we have a new idea of render the next page in background. When click the
> button to jump to the next page, just show it, no other js file execute cost
> needed.
> We call it prerender.
> First. Limition
> Prerender will benifit user experience of waiting time of new page load.
> It is like a tradition way, use extre space(memory) to reduce time cost.
> We need to protected our app`s memory cost, so just one page can be
> prerendered. This limit maybe removed later.
> Second. How we do?
> One way is to store the callNative commander in memory.
> We know weex use javascript engine to explain how the page will be render,
> then js will use callNative() to make native views created.
> Once we just store the callNative commander, not to execute it. When the page
> is truely show, do the commander executed.
> The attach image is the order of weex render steps currently.
> Finally.
> Our goal is to make weex page show quickly.
> We assure that using prerender, the page open in one second will reach 99.9+
> precent. And the global festive main page will works prefect in prerender
> mode.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
