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.
The documentation for Ext.util.TextMetrics.getSize says: "only available on the instance returned from createInstance". In Ext 4, there is no createInstance, anymore nor is TextMetrics a singleton.
Btw, I find it quite hard to keep an overview of the bugs reported in this thread. I have to read the whole thread to see whether a bug has been reported before, and how do you know whether a bug has been fixed or not? Is there no better way/tool to organise bug reporting?
I can't find anywhere on the documentation the config option "uses", I see in the examples that is an array of classes to use that are passed to the Ext.Loader but is not documented...
By the way, I liked the 3.x documentation page more, why have the tabpanel if you are only using one tab??
Thanks to everybody for reporting. All documentation issues noted so far in this thread should be fixed by now and visible in the 4.0.2 release.
Few things to note:
Originally Posted by c089
Ext.dd.DragZone refers to events like this one [--] But they are not listed as events but as methods.
Indeed, the methods in DragZone are actually methods, but the wording of docs made it sound like they were events.
Originally Posted by LesJ
some methods can be *both* static and instance. This is not handled.
This does point to a systemic issue, the current doc-system assumes static and instance methods can't be with the same name. For now we'll try to handle this manually, as there are only few of such cases, but this whole thing deserves a deeper look.
Originally Posted by email@example.com
For some reason the latest docs have remove a whole bunch of classes like the Ext.grid.RowEditor. This makes overriding these classes or trying to understand the Ext inner workings a complete nightmare.
Yeah. Good you brought that issue up. We'll see what we can do about it. Maybe we just have to make all private classes visible again.