pissang opened a new pull request #15870:
URL: https://github.com/apache/echarts/pull/15870


   <!-- Please fill in the following information to help us review your PR more 
efficiently. -->
   
   ## Brief Information
   
   This pull request is in the type of:
   
   - [ ] bug fixing
   - [ ] new feature
   - [x] others
   
   ### What does this PR do?
   
   Before this change for each frame during progressive rendering, we will 
traverse all elements in the storage to update z, blend, states, etc. Which 
brings lots of unnecessary extra cost because we only have to update the new 
rendered elements.
   
   So this PR we add `eachRendered` method to traverse the new rendered 
elements in `view/Chart.ts`. And for the series that support progressive 
rendering will be responsible to manage which elements are rendered in this 
frame. When updating z, blend, states, we can simply use `eachRendered` instead 
of previously `view.group.traverse`.
   
   Besides this major change. We also drop the use of `IncrementalDisplayable`. 
It seems to be an overdesign. We only use it in `LargeSymbolDraw` and 
`LargeLineDraw`. For these two cases, we can merge the points to reduce the 
number of elements. The code is simpler, and we can have tooltip and event on 
the large mode with progressive rendering now:)
   
   Also we brings a new strategy to support series being separated in an 
individual `zlevel` automatically. Progressive rendered scatter and lines 
series will be used. And for a long time developers need to configure zlevel 
manually for lines with trail effect, now it can be done automatically.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to