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. 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 ". Happy new year and thanks again! On Monday, December 31, 2012 9:58:44 PM UTC-2, Thomas Broyer wrote: > > > > On Monday, December 31, 2012 10:55:50 PM UTC+1, Sebastián Gurin wrote: >> >> I needed a lightweight solution for CSS selectors in >> com.google.gwt.dom.client.Element so I made a GWT port of the JavaScript >> library *sizzle*js.com/ <http://sizzlejs.com/> > > > Ah, this is not a port, it's a wrapper. > Also note that the <script src=""> in the gwt.xml won't work with the > xsiframe linker (and the xsiframe linker is the future) > -- 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/-/RjoowyRiuDEJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
