Hello, I have been using gwtquery for months in many projects where SEO is needed. Is in these kinds of projects with a lot of javascript and SEO, that GWT + gwtquery combination is a fantastic solution (test, reusing, compression, ...).
Unfortunately gwtquery has not been updated in a year (I know Ray has been over-worked this time), and there is not a stable release. I sent a big patch to the project a year ago, and now I have to use a patched version of the trunk with many fixes. Lately, we at Apache-Hupa (The webmail of James written in gwt) are thinking to use it to change the behavior of 'html' messages (change links actions, classes, etc..), but we can not include the library until a non SNAPSHOT release is available. So, I vote for continuing the developing of this great library, or include its features in gwt. PS: Ray, I'd like to have comitter access to gwtquery to send a bunch of fixes I have (if possible). Best Regards Manolo On Thu, Feb 11, 2010 at 4:17 AM, jarrod <[email protected]> wrote: > Well count me in for whatever I can do to help get support for a > selector engine into GWT or a well supported community project. > Admittedly, I am no browser quirk guru (which explains why I love > GWT!), but I'll offer my services any way I can. > > It's obviously not release-grade, but I did throw up a project to > provide Java bindings for Sizzle: > http://code.google.com/p/gwt-sizzle/ > > For now, I'm trying to keep it stupid simple. Just the bare minimum to > return a set of Nodes, given a selector. Maybe I can eventually get > the Sizzle code ported to GWT code to take advantage of deferred > binding in the compiler. > > Thoughts? > > > > On Feb 9, 11:37 pm, Bruce Johnson <[email protected]> wrote: >> And if we can get GwtQuery to the point where a lot of people really like >> it, I think we'd seriously consider rolling it into GWT proper. >> >> >> >> On Tue, Feb 9, 2010 at 11:34 PM, Ray Cromwell <[email protected]> wrote: >> > GwtQuery was developed before Gwt 2.0 and it's been a while since it's >> > been updated, but I believe it always was the intent for it to be a >> > 'proving ground' for bringing CSS selectors and jQuery like >> > functionality into GWT core. Besides GWT 2.0 and/or IE8, let me know >> > any issues that are most important to you. Perhaps I can grant those >> > interested in helping comitter access. >> >> > -Ray >> >> > On Tue, Feb 9, 2010 at 8:12 PM, jarrod <[email protected]> wrote: >> > > Yes, I am quite familiar with the project and have tried using it >> > > several times. Unfortunately, it does not work very well with GWT 2.0, >> > > does not support IE8, and appears to be dead as far as code >> > > maintenance. I certainly wish that weren't the case, but given the >> > > outstanding issues and lack of any code commits... what can you do? >> >> >http://code.google.com/p/gwtquery/issues/list?can=1&q=&colspec=ID+Typ... >> >> > > On Feb 9, 10:26 pm, John Tamplin <[email protected]> wrote: >> > >> On Tue, Feb 9, 2010 at 9:51 PM, jarrod <[email protected]> >> > wrote: >> > >> > I have to believe this topic has been broached before, but why does >> > >> > GWT not contain any kind of CSS selector engine? >> >> > >> > More and more I am using GWT to build JavaScript API tools for this >> > >> > that or the other, and often this means integration with non-GWT code >> > >> > (read: hand-written HTML, CSS and JavaScript). >> >> > >> > Tool kits like JQuery and Dojo provide great helper methods for >> > >> > manipulating the DOM via CSS selectors - a feature that is distinctly >> > >> > absent from GWT. And yet, because of the vast differences in browser >> > >> > support for various CSS selector methods (and CSS support itself), it >> > >> > seems like a perfect fit for GWT, given the deferred binding >> > >> > capabilities the compiler offers. >> >> > >> > I do not believe GWT needs to support all the fancy helper "shortcut" >> > >> > methods that other toolkits provide. Most of the extra features like >> > >> > animation already have reasonable equivalents in GWT, and JQuery's >> > >> > method chaining is just a hard-to-read way of minifying your code - >> > >> > something GWT also already does. :-) >> >> > >> > Probably my favorite CSS engine right now is Sizzle JS (http:// >> > >> > sizzlejs.com/) and I can't imagine it would be hard to write GWT >> > >> > bindings for this library (it has three public methods in the API!). >> > >> > In fact, if I can't find them with a quick Google search, maybe I'll >> > >> > start a new project to do so. >> >> > >> > The bindings would be a good start, but this is definitely a feature >> > >> > I'd like to see get first-class support in GWT. >> >> > >> Have you seenhttp://code.google.com/p/gwtquery/wiki/GettingStarted? >> >> > >> -- >> > >> John A. Tamplin >> > >> Software Engineer (GWT), Google >> >> > > -- >> > >http://groups.google.com/group/Google-Web-Toolkit-Contributors >> >> > -- >> >http://groups.google.com/group/Google-Web-Toolkit-Contributors > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors To unsubscribe from this group, send email to google-web-toolkit-contributors+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
