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 am evaluating gxt and I am wondering, whether the Has* GWT interfaces will be supported by the gxt widgets in the future. I mean the interfaces like the HasValue<T> for TextBox or HasText for Label in the common GWT widgets.
These interfaces are quite useful, as You can reference your widgets in the presenter (controller) through these interfaces. This makes your code easy to test in common junit tests, as You can mock the view.
Please let me know, whether such support is planned to be introduced.
That would be a good and natural evolution for the GXT platform; the decision to implement everything from ground up shouldn't exclude the possibility of integrating some elements that are just a good fit. In the case of interfaces, I think the decision is a no-brainer.
Ok, as a result of this discussion and some other threads all over the GXT forums, I created a google code project to address the problem. It is a thin layer of interfaces and simple implementations that sits on top of the GXT framework. The main purpose is to provide a simple way of creating code that is completely testable and mockable via mocking frameworks (such as Mockito). http://code.google.com/p/gxt-interfaces/
I will try to upload the artifact on some public maven repos as well, but in the meantime, just import the code. Hope it helps. Eugen.