#import <UIKit/UIKit.h>
#import "QueueITEngine.h"

@interface TopsTableViewController : UITableViewController<QueuePassedDelegate, QueueViewWillOpenDelegate, QueueDisabledDelegate, QueueITUnavailableDelegate>
-(void)initAndRunQueueIt;
@end

-(void)initAndRunQueueIt
{
    NSString* customerId = @"yourCustomerId"; // Required
    NSString* eventOrAliasId = @"yourEventId"; // Required
    NSString* layoutName = @"yourLayoutName"; // Optional (pass nil if no layout specified)
    NSString* language = @"en-US"; // Optional (pass nil if no language specified)
    
    self.engine = [[QueueITEngine alloc]initWithHost:self customerId:customerId eventOrAliasId:eventOrAliasId layoutName:layoutName language:language];
    [self.engine setViewDelay:5]; // Optional delay parameter you can specify (in case you want to inject some animation before Queue-It UIWebView or WKWebView will appear
    self.engine.queuePassedDelegate = self; // Invoked once the user is passed the queue
    self.engine.queueViewWillOpenDelegate = self; // Invoked to notify that Queue-It UIWebView or WKWebview will open
    self.engine.queueDisabledDelegate = self; // Invoked to notify that queue is disabled
    self.engine.queueITUnavailableDelegate = self; // Invoked in case QueueIT is unavailable (500 errors)
    self.engine.queueUserExitedDelegate = self; // Invoked when user chooses to leave the queue
    
    NSError* error = nil;
    BOOL success = [self.engine run:&error];
    if (!success) {            if ([error code] == NetworkUnavailable) {
            // Thrown when Queue-It detects no internet connectivity
            NSLog(@"%ld", (long)[error code]);
            NSLog(@"Network unavailable was caught in DetailsViewController");
            NSLog(@"isRequestInProgress - %@", self.engine.isRequestInProgress ? @"YES" : @"NO");
        }
        else if ([error code] == RequestAlreadyInProgress) {
            // Thrown when request to Queue-It has already been made and currently in progress. In general you can ignore this.
        }
        else {
             NSLog(@"Unknown error was returned by QueueITEngine in DetailsViewController");
        }
    }
}

// This callback will be triggered when the user has been through the queue.
// Here you should store session information, so user will only be sent to queue again if the session has timed out. 
-(void) notifyYourTurn: (QueuePassedInfo*) queuePassedInfo { 
    NSLog(@"You have been through the queue");
    NSLog(@"QUEUE TOKEN: %@", queuePassedInfo.queueitToken);
}

// This callback will be triggered just before the webview (hosting the queue page) will be shown.
// Here you can change some relevant UI elements. 
-(void) notifyQueueViewWillOpen { 
    NSLog(@"Queue will open");
}

// This callback will be triggered when the queue used (event alias ID) is in the 'disabled' state.
// Most likely the application should still function, but the queue's 'disabled' state can be changed at any time, 
// so session handling is important.
-(void) notifyQueueDisabled { 
    NSLog(@"Queue is disabled");
}

// This callback will be triggered when the mobile application can't reach Queue-it's servers.
// Most likely because the mobile device has no internet connection.
// Here you decide if the application should function or not now that is has no queue-it protection.
-(void) notifyQueueITUnavailable: (NSString*) errorMessage { 
    NSLog(@"QueueIT is currently unavailable");
}

// This callback will be triggered when user has been on the queue page via the webview
// but decided to click the 'leave the queue' button/link.
// Most likely you would want to clear any session and refresh so user will be joining the queue again.
// We do recommend you to hide 'leave queue' on your queue page so this callback should not be handled in most cases.
-(void) notifyUserExited {
    NSLog(@"User has left the queue");
}