You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 4, 2019. It is now read-only.
The textbox stuff could a quite a bit of mess to draw.js. I was thinking it would be a good idea for all the tools to be contained within their own files. To do this we would need to employ a compiler, such as cjsc or browserify, and while we are doing that could employ tool such as grunt to manage everything (run sanity checks, tests, minification etc). Does this sound like a good idea and do you have a preference for such a thing? I use gulp, browserify, less, eslint (and also jasmine and karma for testing.
The text was updated successfully, but these errors were encountered:
I see a lot of projects go down this route and requiring all these additional tools raises the barrier of entry..
While I'm +1 modularization I'm -1 increasing complexity so if we go this route it should be still super simple to modify the software without understanding additional underlying modules/application/build processes etc.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The textbox stuff could a quite a bit of mess to draw.js. I was thinking it would be a good idea for all the tools to be contained within their own files. To do this we would need to employ a compiler, such as cjsc or browserify, and while we are doing that could employ tool such as grunt to manage everything (run sanity checks, tests, minification etc). Does this sound like a good idea and do you have a preference for such a thing? I use gulp, browserify, less, eslint (and also jasmine and karma for testing.
The text was updated successfully, but these errors were encountered: