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.
We would like to use closure compilation as a final step of validating our JS code. to avoid some trivial errors like extra coma in arrays/objects and some less trivial as well. Is it possible to tell sencha build to fail on certain closure warnings (by code?) also is it possible to provide options to closure compiler so we can control parsing to some extent? Same probably goes for Rhino or YUI
Also Cmd seems to be very un-extensible inside. I wanted to solve it by plugging in my own log handler which will analyze errors/warnings but no way, the whole thing is developed around singletons and static fields, makes assumptions everywhere (even main config file is loaded from where sencha.jar is only) and not modular at all. Also it seems to be not very friendly to be executed not under system class loader. I was trying to create maven plugin out of it (real plugin with sencha.jar and dependencies in maven not one executing local cmd install) and had a hell of a time doing it. Got it working but it's dirty. It is important to be able to have it packaged as maven plugin because using exact version of the tool is crucial to being sure your bug fix release is not going to fail due to updated version of the build tool
Another thing that my compressed version did not work. Dynamic loading in dev mode worked fine all files loading no warnings but compressed version still loaded few of classes dynamically because order of compression was not right. I resolved it by removing views: from controllers. But it does not give me much confedence in Cmd's dependency resolution but maybe I missed some rules, will re-read docs
I tried to do it by plugging in my own ConsoleHandler so I can intercept and analyze all log messages but Cmd seems to be so monolithic and un-configurable piece of code that it does not lend itself to any extensions. Its logging also seems to be very unfriendly to be executed under class loaders other than system (maven environment)
If someone in Cmd team is interested, I am willing to be a guinea pig to try few enhancements and maven plugin out of Cmd