Closed GoogleCodeExporter closed 8 years ago
I would be happy to contribute to a 3.0 version. Does anyone know what the
minimum is to to get it working on PhoneGap 3.0?
Does Apple accept apps that are compiled to XCode 4.3?
Original comment by frank.mena
on 6 Oct 2013 at 1:55
Frank,
It seems like another person is starting to work on this:
https://groups.google.com/forum/#!searchin/mgwt/3.0/mgwt/ikJKAO94w5I/v-bqYrgeDvE
J
Original comment by jve...@gmail.com
on 9 Oct 2013 at 10:14
Tried to create a blank PG 3.1.0+GWT project using the latest version of
gwtphonegap and cannot get it to work.
Here's the code in onModuleLoad:
pg.addHandler(new PhoneGapAvailableHandler() {
@Override
public void onPhoneGapAvailable(PhoneGapAvailableEvent event) {
Window.alert("Ready");
}
});
pg.initializePhoneGap();
onPhoneGapAvailable is never called. Is there anything that needs to be done
differently because this use to work fine in previous versions.
Original comment by jve...@gmail.com
on 14 Oct 2013 at 1:39
This can be resolved by installing the Device info plug-in - gwt-phonegap
should check for it before trying to use it.
Original comment by jve...@gmail.com
on 16 Oct 2013 at 11:58
(This excerpted from an answer I just offered on Stackoverflow)
My work-around is to handle the deviceready event directly.
So in onModuleLoad(), I have:
phoneGap = GWT.create(PhoneGap.class);
phoneGap.initializePhoneGap();
setupOnDeviceReady(); // This needs to follow the call to initializePhoneGap()
Where setupOnDeviceReady() is:
private native void setupOnDeviceReady() /*-{
var self = this;
var cb = function() {self.@com.myapp.client.EntryClass::onDeviceReady()();};
$doc.addEventListener("deviceready", $entry(cb), false);
}-*/;
And onDeviceReady() contains whatever code requires phonegap to be initialized
(i.e., whatever code would have been in the onPhoneGapAvailable handler.
Original comment by mikegodi...@gmail.com
on 10 Dec 2013 at 2:34
gwt phonegap 3.5 supports phonegap 3.5
Original comment by svkirans@gmail.com
on 14 Jun 2014 at 7:11
Original issue reported on code.google.com by
jve...@gmail.com
on 19 Sep 2013 at 11:33