Giter Club home page Giter Club logo

assets's People

Contributors

3datawill avatar arturitu avatar atarng-magicleap avatar cvan avatar dmarcos avatar donmccurdy avatar feiss avatar fernandojsg avatar giordyb avatar knochi avatar machenmusik avatar mkeblx avatar ngokevin avatar technobuddhist avatar zach-capalbo avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

assets's Issues

Specify licenses.

In each folder, we can have a LICENSE file that lists the license for each asset.

Moving controller models to a separate repo

During the WebVR spec face to face meeting we discussed about a way for developers to easily find models for the different controllers in the market, hands and other kinds of basic virtual tools. We debated whether it should be a new platform API or just an official CDN that contains all the models. A-Frame hosts the assets in the gh-pages of this repo (https://github.com/aframevr/assets/tree/gh-pages/controllers). In order for any library to benefit from those we could:

  1. Move the models to a separate repo that it's not a-frame specific.
  2. Define conventions for file names, model part names, format, license...
  3. Decide where they should be hosted (gh-pages might fall short) and the url / domain schema to handle versioning.

What do you think? @feiss @fernandojsg @toji @ngokevin @TechnoBuddhist @machenmusik

Minimal set for CDN

Thanks to aframevr/aframe#5333 now in 1.5.0 it's possible to define the CDN that can thus be local, thus follow aframevr/aframe#5119 .

It's possible to clone this repository and point to the hosted version but this repository is huge (>500Mo). Briefly skimmed through it seems most of it (e.g .git itself, .blend model source, etc) aren't actually needed.

Few paths to consider, from easiest to more demanding

  1. updating README.md with required directories, e.g ./fonts and ./controllers I imagine, clarifying which files can removed to trim down to lowest size
  2. provide a "build" with the minimum, e.g a .zip generated from a script like tar -cvf minglb.tar fonts/ $( find controllers/ -type f -name "*.glb" )
  3. changing the structure to have a dedicated directory with only necessary content, e.g ./required/ with ./required/fonts and ./required/controllers and keeping there only used files, e.g .glb but not .blend
  4. splitting in 2 repositories

Optimize controller models

Could use an optimized, simplified set of controller models. Right now some quite heavy.

Current model stats:
-Oculus Touch: 0.88MB - 6.9k verts
-HTC Vive: 1.6MB - 8.7k verts
-Daydream: 0.10MB - 0.86k verts
-Gear VR: 0.03MB - 0.21k verts

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.