npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

pixi-display

v1.1.1

Published

Pixi.js plugin, allows to change rendering order of containers without changing the scene graph.

Downloads

95

Readme

pixi-display

Allows to change rendering order of pixi-v4 containers without changing the scene graph

Compiled files are located in "bin" folder

Example

Please look at example

Some explanations

  1. create some DisplayGroup , each has a z-index
  2. assign them to some of displayObjects (as shared component)
  3. assign displayList to root container (as a component)
  4. Displaylist looks inside subtree and sorts all the displaygroups that appear there, also calculated the list of elements that appear inside every DisplayGroup
  5. all objects that don't have displayGroup are added in "displayChildren" list of first parent that has it a displayGroup.
  6. inside each DisplayGroup you can specify sorting algorithm, if it is needed. (sort by y-coord or something like that)
  7. DisplayList -> DisplayGroups -> containers -> DisplayChildrens

As a result, every object will have a DisplayFlag:

  1. AUTO_CHILDREN - its children can appear in other display groups, so we render only self _renderWebGL
  2. AUTO_CONTAINER - have mask or filters, renders whole subtree renderWebGL
  3. AUTO_OBJECT - no children. thus, renderWebGL will be called
  4. MANUAL_CONTAINER - Specified by user. Its a particle container. Call renderWebGL and dont even try to check childrens, for performance.

Pros

  1. compatible with other implementations: just assign each element its own DisplayGroup. All elements will be sorted
  2. optimized for cases when you already know that 1000 elements have the same z-index: just assign them the same DisplayGroup
  3. optimized for cases when you know that some displayObjects follow natural order of things (rendered just after parent)
  4. optimized for cases like "ParticleContainer", you can set special DisplayFlag to container that way displayList will consider it a "leaf" and dont check its children at all.

Cons

  1. Interaction is different, there might be bugs. Performance of processInteractive() can drop a bit.
  2. Non-renderable elements are not interactable. Elements with alpha=0 are interactable but their children are not.