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 have a workspace with few pages (ExtJs apps) , all of them using the same theme (package).
The theme has many images , which after app compilations are stored in each one of the pages (apps) seperately.
This causes a waste of storage , and worst of all- it prevents from caching the images on clients browser.
Is there a way to have the theme images stored in one place ?
I have a similar problem with a "slight" difference I have one ExtJS web app and one Sencha Touch android app. I think that dynamic content such as uploaded images should be available through something like http://cdn.domain.com/uploads/ for both apps, even though ST app is native. Not sure about static content in my case. Probably it needs to be duplicated in both apps, since android apps are packed into .apk with phonegap/cordova and should not load static resources from the web. But in your case, I think you should put shared resources on a common CDN. You can also control which folders are merged into which app with sencha cmd. It depends on how you structured your apps. Here's my idea on how it should be done.
Thanks, seems I'll indeed need to make a dedicated folder with shared images and somehow tweak the build scripts and sass to use them. The downside is that I loose all the benefits of sencha theme package and cascading of resources.
Other approach I thought of is making another 'stub' app which will 'require' all the shared components. then, all the other apps will point to that app's resources.
Both of the approaches unfortunately involve a degree of hacking and struggling.
It would be nice to have some kind of advice / guide/ best-practice from Sencha for shared resources in multipage apps - It's not an uncommon practice imho.
p.s. a cdn is not an option in my particular case. It runs on devices in (often) offline environments, not on a public web-server. and those devices have a limited storage, which is unresponsible to waste with many duplicate resources.