Tuesday, January 1, 2013

Re: gwtsizzle - CSS selectors for GWT dom



On Tuesday, January 1, 2013 6:13:32 AM UTC+1, Sebastián Gurin wrote:
Thank you Thomas for the clarification and for taking a look to the project. Didn't know about the new xsiframe. I'm reading some documentation and fixing my projects.

about wrapper/port thing, I thought a wrapper was when you put the JSO as a "pure" java class attribute. Then you delegate all methods to the JSO. You have a little (x2) overhead because of the second call but you gain in language because you work with "pure" java so you can do new MyClass() and inheritance.

I would say there are two "levels" of wrapping: providing a GWT API for a JS lib, and then providing a more Java-like/bean-like API on top of it.
 
In my case I use JSOs for talking directly to JS objects from java, so I didn't called "wrapper" but perhaps you are right, i don't know... iIm pretty confused about terminology here.... you are right it is not a port... I would call it "(direct) Java API for sizzlejs ".

Let's call it a "bridge" then. 

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/4Tiqzl06LmMJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment