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.
When having a look at the new site, I'm a bit surprised to see a change in the terms of the license. ExtJS 2.01 and lower were LGPL licensed, but 2.1 is GPL licensed. I'm sure you know that this is a BIG change. Is this intentional or an oversight? I really wouldn't want to see a fork in the community caused by this change of license.
Unfortunately I would have to agree. I have been using ExtJS for a long time now. this switch in license in my opinion is unfortunate, while I don't forsee myself not using this toolkit/library at this time, I still strongly disagree with this decision mainly because the GPL is VIRAL, if you use ExtJS in your app now, you must also license your app as GPL, which I dislike very much.
I would still like to applaud Jack and the rest on their work and thank you for your continued work, but in my opinion this is not a good decision.
Despite the fact that the framework is worth the money - it's definitely a major change in the license policy. You are no longer encouraged to buy a commercial license but forced if you want to keep your application commercial or just closed source.
Again - I'm not telling it's not worth buying it. But this fact should be made absolutely clear to the user community so everyone upgrading from 2.0 branch are aware of the consequences.
I am not sure that it effects me, actually i am sure it doesn't as i emailed support in the past about it. You can use extJS with a closed source backend like php - and in my case the ext code is worthless without the backend anyway.
The case was the same with lgpl, there was no way that your ext widgets could have been licenesed in any other way anyway as they are too much reliant on the core lgpl sourced stuff.
Main point of this - if you are looking to commercially / close source projects with extjs, you either need to buy a license OR make sure your backend is "your backend" lol - that means steeering very clear of ext gwt !