Ok. I went ahead and implemented the Geolocation stuff too, so this
brings gwt-gears up to speed with the latest gears 0.4 release.
I filled out a CLA, I'm not sure how/when I know that it was accepted.
There are a few things regarding design that I'm wondering. Whats the
preferred solution for handling optional arguments and parameter
objects. For optional arguments I created overloads for each
additional parameter...
public native boolean getPermission()
public native boolean getPermission(String siteName)
public native boolean getPermission(String siteName, String
imageUrl)
public native boolean getPermission(String siteName, String
imageUrl, String extraMessage)
For parameter objects I created a builder which extends
JavaScriptObject.
geo.getLocation(new SuccessCallback() { .... },
PositionOptions.create().setHighAccuracy(true).setGearsRequestAddress(true));
Any tips on better ways to map the JS APIs into Java-land?
On Oct 22, 4:06 pm, Mark Renouf <[EMAIL PROTECTED]> wrote:
> > I think the HttpRequest class has been there, but we didn't include it
> > because we don't have official GWT support in workers yet and there is a
> > comprable RequestBuilder class in GWT proper to use in the Main page. It
> > wouldn't hurt to add it, though!
>
> Ahh. That makes sense.
>
> But, unless I'm mistaken, only the Gears HttpRequest supports the Blob
> API... that's why I jumped into this. I have a working example now
> too. I'll take a look at the procedures for submission and provide
> what I have.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
