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

@iiif/3d-manifesto-dev

v0.5.3

Published

IIIF Presentation API utility library for client and server with 3D extension

Downloads

25

Readme

manifesto-3D

Client and server utility library to support draft 3D extensions to to the IIIF Presentation API client and server utility library.

Forked from IIIF-Commons/manifesto.

Goal of implementing the Draft API under development by the IIIF 3D Technical Study Group.

Documentation

Manifesto-3D.js

Loading through package manager

npm install manifesto-3d.js --save

Demonstration Projects

Example manifests conforming to the Draft API .

Prototype Viewers rendering the example manifests.

ChangeLog

From start point of the version distributed from JulieWinchester/manifesto

To package.json version 4.3.0-draft3dapi.0.1.0

distributed from vincentmarchetti/manifesto#3dtsg-main there were these changes:

  1. This test is no longer useful for the Target of an Annotation:

     if ( typeof(target) === "string" ){
         // handle case where target is a Scene
     }

    Draft manifest 3_lights/direction_light_transform uses two ways of encoding the value of a target property for an Annotation: with a json string value of the IRI, or with an object with id property of the IRI for the Scene. To avoid exponential expansion of if-else code when combined with target property which can also be SpecificResource resources, the parsing code was changed so tha the value returned from getTarget() is always an object.

    Since the Target property will always be an object referencing a Scene, or a SpecificResource whose source property is a Scene, the code for handling either would be

     if (target.isSpecificResource){
         // handle a SpecificResource, with  selector property
         // and whose source property is the Scene
     }
     else{
         // handle a Scene directly
     }
        
  2. Annotation.getBody3D() is deprecated.

    The Annotation.getBody() from the Presentation 3 code has been extended to support the resources that can be included in a 3d Annotation body property. An important difference is that the getBody() function returns an array of objects, while the getBody3D() returns a single object. The deprecated function getBody3D() should be replaced with getBody()[0]

To package.json version 4.3.0-draft3dapi.0.2.0

  1. Fixed a bug that occurred in determining the 'source' property of a SpecificResource resource that is the "target" property of an Annotation. This bug escaped detection previously because in the 3D case this 'source' property has always been a Scene resource, and the value is not needed for visualization.

To package.json version 4.3.0-draft3dapi.0.3.0

  1. Added isSpecificResource and isAnnotationBody properties to the SpecificResource and AnnotationBody classes, in response to developer suggestion. (Slack, Apr 24 2024)

To package.json version 4.3.0-draft3dapi.0.4.0

  1. Implemented Perspective Camera properties in the Camera class.

To package.json version 4.3.0-draft3dapi.0.5.0

  1. Implement lookAt property of Camera class and of Light class.