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.
one of the best components I've seen fo sho.
anyways, tested this on my galaxy nexus with ICS 4.0.2:
- on chrome beta - doesnt work at all (but its the first beta so will probably be fixed soon)
- on the default android browser it works. some quirks though mainly due to animation (is there a way to disabe animation?). on the way out the sliding panel adjusts a few pixels from the top. on the way back the sliding panel adjusts it self such that the whole panel goes a few pixels to the right and to the bottom and that adjusts back. looks kinda bad.
I did not look at the code but I used to see such behavior in ST1 when I was relayouting components...
I will use my iphone when I get back home to test this plus film the nexsus's behavior with the iphone and put a link here so that you can see what I am talking about.
BTW, the sliding gesture on the toolbar to open the menu - no sure its a good idea for android cause on chrome sliding like that switches between open tabs...
great component! hope to see it polished some more and finalized - I will surely use it.
thanks for sharing!!
BTW; and this is more of an MVC architecture question
the sliding menu is a component, yet, in the example, it resides in the view folder of an ST2 MVC app. is that where custom components should go? is view.js the right name?