[gwt-contrib] Re: GWT-Query - needs forking?
Hi Ray, its more that I want to apply the critical IE8 patches that have been there for several months If you were planning on starting working on it again, then no problem, I'll leave if to you. On Mar 17, 8:59 pm, Ray Cromwell wrote: > Richard, > The project is on life support because of other work I've been doing > on the GWT compiler, but I do intend to revive it soon. I'd be happy > to give committer access, can you send me an example patch with what > you'd like to change for review? > > -Ray > > On Tue, Mar 16, 2010 at 8:18 PM, Richard Vowles > > > > wrote: > > Hi all, > > > Not sure how to get a hold of the person responsible for GWT-Query, > > which was spoken of in terms of including it in GWT itself. This is my > > last ditch attempt - the project appears to have died in May, and I'd > > like to get committer access to the project. > > > Ta! > > Richard > > > -- > >http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] GWT-Query - needs forking?
Hi all, Not sure how to get a hold of the person responsible for GWT-Query, which was spoken of in terms of including it in GWT itself. This is my last ditch attempt - the project appears to have died in May, and I'd like to get committer access to the project. Ta! Richard -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: HtmlUnit OOPHM client
Am I to understand from this that someone else (other than me) has implemented a OOPHM client for HtmlUnit? On Sep 17, 7:30 am, j...@google.com wrote: > Reviewers: jat, > > Message: > For some reason, Reitveld 404s on JavaObject and HtmlUnitSessionHandler, > so comments are here: > > HtmlUnitSessionhandler --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] htmlunit 2.6 is out
And there are quite a few fixes in it, in case anyone wants to update the lib. http://htmlunit.sourceforge.net/changes-report.html#a2.6 --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: UiBinder - ids vs classes and html element binding
No - more like (for example), when it hits a it always creates a Google LabelElement - say I want to create a MyLabelElement instead (which does some extra thing, which in my case it does). I can't do it without hacking it (which I have done). Happy to file an Issue on this... On Aug 27, 11:49 pm, Joel Webber wrote: > I'm not entirely certain I understand the problem here -- is the issue that > you want to use an element for which there's no Element subtype in the .dom > package? We didn't go to great lengths to make this extensible, because the > set of legal HTML DOM elements changes at a glacial pace. But if there's one > we missed, please let us know! --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: UiBinder - ids vs classes and html element binding
I wouldn't mind some convincing urls to backup this viewpoint if you have any :-) The entire rest of the team here is saying "id id id", "class bad, id good". Searching for "html id brittle" wasn't very enlightening :-) I have also found that there seems to be no way of overriding the class that is created when hitting HTML elements - it is hard coded in UiBinderWriter to look only in the Google classes for elements with TAG. Descending and fixing it for UiBinderWriter was relatively straight forward (even tho I had to put the replacement class in com.google...), but because all of the important methods are private in UiBinderGenerator, I had to replace that and copy the methods, which was triple yuk. Good to have the source though :-) Solving the problem would be easy (i.e. allowing people to override and replace their own classes only if they wanted to) by the UiBinderGenerator asking for the UiBinderWriter through the GWT.create mechanism and the right methods being protected in the Writer instead of package private... You guys may already have a different solution so it that is more elegant though. Ta Richard On Aug 27, 3:56 am, Ray Ryan wrote: > And you can set the debug id via ui.xml: > Hiya, pal. > > If you're not going to use CssResource, there is nothing you can do with an > id selector that you can't do with a class selector. I really discourage the > use of id selectors, they're brittle. > > rjrjr > > On Wed, Aug 26, 2009 at 11:53 AM, Joel Webber wrote: > > The biggest problem here is that ids have to be unique within a document, > > and UiBinder has no way of enforcing this. > > If you want to use it for styling, you're probably better off with > > CssResource (we're working on updating the samples to reflect what we > > believe to be the best pattern for doing this). > > > As for testing, I assume you mean using something like Selenium. This is > > actually why we created the UIObject.ensureDebugId() stuff -- especially so > > that you can turn it off in deployment. But if you're using GWTTestCase, you > > can just bind the elements to fields and grab those directly. > > > Cheers, > > joel. > > > On Tue, Aug 25, 2009 at 10:38 PM, Richard Vowles > > wrote: > > >> One of the things I have noticed with the UIBinder is that you can't > >> set the id on the fields - which is pretty important for css styling > >> and testing. I seem to have to set them in code. > > >> > > >> causes it to fail to compile. I know id is an attribute of getElement > >> () but since this is a very common thing to do, I'd have expected > >> ui:id or some such (or just id being acceptable). Am I missing > >> something? > > >> Ta > >> Richard > > >> On Aug 26, 12:49 pm, Bruce Johnson wrote: > >> > No plans to do drag-n-drop or anything wysiwyg. We'll probably > >> > continue to focus on the basics. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: UiBinder first impressions
One of the things I have noticed with the UIBinder is that you can't set the id on the fields - which is pretty important for css styling and testing. I seem to have to set them in code. causes it to fail to compile. I know id is an attribute of getElement () but since this is a very common thing to do, I'd have expected ui:id or some such (or just id being acceptable). Am I missing something? Ta Richard On Aug 26, 12:49 pm, Bruce Johnson wrote: > No plans to do drag-n-drop or anything wysiwyg. We'll probably > continue to focus on the basics. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Someone with permission want to delete the dodgy files?
Not spamming the group but spamming the files section is pretty cunning. :-( --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
