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.
My first attempt to make a Facebook-like sliding navigational component, SlideNavigation, has proved to be pretty useful. However, I've gotten a lot of queries from people asking how to make it work in ways that I never originally intended. Some of the most frequent requests are:
Support for both left and right menus simultaneously
Using components other than a list in the menu
Support for multiple slide navigation instances in the same app
Nesting the slide navigation inside other components
With the way that the component is currently designed, achieving any of these would require quite a bit of code changes. So, I've started working on an updated version that is more flexible. I've decoupled the navigation component from the slide component. As a result, all of the above use-cases are now possible and I'm calling the new component 'Ext.ux.slide.View'.
I'll be uploading the code onto GitHub and would love to get some help finishing it. In the meantime, here is a short video to highlight some of the new features of the component.
oh and if you're looking for help on the code, I'd be happy to help out. I have this so far: https://github.com/shepsii/sidenav but no reason to kill one bird with two stones ;-)
I'd love the help dude. I just put the code up on GitHub, but beware it is pretty rough. I literally whipped this together in day. Some stuff is borrowed from my SlideNavigation implementation, but there is a lot of new code in there, so there are bugs aplenty.
My initial plan is to implement at least two main components; the main view (Ext.ux.slide.View) and a convenience class (Ext.ux.slide.List). The slide List would make it easy to achieve functionality like SlideNavigation provides, and could be used as the component on either or both the right and left side. Of course, I'm also totally open to suggestions.
Also, I'm pretty partial to implementing this without a controller--a la the core Sencha components. I like the idea of keeping things simple for people wanting to use this and providing all the base functionality in a single component is really tidy way to achieve this. The 'Ext.ux.slide' namespace also makes it easy to integrate into existing project. My two cents anyway.
Absolutely agree re: controller. The reason it's like that in the example I posted is that the code was ripped out of an application I'm building - hence the full on MVC - but building a component means it should all be on the view, I completely agree. People should be able to use it the same way they do other sencha touch components.
I'll go ahead and take the conversation over to github... cheers!