| Name | Modified | Size |
|---|---|---|
| .. | ||
| project.xcworkspace | ||
| project.pbxproj | 11 years ago | 26 KB |
| Change | User | Description | Committed |
|---|---|---|---|
| 8706 | Matt Attaway | Infrastructure work to more intelligently handle FSEvents Prior to this change all file... system events were equal; chown-ing a file was considered the same as changing the content. With this change we: 1) bundle all of the file events into one operation instead or doing it one file at a time 2) ignore any file events that are not create/delete/modify/rename The interfaces are all in place, but the Overseers are still not taking advantage of this information, so there’s no user visible change at this time. (hopefully) Infrastructure only change « |
11 years ago |
| 8686 | Matt Attaway | Swap in new connection dialog There’s still a fair amount of polish to do, but it’s good... enough to replace the old connection dialog. User visible change « |
11 years ago |
| 8684 | Matt Attaway | First steps on the new connection dialog At this point it’s effectively a read only dia...log. Changes made in the text fields are currently ignored. It does look much nicer though. To view it use the appropriately named ‘??????’ menu entry. User visible change « |
11 years ago |
| 8595 | Matt Attaway | WIP on handling connection errors With this change we report the errors to our delegate..., but we don’t attempt to recover. That will come with the next checkin. This change does add in the protocol for handling these errors. User visible change « |
11 years ago |
| 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. « |
11 years ago |
| 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 « |
11 years ago |
| 8569 | Matt Attaway | Rejigger P4Connection to use a standard return type The previous mechanism made it hard... to return anything but error messages. With the P4Message object we can return dictionaries, lists, and messages with a single object. I can use the new object more intelligently, but that’s for another change. I also reorganized the code to separate the ‘p4’ layer off into its own potentially reusable bucket. No functional change. « |
11 years ago |
| 8525 | Matt Attaway | Refactor the Perforce interaction out of the Overseer into a separate class No function...al change, hopefully. This should just simplify the Overseer code and set me up to have a proper place to run Perforce commands. « |
11 years ago |
| 8519 | Matt Attaway | Finally add a connections dialog to manage connections It’s taken a week to figure out... how to manage windows and tabelviews, but this change adds a crude connection dialog to add and remove connections as well as save them out to the preferences file. More to do to make it more sane, but it works for now! « |
11 years ago |
| 8506 | Matt Attaway | Pull model out of controller; disable dock icon No functional change, but the code is m...oderately more sane. This change introduces an Overseer object that is responsible for maintaining one path/Port/User/Client combination. All of the delegation responsibilities move to the Overseer, as does FileSystemWatcher configuration. Overall this just sets me up to actually monitor multiple paths. « |
11 years ago |
| 8504 | Matt Attaway | Add all the APIs!!! This adds in a status bar icon with a pointless menu as well as needl...ess notifications when a file changes in the watched path. While essentially useless, I think I’ve found the APIs for all the major pieces. Now I just need to make them do something useful… « |
11 years ago |
| 8502 | Matt Attaway | Initial checkin of Pulse, a lightweight Perforce client for the Mac This is a sketch of... what a Perforce client inspired by the UX of cloud synchronization software would look like. I’m not trying to build something production worthy yet; at this point I’m just trying to get something up and running as fast as possible so I can play with the UX. At this point I can monitor a directory and kick off ‘p4 info’ calls anytime a file changes. It is the polar opposite of useful. Do note I’ve never written code in Objective-C before. Here be ugly, malformed dragons. « |
11 years ago |