@Alex and Damien, Great point! Cannot agree more the new system must go well with Angular js.
For Angular js, look at this project: https://github.com/borisyankov/DefinitelyTyped/tree/master/angularjs it defines Angular modules into Typescripts. In our company, there are two project using Angular + Typescript using the DefinitelyTyped, maybe I can bring some know-hows on that. @Damien One good point of Typescript is, they will not throw any errors when we move onto them. If we have no type on code, it work just like a javascript. (As I already mentioned, it just work if we change xx.js -> xx.ts, just changing the filename) You can have some simple tutorial on that here. http://www.typescriptlang.org/Tutorial Also building Typescript goes well with Grunt, I'm attaching build file we're using. Gruntfile.js === module.exports = function(grunt) { // Project configuration. grunt.initConfig({ pkg: grunt.file.readJSON('package.json'), watch : { scripts: { files: ['sticker/static/ts/**/*.ts'], tasks: ['typescript'], options: { spawn: false } } }, typescript: { build: { src : ['sticker/static/ts/**/*.ts'], dest : 'sticker/static/js/', options: { mudule : 'amd', target: 'es3', sourceMap: false, basePath : 'sticker/static/ts' } } } }); grunt.loadNpmTasks('grunt-typescript'); // Load the plugin that provides the "watch" task. grunt.loadNpmTasks('grunt-contrib-watch'); // Default task(s). grunt.registerTask('default', ['typescript']); }; On Wed Feb 04 2015 at 2:38:54 PM Corneau Damien <[email protected]> wrote: > I think it can be included if it matches multiple conditions: > - Has to be angularjs ready > - Has to be easy to set up (currently we are mainly using yeoman to create > new controllers etc..) > - Has to fit inside of our build and dev Grunt rules > > Not a big fan of adding changes that big just to add the var types into the > code, one thing I'm scared is: Will it pop errors everywhere once it's > activated? (because of missing types?) > > IDE support is not that important since you can always tell your editor to > use javascript highlighting and work without auto-completion. > > > On Wed, Feb 4, 2015 at 2:07 PM, Alex B. <[email protected]> wrote: > > > Having types always strike as a good idea to me, thanks for bringing this > > discussion! > > > > Just to understand the ground better: typescript is made by microsoft and > > AFAIK there are other implementations like Flow > > <https://github.com/facebook/flow> from Facebook and AtScript from > Google > > (part of Angular, superset of Typescript, brings annotations too) > > > > I wonder, should we also consider alignment with angular as an important > > point for whatever alternative we look at? > > > > > > On Wed, Feb 4, 2015 at 12:51 PM, Kevin (Sangwoo) Kim < > [email protected]> > > wrote: > > > > > Hello developers, > > > > > > I'd like to open a discussion on getting Typescript into zeppelin. > > > > > > http://www.typescriptlang.org/ > > > > > > Typescript brings type system onto javascript codes, which improves > > > productivity working with huge js codes. > > > > > > One of the really good point of Typescript is, 100% compatibility with > > > javascript, that is, > > > if we just change xxx.js into xxx.ts, it just works. > > > Then we can add some classes and type annotation gradually. > > > > > > Some frontend guys in our company already compared similar technology > > like > > > coffeescript and finally using Typescript and they are really > satisfied. > > > > > > On the other hand, IDE support could be a limitation of Typescript. > > > IntelliJ ultimate edition ($199) or Visual Studio can be used to > utilize > > > full editing feature of Typescript (auto completion, etc) > > > I can confirm syntax highlighting feature for Typescript works on > Sublime > > > editor. > > > (Of course you can use any editor or IDE to edit ts, tough.) > > > > > > Any idea on this topic is welcomed! > > > > > > Regards, > > > Kevin > > > > > >
