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.
I might have node that contains tens of thousands child nodes.
I'm trying to figure out how to lazily load node children (infinite scrolling).
I can load all children in one go (like it works currently) but it may take minutes to load such amount of a data (in current tests biggest nodes are ~14MB of json data). So is there way to load them like in grid dynamically?
Another option could be grouping by multiple columns in grid, but I haven't found any solution for that either.
Without knowing exactly what you mean by connector (hardware, software, association of some kind?) I'd assume they could be categorised or grouped in some way.
Sorry I can't be more help.
I'd assume, since trees and grids have a common base of table (for some reason I've never quite fathomed), I suppose it would technically be possible to do something similar to the infinite grid with it, but you'd probably run into my favourite(!) class NodeInterface, which is about as flexible as a brick!
You can try to use it or just find some hints, I hope. But I do not believe it will work with 4.1 unfortunately! I have not checked that yet.
It would be nice if you can share your expirience how such data could be well visualized and managed. Maybe we can find some good solution for that together and force that to Sencha team . As you can see I have some problem to convince people to that .
I generally agree with you. It is better to use grids when it is possible. But I (my users) found at least few business cases when trees are more intuitive to manage data. It's usually when "natural" data organization is a hierarchy (products definition or categorization, organization or employee hierarchy, etc.)