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.
If I recall the live demo had a minified and concatenated version so I could not get it from there. I also tried to figure out what was wrong with the code in the github myself but I just could not fix it.
I hope the author will update his github soon as I like JAM and would want to start using it as soon as i can...
OK, since I see there's real trouble setting up even a basic app using just barebones I provided through GIT, I'll prepare the whole deal - small demo app that will show you how to integrate and use the menu plugin, along with changing views from menu.
Please, don't ask me questions like "how do I make app remember the last view I was on before I exited...".
This is not the goal of this plugin. You will have to code in your own logic for specific features you need, or else this plugin will end up being too complicated and not "just" app menu
well, still unusable.
the index.html points to 2.1.1 and not 2.0.1. trying to work with 2.1.1 yielded the same results as before the latest check-in (cramped components on the upper left side). I think the majority needs 2.1.1 support.
thanks for the re-factoring and putting the time to fix this but I will wait until this thing is stable enough.
Fixed path to SDK in index.html. This is really not a biggie man, you just needed to drop the SDK and fix this path, cmon Have you actually tried it with 2.0.1?
Cramped components on the upper left side - this is what I saw when trying to use old css build, from 2.0.1 sdk. I think this is solved by rebuilding scss files using defaults from 2.1.1.
I'll check this css issue once more, and try to get it right for 2.1.1 with mask and all.
Boy, you're talking like 2.1.1 is Holy Grail compared to 2.0.1
I've been out of the game for a month or two - can you tell me what are the real improvements in 2.1.1?
I remember reading topic about upcoming release/ongoing issues a while back, bad scroll performance on Androids, for example, and it didn't sound they were going to fix it in 2.1.1....
listen, I have changed what ever I could (inc. the path to the SDK) but it did not work with 2.1.1.
I personally appreciate your work and help. however, if you put a component out and expect others to fix it up I think you are taking the wrong path.
also, it does not really matter what benefits 2.1.1 has over 2.0.1. its the principle of being able to use whatever build we developers choose and have the component work, not to mention that fact that 2.2 is just around the corner and I am aiming to use it.
just my 2 cents.