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

lucy-compose

v0.1.1

Published

Agnostic scene composition tool.

Downloads

5

Readme

Lucy Compose Build Status

Part of lucidity project.

Agnostic scene composition tool

Compose complexe scenes by writing simple composition functions. The framework can be used to compose about anything (see tests for examples). This whole library is just a convenient way to load 'effects', call setup on them and render with support for live coding and async loading.

Asynchronous scene loading and setup uses promises and ensures that scenes down the graph hierarchy are entirely loaded before they are inserted in parent objects through the call to setup.

There is a set of composition helpers for THREE.js using lucy-compose: lucy-three.

First declare sources by specifying a folder.

const compose = require ( 'lucy-compose' )

const fx    = compose.load ( 'fx'         )
const scene = compose.load ( 'scene'      )
const trans = compose.load ( '../somelib/transition' )

Compose a view from a single scene.

// expects scene/cube.js or scene/cube/index.js to exist
scene ( 'cube' )

// same scene but with some additional options (these are passed right through
// to the scene's "setup" function).
scene
( 'cube'
, { distance: 5.0, extent: 1.0 }
)

Compose with postprocessing effect.

fx
( 'blur'
, { radius: 0.3 }
, scene ( 'cube' )
)

Transition between 'cube' and 'sphere' scenes using a 'fade' effect.

trans
( 'fade'
, { position: 0.3 }
, fx
  ( 'blur'
  , { radius: 0.8 }
  , scene ( 'cube' )
  )
, scene ( 'sphere' )
)

Scene API

In order to be composed, scenes should implement the following methods:

  • setup ( options [, sub scenes ] ) Should return a scene. Called once on scene composition. It is up to what makes most sense in the project to create a new scene on each setup or to use a singleton, keeping state stable on composition changes.

  • scene.render ( context [, target ] ) Render the scene, optionally targetting the provided target object. Called on each frame. The context is passed down the scene hierarchy and can be anything. Usually, this is an object containing globa state information (time, uniforms, etc).

Look at 'test/fixtures/scenes/bing' to get an idea of a simple Scene definition.

Installation

npm install lucy-compose --save

Tests

 npm test

Contributing

Please use 'jessy style'.

Add unit tests for any new or changed functionality.

Release History

  • 0.1.1 (2015-09-03) Moving THREE.js wrapper classes to lucy-three.
  • 0.1.0 (2015-09-03) Initial release