StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12030914
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-19T23:54:02.850
FavoriteCount
0
LastActivityDate
2012-08-19T23:54:02.850
LastEditDate
LastEditorUserId
0
OwnerUserId
239078
ParentId
12007873
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Ok, I figured this out by reading the basic examples in the <a href="http://docs.phonegap.com/en/2.0.0/guide_plugin-development_index.md.html" rel="nofollow">Cordova Plugin Development Guide</a> closely. The problem was with the ordering of parameters for <code>cordova.exec()</code>, which must have changed recently. I plan to submit a pull request on GitHub with a working version of the plugin, but for now, here's the basic solution. Before asking this question, I had updated the imports in AudioEncode.h from <code>#import <PhoneGap/PGPlugin.h></code> to: <pre><code>#import <Cordova/CDVPlugin.h> #import <Cordova/CDVPluginResult.h> </code></pre> Any reference to <code>PGPlugin</code> should also be updated to <code>CDVPlugin</code>, and <code>PhoneGap</code> should become <code>cordova</code>. Here's the crux of the problem: in AudioEncode.js, <code>cordova.exec()</code> (where the original plugin calls <code>PhoneGap.exec()</code>) needs to be called like this: <pre><code>AudioEncode.prototype.encodeAudio = function(audioPath, successCallback, failCallback) { cordova.exec(successCallback, failCallback, "AudioEncode", "encodeAudio", [audioPath]); }; </code></pre> If you don't order the parameters like this, the callbacks won't be passed in (although audioPath was...). Look at the docs for more details, but the parameters have to be the two callbacks first, the module name, the module action, and finally an array of extra parameters. Then, you'll need to read in the parameters in the main encodeAudio function like this: <pre><code>self.callback = [[arguments objectAtIndex:0] retain]; NSString* audioPath = [arguments objectAtIndex:1]; </code></pre> Note that there is only one callback object now, which contains references to the success and fail callbacks. This means that whenever the plugin sets up variables for <code>successCallback</code> and <code>failCallback</code>, you now only need <code>callback</code> (e.g. <code>@synthesize callback</code>). This is also declared in the AudioEncode.h file with <code>@interface</code> and <code>@property</code>. Now, when actually firing the callbacks & returning data (in the <code>doSuccessCallback</code> and <code>doFailCallback</code> functions), you need to use <code>CDVPluginResult</code>, like this: <pre><code>CDVPluginResult* pluginResult = nil; NSString* javaScript = nil; pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_OK messageAsString:path]; javaScript = [pluginResult toSuccessCallbackString:self.callback]; [self writeJavascript: javaScript]; [self.callback release]; </code></pre> Until I get the updated module up on GitHub, this should help anyone to get the plugin working.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPhoneGap plugin: AudioEncode success callback never called
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbjudson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POPhoneGap plugin: AudioEncode success callback never called
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.