// // PLSLoginWindowController.m // Pulse // // Created by Matt Attaway on 2/19/14. // Copyright (c) 2014 Zen of the Monkey. All rights reserved. // #import "PLSLoginController.h" #import "PLSOverseer.h" @interface PLSLoginController () @end @implementation PLSLoginController - (id)initWithWindow:(NSWindow *)window { self = [super initWithWindow:window]; return self; } - (void)windowDidLoad { [super windowDidLoad]; NSString* title = [[NSString alloc] initWithFormat:@"Enter password for '%@' on %@", self.os.user, self.os.port]; [self.header setStringValue:title]; [self.password setStringValue:@""]; } - (IBAction)login:(id)sender { if(self.os) { [self.os login:[self.password stringValue]]; if(!self.os.needsLogin) { [self.os startTracking]; } } [self close]; } - (IBAction)cancel:(id)sender { [self close]; } @end
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#3 | 8597 | Matt Attaway |
Handle disconnected servers automatically If Pulse loses its connection with the Perforce server it now reports that the connection is down and starts a new timer to look for a live connection. The Overseer handles all of this on its own; unlike login there’s really nothing for the user to do. This change also fixes a bug where the login dialog was not being properly regenerated for connections after the first. User visible change |
||
#2 | 8592 | Matt Attaway |
Add less aggressive notification when background processes detect need to login Instead of popping a dialog up right in your face we use a standard notification and change the status icon to indicate Pulse is unhappy. Using the login menu item will log the user is and restart the background processes. User visible change. |
||
#1 | 8590 | Matt Attaway |
Add crude login capabilities This is the first step toward getting the login behavior I want. Right now anytime a Peforce command gets a login error the Overseer ion charge notifies its delegate, which is currently the AppDelegate. The AppDelegate then kicks off the requisite login dialog which gets the password and does the login. There’s no error handling or feedback and the dialog pops up even when it is a background process that hit the error. The next step is to implement the Login menu item and the ‘need login’ tool tip and status icon. User visible (and possibly user annoying) change |