Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
spider-monkey: a development environment for p5js sketches (amongst other things)
There are already plenty of tools available for p5js development; but so far none of them have met all of my needs. The p5 editor is focused on coding p5 and to my knowledge doesn't handle other functionality I'd like (e.g. SASS compilation). The Brackets editor has got a really nice live preview function; up until you hit F12 to initiate the browser developer tools and lose the connection...
To get a fully customisable development environment I decided to roll my own using some - now fairly standard - JS development tools: nodeJS/npm + Gulp + browserSync + Browserify + SASS + Jade. Assuming you can get nodeJS, npm and a couple of other global dependencies installed (if you're on Windoze I share your pain) you can pull the package definition; gulpfile and example source files from github.com/blindfish3/spider-monkey.
This project is as much about me getting a bit more up to speed with these tools; so don't necessarily represent good practice. I'd gladly welcome feedback, pull requests with improvements etc...