On Thursday, August 21, 2014 10:46:49 AM UTC+2, Zied Hamdi OneView wrote:
Do you think I should enter a feature request with this or is there already something happening in GWT internally?
Nothing's happening right now on RF.
You can file a feature request, but be aware that it's unlikely I would contribute the code (I can't tell for Manolo, the other assigned maintainer for the RF module; see https://groups.google.com/d/topic/google-web-toolkit-contributors/eq0LsmH2blw/discussion) so you'd probably have to contribute the patch.
On Thursday, August 21, 2014 10:59:32 AM UTC+2, Zied Hamdi OneView wrote:
The idea is :"Since GWT is rigid in "when things should happen" (phases), it should be more permissive in how you manage each step"Since it imposes that validation must happen only the validation phase, it should allow to better tune how you do your validation.
This is similar to what I proposed a couple years back about loading the entities: you could optimize your database requests if you knew which things will be needed (e.g. use different fetch groups in JPA to switch between loading relationships lazily or eagerly). It still hasn't happened, and now that I'm an entitled maintainer for RF I don't even know how that could be done "correctly". It's a can of worms. I fear that the validation case you're raising can quickly become a can of worms; and RF is almost already itself a can of worms, so I'm quite reluctant to add features to it… (remember: once introduced, features have to be maintained, and when you're an assigned maintainer, people will held you responsible for the maintenance)
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment