jordan
/
procmon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix relative links

Browse Source
master
Jordan Orelli 8 years ago
parent c55d2d5f05
commit e9e68e8dd6
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File

14
README.md
Unescape Escape View File

@ -29,7 +29,7 @@ debugging and learning purposes.
## construction ## construction
[`procmon.go`](blob/master/procmon.go) is the single Go file of interest to the [`procmon.go`](procmon.go) is the single Go file of interest to the
Go toolchain. Go toolchain.
### triggering the cgo generation and link step ### triggering the cgo generation and link step
@ -60,7 +60,7 @@ The other lines in this comment, that is, the lines that do _not_ begin with
project, that is just one line: the line that includes `procmon.h`, the header project, that is just one line: the line that includes `procmon.h`, the header
file for the C code that we want to access. file for the C code that we want to access.
Down [in the Go program's `main` function](blob/master/procmon.go#L50), we spawn a goroutine to listen on a Down [in the Go program's `main` function](procmon.go#L50), we spawn a goroutine to listen on a
channel for changes: channel for changes:
```go ```go
@ -97,7 +97,7 @@ void MonitorProcesses();
The cgo toolchain automatically associated `procmon.c` with our header file The cgo toolchain automatically associated `procmon.c` with our header file
`procmon.h` that we imported in our cgo import comment. [The implementation of `procmon.h` that we imported in our cgo import comment. [The implementation of
the `MonitorProcesses` function appears in the `MonitorProcesses` function appears in
`procmon.c`](blob/3767628a0e24c6bccd463a2616f7f5226d4e1c9c/procmon.c#L5): `procmon.c`](procmon.c#L5):
```obj-c ```obj-c
void MonitorProcesses() { void MonitorProcesses() {
@ -108,7 +108,7 @@ void MonitorProcesses() {
This function does two things: it starts by accessing a singleton of our This function does two things: it starts by accessing a singleton of our
Objective-C class `ProcWatcher` (that's `[ProcWatcher shared]`, which is defined Objective-C class `ProcWatcher` (that's `[ProcWatcher shared]`, which is defined
[here](blob/3767628a0e24c6bccd463a2616f7f5226d4e1c9c/ProcWatcher.m#L6)) and [here](ProcWatcher.m#L6)) and
invoking its `startWatching` method. This subscribes our `ProcWatcher` instance invoking its `startWatching` method. This subscribes our `ProcWatcher` instance
to OS notifications. We'll come back to how the ProcWatcher subscribes to to OS notifications. We'll come back to how the ProcWatcher subscribes to
events in a bit. events in a bit.
@ -138,7 +138,7 @@ infrastructure, and it prevents our program from terminating.
#### back to observing NSNotifications #### back to observing NSNotifications
[The `startWatching` [The `startWatching`
method](blob/3767628a0e24c6bccd463a2616f7f5226d4e1c9c/ProcWatcher.m#L6) method](ProcWatcher.m#L6)
accesses the current OSX user's accesses the current OSX user's
[`NSWorkspace`](https://developer.apple.com/reference/appkit/nsworkspace). The [`NSWorkspace`](https://developer.apple.com/reference/appkit/nsworkspace). The
`NSWorkspace` handle allows us to hook into `NSWorkspace` handle allows us to hook into
@ -170,7 +170,7 @@ The notable feature here is: we pass a callback to our notification center, and
within that callback, we invoke a curious function: `AppStarted`. That function within that callback, we invoke a curious function: `AppStarted`. That function
isn't defined anywhere in our C or Objective-C code: it's defined [in our isn't defined anywhere in our C or Objective-C code: it's defined [in our
original Go file original Go file
`procmon.go`](blob/3767628a0e24c6bccd463a2616f7f5226d4e1c9c/procmon.go#L28-L31): `procmon.go`](procmon.go#L28-L31):
```go ```go
//export AppStarted //export AppStarted
@ -196,7 +196,7 @@ by so quickly, but it's there, and it's on disk when our C code gets compiled.
In order to access those definitions from our C code, our C code has to import In order to access those definitions from our C code, our C code has to import
this fleeting header file. In this project, that inclusion happens in this fleeting header file. In this project, that inclusion happens in
`ProcWatcher.m` `ProcWatcher.m`
[here](blob/3767628a0e24c6bccd463a2616f7f5226d4e1c9c/ProcWatcher.m#L1), which [here](ProcWatcher.m#L1), which
looks like this: looks like this:
```c ```c

Write Preview
Loading…
Cancel
Save