Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The solution proposed by the S.O. post you link could be implemented in this way:</p> <p>1) create a wrapper to MGTwitterEngine; this wrapper will expose any selector you need of MGTwitterEngine and will add to each of them a parameter which identifies the view controller that is calling it;</p> <p>2) your wrapper to MGTwitterEngine would act as a unique delegate to all requests sent;</p> <p>3) for each request that the wrapper receives from a view controller, the wrapper will store the view controller address in a NSMutableDictionary associated to the twitter id;</p> <p>4) when a response comes back, the delegate (which is the same object as the wrapper) will find out which view controller sent the request initially (by searching in the dictionary for the twitter id that came with the response), and forward the response to it.</p> <p>I hope this helps....</p> <p>EDIT:</p> <p>this is how you could do it (I am including only 1 API call and just the relevant code):</p> <pre><code>@interface TwitterClientViewController : UIViewController &lt;MGTwitterEngineDelegate&gt; { } @end @implementation TwitterClientViewController; - (void)requestListOfUsers:(NSString*)username { [twitterEngineSingleton getListsForUser:username requestDelegate:self]; } - (void)requestSucceeded:(NSString*)connectionIdentifier { NSLog(@"Hello"); } @end @interface AdvancedTwitterEngine : NSObject &lt;MGTwitterEngineDelegate&gt; { MGTwitterEngine* _engine; NSMutableDictionary* _callerIds; } -(NSString*)getListsForUser:(NSString*)username requestDelegate:(id&lt;MGTwitterEngineDelegate&gt;)delegate; @end @implementation AdvancedTwitterEngine; -(void)init { if (self = [super init]) { _engine = [[MGTTwitterEngine alloc] initWithDelegate:self]; _callerIds = &lt;init&gt; } return self; } -(NSString*)getListsForUser:(NSString*)username requestDelegate:(id&lt;MGTwitterEngineDelegate&gt;)delegate { NSString* twId = [_engine getListsForUser:username]; [_callerIds setObject:controller forKey:twId]; return twId; } //-- delegate methods - (void)requestSucceeded:(NSString*)connectionIdentifier { id&lt;MGTwitterEngineDelegate&gt; dlg = [_callerIds objectForKey:connectionIdentifier]; [dlg requestSucceeded:connectionIdentifier]; } @end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUsing MGTwitterEngine Singleton
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsergio
    1. USsergio
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing MGTwitterEngine Singleton
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO1. What do you mean by expose any selector and will add to each of them a parameter identifying viewcontroller that is calling it?
      singulars
      1. PO
      1. USsayzlim
    2. COfor each "required" selector in MGTwitterEngine, the wrapper will offer that same selector with an added parameter; there are many different design choice you can do here, so basically I cannot go in more detail. The idea is "extending" the MGTwitterEngine API by adding the selector that also include the "sending" view controller parameter; as to the actual request implementation, those additional selectors would simply call the base implementation found in MGTwitterEngine (after dealing with the nsdictionary stuff).
      singulars
      1. PO
      1. USsergio
    3. COSorry if I'm too slow to catch on. Basically, I should write my own method for the wrapper that use the MGTwitterEngine methods to fetch the data. If I only have one view, can you show me an example how you'll create one method within the wrapper? (Any design is fine, and if you don't mind, please stay for while... because I'm still confused)
      singulars
      1. PO
      1. USsayzlim
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload