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.
Over the last couple of weeks that I've been actively using ExtJS again and 3.0 in particular I often come across weird, inconsistent, unexplained behaviour in the framework. These hinder people using the api effectively often requiring to go and consult the docs or even look at the source code. While in the end this can't be avoided (and shouldn't) I think the api can be improved significantly if it were following a more consistent design.
Here are but few of such problems:
Some components support 'icon', others 'iconCls' and some both. There is no clear consistency
CSS class property is often named differently. Sometimes cssClass whiel at other times shortened to cls. While class can't obviously be used due to it being a reserved keyword I feel it should just use 'cls'
Class and xtype names are at times nonsensical or mismatching: GridPanel -> grid, TreePanel -> treepanel, TriggerField -> trigger. I think more consistent corrolation between the actual class and xtype would help a lot in code readablity.
This are few pains I've had so far. I do think that there should be more effort in streamlining the api and the framework. For example by stating mismatching properties and xtypes as deprecated in extjs 4.0 and then remove deprecated features from 5.0 and so on.
This is one of those things that I've pinged the team about and they've communicated that they are aware of these issues. Being that changing things in the 3.0 branch would be a breaking change, they are not going to. So i guess they will have to wait till 4.0.
yes that makes sense. Like I said declare methods, classes, properties, etc. as deprecated in the next major version (at least things that can't be easily removed to keep backward compatibility) and then commit to remove in the next version. This would give ample of time and warning for people to stop using deprecated features.