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.
If you mean documentation for JSBuilder, that would be no. It looks like the code was ported from something into C# and there are virtually no comments.
If the code was commented in the standard .Net/C# format, it could be used to generate nice HTML doc via something like NsDoc. However, since there's talk about migrating this to something else (Swing, maybe??), it's probably not going to happen short-term. Even if it's not migrated, I don't know that anybody is going to go thru and document the current codebase.
I was wondering if it was possible to generate a documentation that looks like Jack's documentation center -with or without JSBuilder-.
I think the question was regarding generating doco with the same styles/formatting as Jack's new doc center. The answer currently is no. Jack wrote a custom PHP-based parser to output his docs that is separate from JSB and currently not public. However, we have discussed possibly rolling that into JSB in a future release. Nothing has been decided for sure yet though.
Originally Posted by tryanDLS
It looks like the code was ported from something into C# and there are virtually no comments.
If the code was commented in the standard .Net/C# format, it could be used to generate nice HTML doc via something like NsDoc.
Just to clarify, it was not ported -- it was originally written by Jack. But... it started out as a "quick and dirty" solution to a problem that Jack had that slowly grew into a larger project. Initially, I don't think Jack even thought about sharing the source until people started asking for it, hence no thought about internal documentation. If the tool continues to move forward and become more popular, then reworking it / porting it / documenting it will probably happen at some point.