In the new release candidate, the AbstractStoreSelectionModel<M> has been modified from using the standard HasSelectionHandlers<T> to a new version HasSelectionHandlers<M>. These interfaces are exactly the same. The difference lies in the new custom SelectEvent. This event also does the same thing, but also adds a Context object. That is the only difference. Other than that, it looks like pretty much a copy-paste job.
While the extra information might prove useful to some implementations, it makes it harder when multiple view implementations are used for a presenter. Custom implementations of a view that do not rely on GXT can now no longer implement the same view interface.
Why not create a new HasSelectionHandlersX interface that extends the default HasSelectionHandlers? Why not implement both interfaces?
You have raised some good points. We have opted to rename the GXT versions to CellBeforeSelectionEvent and CellSelectionEvent. Both events extend the GWT versions. The primary reason we created the new classes was that we were not able to create and fire the events with our cells (member visibility issue) and to add support for the context in the event for cells. With this change, the code will work the same way as before the RC release.
Turkiyenin en sevilen filmlerinin yer aldigi xnxx internet sitemiz olan ve porn sex tarzi bir site olan mobil porno izle 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 porno izle siteleri olmamasidir. Bu yuzden iste. Ayrica en net goruntu kalitesine sahip adresinde yayinlanmaktadir. Mesela diğer sitelerimizden bahsedecek olursak, en iyi hd porno video arşivine sahip bir siteyiz. "The Best anal porn videos and slut anus, big asses movies set..."