https://github.com/gadicc/meteor-famous
Temporary package for Famo.us Mixed Mode v0.5.0
https://github.com/gadicc/meteor-famous
Last synced: 11 months ago
JSON representation
Temporary package for Famo.us Mixed Mode v0.5.0
- Host: GitHub
- URL: https://github.com/gadicc/meteor-famous
- Owner: gadicc
- Created: 2015-05-24T13:32:25.000Z (about 11 years ago)
- Default Branch: master
- Last Pushed: 2015-08-09T07:01:03.000Z (almost 11 years ago)
- Last Synced: 2025-04-05T10:30:10.158Z (about 1 year ago)
- Language: JavaScript
- Size: 133 KB
- Stars: 4
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## gadicohen:famous
Temporary package for Famo.us Mixed Mode v0.5+
I won't be maintaining this package, it's just for people who want to get up
and running with the new mixed mode quickly (including glsl shaders).
I suggest to:
* Use Famous via [raix:famono](https://atmospherejs.com/raix/famono) once https://github.com/Famous/engine/issues/152 is fixed.
* Wait for new version of [mjn:famous](https://atmospherejs.com/mjn/famous)
* Use Famous via [cosmos:browserify](https://atmospherejs.com/cosmos/browserify) once https://github.com/Famous/engine/issues/152 is fixed.
* Use Famous via [rocket:module](https://atmospherejs.com/rocket/module) once https://github.com/Famous/engine/issues/152 is fixed.
## Development / Manual Upgrade
```bash
$ git clone https://github.com/gadicc/meteor-famous.git
$ cd meteor-famous
$ git submodule init
$ git submodule update
# must be global for now (famous < 0.6.2 requires glsify@1.6.0, not v2!)
$ sudo npm install -g glslify
```
Now you can symlink to that directory from any app's packages folder, and Meteor will use that release instead.
If you ever need a specific commit, just go into `meteor-famous/lib/famous` and
`git checkout `.
Note, when building the package, you'll get some errors about glsify not being
found. As long as glslify is installed globally, you can safely ignore that.
It's because of the `require('glsify')`, and the glsify compilation stuff
happens elsewhere in the tool chain. I should just have it not output an error
for glslify, didn't realize so many people were using this :)