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
I love Jade because of how it takes away a lot of the HTML 'cruft' and I find Jade really easy to follow. I definitely see the analogy to coffeescript. I have looked at coffeescript several times. However for whatever reason I haven't had the same feelings for coffeescript. I "had to" pick one of the HTML templating tools and I happened to choose Jade but I haven't felt I had to use a tool like coffeescript. By keeping this in pure JS I feel it's maybe more accessible to a wider audience.
Long way of saying I guess I'm just not that familiar with coffescript.
Makes sense. I'll work on adding support for it, while keeping the system files in pure JS. We just have to add coffee-script as a dependency, and gulp-coffee to devdependencies. A little snippet, and maybe a linter, and users will be able to use coffeescript for their projects.
As far as I know I don't need to give permission - just open a pull request. That's how I have done it on other repos. Looking forward to checking it out!
Pushing to git@github.com:dstroot/skeleton.git
ERROR: Permission to dstroot/skeleton.git denied to dudo.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I'm only pushing my coffee branch, too... not master. I can pull fine... just can't seem to push.
Have you tried opening a pull request? Generally contributors don't push, the owner pulls. At least thats how it's worked on other repos I have contributed to. You open a pull request with the changes in your fork. I review them and pull them in.
Haha, no. I'm used to bitbucket, I guess. You just push a branch up, then submit the PR. I'll figure it out here soon... I've been playing a bit more with ReactJS lately. I'll get this pushed up tomorrow, though =)
Activity
dstroot commentedon Jul 8, 2014
I love Jade because of how it takes away a lot of the HTML 'cruft' and I find Jade really easy to follow. I definitely see the analogy to coffeescript. I have looked at coffeescript several times. However for whatever reason I haven't had the same feelings for coffeescript. I "had to" pick one of the HTML templating tools and I happened to choose Jade but I haven't felt I had to use a tool like coffeescript. By keeping this in pure JS I feel it's maybe more accessible to a wider audience.
Long way of saying I guess I'm just not that familiar with coffescript.
dudo commentedon Jul 8, 2014
Makes sense. I'll work on adding support for it, while keeping the system files in pure JS. We just have to add
coffee-scriptas a dependency, andgulp-coffeeto devdependencies. A little snippet, and maybe a linter, and users will be able to use coffeescript for their projects.I'll holler when I have a PR ready.
dstroot commentedon Jul 8, 2014
Awesome - that would be really helpful. Maybe even encourage me to give it an honest try ;)
dudo commentedon Jul 11, 2014
Hey Dan. I have a PR ready for the coffeescript integration. You wanna give me permission to push a branch?
I made the appropriate changes, but also converted 2 files to
.coffeeas working examples:user.coffeecontrollerUser.coffeemodelI set $.coffee to compile to
public/js... might consider tucking that away (compileddir or something, then we can ignore it from linting?)We can chat a bit after you take a look at it, and see it in action.
dstroot commentedon Jul 12, 2014
As far as I know I don't need to give permission - just open a pull request. That's how I have done it on other repos. Looking forward to checking it out!
dudo commentedon Jul 12, 2014
I'm only pushing my coffee branch, too... not master. I can pull fine... just can't seem to push.
dudo commentedon Jul 12, 2014
might have to add me as a collaborator in settings.
dstroot commentedon Jul 13, 2014
Have you tried opening a pull request? Generally contributors don't push, the owner pulls. At least thats how it's worked on other repos I have contributed to. You open a pull request with the changes in your fork. I review them and pull them in.
dstroot commentedon Jul 17, 2014
You give up on me? ;)
dudo commentedon Jul 17, 2014
Haha, no. I'm used to bitbucket, I guess. You just push a branch up, then submit the PR. I'll figure it out here soon... I've been playing a bit more with ReactJS lately. I'll get this pushed up tomorrow, though =)
Cheers!
dstroot commentedon Jul 17, 2014
React is damn cool - I played with it a bit too. It's just pretty "different" so you really have to commit to it I think rather than just dabble...