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.
* Comments can be formatted with Markdown instead of HTML.
* A lot more information is inferred from code - so you can keep your comments DRY.
While doing this, JsDuck aims to be backwards-compatible with ext-doc. So comments written for ext-doc will display about the same under JsDuck, but not the other way around.
It's still in early beta, so there's a lot of stuff in my TODO list, but I've already found it quite satisfying to use - not having to type @class and @extends at all have greatly increased my refactoring speed, and the reduced boilerplate code has made me less reluctant to create small little classes.
Tell me what you think.
PS. While developing it I discovered several bugs in ExtJS doc-comments. I've created a list of them for those who care to fix.
Last edited by renku; 21 Sep 2011 at 3:51 AM.
Reason: Updated link (JSDuck now part of senchalabs)
It looks like an interesting project. I'm surprised you went to so much work just to remove the HTML comments you're so frustrated with (IMO not worth the effort... then again, my documentation is very to-the-point).
The thing I like the most about your approach is removing the XML config file - that has been a thorn in my side for a while now.
I haven't downloaded it yet, but I'll spend some time this week playing with it.
Developer Relations Manager, Sencha Inc.
I'm surprised you went to so much work just to remove the HTML comments you're so frustrated with (IMO not worth the effort...
Well, it was an interesting and fun project to do. I had recently learned about recursive-descent parsing, so it was a perfect project to use some of those skills.
given that the sencha team is working on their own jsdoc parser, I don't see the purpose of doing this, other than going through the exercise.
Are you referring to ext-doc, or is there something else on the table?
Speaking of ext-doc, I thought several times of extending it with the functionality I wanted. I studied the source code, played around with it, etc. But in the end I felt that I had to make too many changes, so maybe it was easier to just completely re-implement the whole thing. Besides, writing Java happens to cause pain for me, I opted to have fun instead with Ruby. (Sorry, the last thing is my personal problem - no offence towards Java-guys intended.)