Re: gwt-inerop-utils preview

Paul,

I am also hesitating a bit too ... I see some people that I respect do go for the whole enchilada with no regrets. Here is a JS API that requires 4-argument callback. 

Jen does have a point  about custom defined functional interfaces, they:

- can have more specific argument types, can even be primitive ones (int, boolean, etc...)

- can be documented much better

On Friday, June 3, 2016 at 11:32:24 AM UTC-7, Paul Stockley wrote:

Jens,

    I can see your point, about the usability when you get many arguments. Originally I was going to kind of mirror the Java JDK and not go more than 2. Personally, I think it is a lot better to define custom interfaces when possible. To avoid having hundreds of class files I have started making them local to the API classes. I think this helps with readability.  

The case when the generic functions are useful is when you are prototyping a new API or porting some exsting javascript code. Hristo, what is an actual case where you need 4 or 5 parameters? 

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.