Closed vfonic closed 9 years ago
Thanks for the reply and explanation. I'm looking forward for updates to the package.
+1 for the coffeescript support, I was excited to find this plugin but I'm afraid it is not very useful for me at this point. Anyway, nice work, I hope to see an update soon ;-)
+1 for the CS support. It's fantastic to use coffeescript with AngularJS. See this article for example: http://alxhill.com/blog/articles/angular-coffeescript/
+1 for CS Support. This is already a great package for sublime text, but coffee script support would expose this package to more individuals.
I've decided against fragmenting the code into ST2/ST3 branches and now have sometime to look into the CS addition. After reviewing some CS code fragments specific to angular it might not take much to add it in.
It would be nice if any of you, @gamegenius86 @oliverzy @spint @vfonic , have (or know of) a codebase that you can point me to that has a decent amount of angular written in CS that I can test against it, I'll see if I can get this knocked out.
+1 * 100 @subhaze - Your Angular ST package with CS would be insanely sweet!
There is a CoffeeScript version of the PhoneCat tutorial here: https://github.com/jmafc/angular-phonecat-brunch , could be helpful for testing?
@AndreasHassing Thanks, I'll see what I can get working.
Just wanted to check in on progress with this. Run into any problems?
Not anything in general, my free time has been cut pretty short these past few months. I have some, homebrewed, unit testing in progress and an experimental branch I started up here https://github.com/angular-ui/AngularJS-sublime-package/tree/experimental-coffee
So there's been 'some' progresses, just slow at the moment :/
I hate to bother, but is there any updates regarding CoffeeScript support?
I wanted to get this in, but in reality, I don't use CoffeeScript so I don't have much inspiration to add it or extra time on hand for supporting CoffeeScript as a new feature in the future. Sorry :-/
I hadn't planned on adding CoffeeScript support, but, I'm not against it.
My current thought process has been:
Once Package Control 2.x officially releases, fully separate the codebase into a ST2/ST3 branch system to help clean up the code, break up the main py file into smaller, testable, files.
Then add unit tests where possible so I can more easily experiment with the codebase without having to manually go through each feature by hand, in each editor, testing each lang, looking for regressions :)
After all that I'd feel more comfortable with the idea of introducing another lang to support.