Turkiyenin en sevilen filmlerinin yer aldigi porno internet sitemiz olan ve sex tarzi bir site olan sitemiz gercekten dillere destan bir durumda herkesin sevdigi bir site olarak tarihe gececege benziyor. Sitenin en belirgin ozelliklerinden birisi de Turkiyede gercekten kaliteli ve muntazam, duzenli siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir.
Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.
I just spotted TypeScript (http://www.typescriptlang.org/), and it looks promising. Has anybody had a chance to play around with it yet? I want to understand if it would be possible to produce a TypeScript declaration file to declare all the types from the Ext JS and Sencha Touch frameworks. I'd love to have better static analysis and tool support for my Sencha development work.
Regardless of how many times I say this comment was obviously a personal comment, it's still personal. If you haven't talked to me or followed me on Twitter or anything, I'm anal about my code and the syntax that TypeScript (even ES6) is ugly.
I was thinking about looking at the existing declaration files that the TypeScript team already produced for JQuery, JQuery UI, node.js, etc. to figure out exactly what kind of metadata it needs and then seeing if it's possible to create declarations for some Sencha classes manually. Then, once I have an idea if it's possible and, if so, what exactly the declarations look like, I could try to automate the construction of the declaration file(s) from the Sencha class system. Even if you could manually create declarations for the entire framework, you wouldn't want to curate them manually; you would want them to be updated automatically whenever the underlying framework changes. Of course, it would be great if Sencha could provide the necessary type declarations. I'm sure the creators and maintainers of the framework understand it better than I ever will.
For something like Ext, I don't think it makes tons of sense. Ext provides a class system and takes care of most cross browser issues. It provides a ton of functionality that Js doesn't do on its own. As far as code analysis is concerned, Sencha recently released an eclipse plugin that brings plenty of code intelligence to the table. I think TypeScript would add a layer of complexity to Ext without bringing any benefit that it doesn't already have. TypeScript looks cool and I think it would be great to use if you are working with Js on its own, but not with something like Ext.
I think it would be worth it just for the intellisense...
FWIW - I was having a play with this today - extracting the data from the documentation - and I've got that into a C# object so I can play with it..
For now - as an example - I can generate code like this (this is pretty much straight from reading the jsduck json output) :
While I have never used Ext's eclipse plugin as it is bundled with Sencha Complete, I would think it would be much more intelligent for use with Ext than a third party language's intellisense. I would certainly support a person's decision to try to add it though.
I do agree however that a lot of those "ugly" optional features of TypeScript are already solved when using Ext such as module-like class definitions, callParent(), constructors, as well as a type/class system with inheritance.
Even though there is an Eclipse plugin for Ext, I don't see it being an apealing option for windows developers to have to use both visual studio and eclipse to properly debug things at development-time....
Since the Ext docs are generated from the source, I don't think it would be difficult to generate .d.ts definitions as well out of them.