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.
I highly suggest NOT using a mobile framework on desktop applications. It's not architected for it. Also using mobile metaphors for desktop use is going to be somewhat of a UX nightmare. I've seen it time and time again and the projects fail because of it.
I have been reading the Sencha forums about this topic (mob vs. desktop frameworks being different products altogether).
I've already built my Sencha Touch 2 apps. For a first time user of the framework, I think I did "okay". Lost some hair and a few weeks of sleep, but I can manage
I've been very careful with the UX -- made sure to make it usable on iPad but manageable on desktop/mouse. (this was because I had to -- time/money constraints like every other company on the planet)
If I now want to allow desktop users to access these apps, what is the best technology strategy?
Back-port to ExtJS 4?
Or is there a Sencha CMD switch to do the magic for me? (not talking about magically modifying UX... just talking about backend engine/api/CSS/HTML support nightmare being taken care of by the framework)
Any sage advice from the developer community would be greatly appreciated.
I really am loathing opening up all the MVC code and ripping it to shreds just so a desktop browser can render what's already done!