## Wednesday, September 30, 2009

### Quick study

Yesterday I came across a very nice set of quick explanations of what Apple calls "Core competencies." It's very well done, highly recommended and particularly suited to the impatient.

### Writer's block

In my early days with Cocoa (using PyObjC) one of the hardest things to wrap my head around was the byzantine nature of the way you ask the user for a filename to save to (or open). What can be difficult about that?

The function has one of the longest names I've ever seen:

The modal part isn't bad---it just means we'll stop everything else for the user (in that application anyway) until they please answer the <frickin'> question. The modalDelegate and contextInfo can be nil. Great!

The complication came with selectors (what are they?) and how do we get one in Python? Suddenly I had to learn about method signatures and other arcanery when all I wanted to do was save something...

Now, there's a new world: blocks.

The old method is

It is shorter, but WTF? What is that caret-like thing sticking up there? What's with the double parens "))" and all the brackets? That's a block. It's like a Python lambda (section 4.7.5). Also known as a closure. And most informatively: an "anonymous function."

In my code, it looks something like this:

What this:

says (in the Cocoa docs, first example) is the following. When the modal dialog is finished, there will be an integer result that describes which button the user clicked. We are going to pass into the modal dialog handling part of Cocoa a "completionHandler".

What is that? It is a function with no name that we are going to define on the spot. It doesn't return anything (and we can leave that out in our implementation), but it expects an NSInteger argument named result. The next five lines (including the first curly bracket) are the code for our function, followed by another curly bracket that terminates the block, and followed (finally) by a straight bracket that ends the message to the savePanel.

Sneakily, we call the method to actually save the file from within this anonymous function that takes a simple NSInteger and returns nothing.

That's the basic explanation. Blocks are apparently way more useful than that. But this, you have to know.

The function has one of the longest names I've ever seen:

`- (void)beginSheetForDirectory:(NSString *)path file:(NSString *)name modalForWindow:(NSWindow *)docWindow modalDelegate:(id)modalDelegate didEndSelector:(SEL)didEndSelector contextInfo:(void *)contextInfo`

The modal part isn't bad---it just means we'll stop everything else for the user (in that application anyway) until they please answer the <frickin'> question. The modalDelegate and contextInfo can be nil. Great!

The complication came with selectors (what are they?) and how do we get one in Python? Suddenly I had to learn about method signatures and other arcanery when all I wanted to do was save something...

Now, there's a new world: blocks.

The old method is

*deprecated*(that's Cocoa for "it sucks to be you"). The new method defined in the docs is:`- (void)beginSheetModalForWindow:(NSWindow *)window completionHandler:(void (^)(NSInteger result))handler`

It is shorter, but WTF? What is that caret-like thing sticking up there? What's with the double parens "))" and all the brackets? That's a block. It's like a Python lambda (section 4.7.5). Also known as a closure. And most informatively: an "anonymous function."

In my code, it looks something like this:

[savePanel beginSheetModalForWindow:[NSApp mainWindow] |

What this:

`(void (^)(NSInteger result))handler`

says (in the Cocoa docs, first example) is the following. When the modal dialog is finished, there will be an integer result that describes which button the user clicked. We are going to pass into the modal dialog handling part of Cocoa a "completionHandler".

What is that? It is a function with no name that we are going to define on the spot. It doesn't return anything (and we can leave that out in our implementation), but it expects an NSInteger argument named result. The next five lines (including the first curly bracket) are the code for our function, followed by another curly bracket that terminates the block, and followed (finally) by a straight bracket that ends the message to the savePanel.

Sneakily, we call the method to actually save the file from within this anonymous function that takes a simple NSInteger and returns nothing.

That's the basic explanation. Blocks are apparently way more useful than that. But this, you have to know.

### Can I get a date?

### NSDate

I'm pretty sure this is not the official way to do it, but an easy way to extract the year-month-date information from an NSDate instance is to do

`componentsSeparatedByString:@" "`

on the description. Also, notice that constructing an NSDate object from a string requires a complete specification---including the time zone!

And at first I thought, there seems to be a bug in Apple's implementation of the

`dateWithString`

method. We specified January 1, but the resulting NSDate is one day (and one year) earlier. The answer lies in the time zone. Cocoa has converted my GMT time in constructing the NSDate to the current time zone where I am, even correcting for daylight savings time on the appropriate dates.today 2009-09-30 16:05:32 -0400 |

// gcc -o test test3.m -framework Foundation -fobjc-gc-only |

Labels:
command line,
Instant Cocoa

### The number of the beast

As you may have noticed, I get a little bit obsessed. Right now, I'm working hard on Cocoa, next month it'll probably be something else. And I want to use the blog as a way to (in Bill Bumgarner's memorable phrase) "so Google can organize my head." This post is tagged "Instant Cocoa." The idea is to present a short, succinct exploration of some aspect of Cocoa with working code. Now, that code may break in the future, but it seems like a good idea right now.

And a disclaimer: these posts are for someone exactly like me. In fact, they are for me. If you know anything about Cocoa, you are probably wasting your time. But if you're struggling with the documentation and overly complex examples, you've come to the right place.

So I had a couple of questions:

• what 's the difference between the class method and instance method for getting a new number?

• why is there a method for int and also a method for integer?

• I saw a discussion of something funny going on with NSNumber, and I thought I'd explore it. See below.

You can copy and paste the code listing into a text file. Save it and compile it from the command line as indicated. In the first part, we do alloc..init. That means in the classical memory environment (as here b/c we compiled without garbage collection), we own the NSNumber and~~must~~ should release it when we're done with it.

Curiously, this freshly minted NSNumber has a retainCount of 2. I thought we owned it, but it looks like we we're just renting...

After that we get a second NSNumber using the same integer value (1) by the class "convenience" method. This code fails unless we set up the autorelease pool beforehand. Something very wild happens. It has a retainCount of 3, and remarkably, the retainCount of our first NSNumber has also gone up. Can you guess?

We really shouldn't, but let's do a retain on the first number in the second part of the code. Once again, the retainCount of

The last line of the output results from the third section of code. We go through the integers one-by-one until the NSNumbers we get from calls to the class method are different. This happens when i = 13. For 0 through 12 they are identical. It's a baker's dozen.

[blogger is doing weird sh*t with the indentation on my code. Sorry about that. Let me know if something doesn't work for you.] And let me know if you have a better idea about code posting in html.

And a disclaimer: these posts are for someone exactly like me. In fact, they are for me. If you know anything about Cocoa, you are probably wasting your time. But if you're struggling with the documentation and overly complex examples, you've come to the right place.

### NSNumber

NSNumber provides a way of storing a value (the docs say: "a signed or unsigned char, short int, int, long int, long long int, float, or double or a BOOL." You can't do math with these things, but you can store them in an array and write them to disk, very useful indeed. You can also compare them, and get them back out again when you need them.So I had a couple of questions:

• what 's the difference between the class method and instance method for getting a new number?

`+ (NSNumber *)numberWithInteger:(NSInteger)value`

- (id)initWithInteger:(NSInteger)value

• why is there a method for int and also a method for integer?

• I saw a discussion of something funny going on with NSNumber, and I thought I'd explore it. See below.

You can copy and paste the code listing into a text file. Save it and compile it from the command line as indicated. In the first part, we do alloc..init. That means in the classical memory environment (as here b/c we compiled without garbage collection), we own the NSNumber and

Curiously, this freshly minted NSNumber has a retainCount of 2. I thought we owned it, but it looks like we we're just renting...

After that we get a second NSNumber using the same integer value (1) by the class "convenience" method. This code fails unless we set up the autorelease pool beforehand. Something very wild happens. It has a retainCount of 3, and remarkably, the retainCount of our first NSNumber has also gone up. Can you guess?

We really shouldn't, but let's do a retain on the first number in the second part of the code. Once again, the retainCount of

*both*NSNumbers is incremented. What's going on? A peek at the addresses of the objects reveals the magic: they actually are the same thing! Here's the output (stripped of the date/time info from NSLog):n1=1 count=2 |

The last line of the output results from the third section of code. We go through the integers one-by-one until the NSNumbers we get from calls to the class method are different. This happens when i = 13. For 0 through 12 they are identical. It's a baker's dozen.

// gcc -o test test4.m -framework Foundation |

[blogger is doing weird sh*t with the indentation on my code. Sorry about that. Let me know if something doesn't work for you.] And let me know if you have a better idea about code posting in html.

## Tuesday, September 29, 2009

### Cocoa: More about archiving

This post is the result from some more tests I've run on archiving. Some interesting points:

• I'm compiling and running the tests from the command line. I've enabled garbage collection as you can see in the compiler invocation on the first line of the listing.

• The object to be archived is an instance of NSColor. In order to use this class, I need to not only import the AppKit but also

• Just for fun, I get a color from the "Crayons" color list.

• The last example used NSKeyedArchiver, but since we're not using a key, we can just use NSArchiver.

• The interesting part is where the action happens in:

Essentially, the archiver says to the object: encode yourself! Since NSColor conforms to NSCoding, it should (and fortunately, is) able to do that.

• The encoded color is an NSMutableData object, and can now be added to an array and written to a plist file.

Output:

Code listing:

• I'm compiling and running the tests from the command line. I've enabled garbage collection as you can see in the compiler invocation on the first line of the listing.

• The object to be archived is an instance of NSColor. In order to use this class, I need to not only import the AppKit but also

*link against it*. I missed that at first.• Just for fun, I get a color from the "Crayons" color list.

• The last example used NSKeyedArchiver, but since we're not using a key, we can just use NSArchiver.

• The interesting part is where the action happens in:

[archiver encodeObject:maroon]; |

Essentially, the archiver says to the object: encode yourself! Since NSColor conforms to NSCoding, it should (and fortunately, is) able to do that.

• The encoded color is an NSMutableData object, and can now be added to an array and written to a plist file.

Output:

2009-09-29 16:13:04.573 test[1077:10b] color NSCalibratedRGBColorSpace 0.501961 0 0.25098 1 |

Code listing:

// gcc -o test test2.m -framework Foundation -framework AppKit -fobjc-gc-only |

### Cocoa: NSKeyedArchiver

For a Cocoa application, I want to save an NSColor in a plist file on disk. Saving and loading data like strings and NSNumbers from such a file is easy. Just use writeToFile: atomically (or writeToURL: atomically:), and reload the data with arrayWithContentsOfURL:

The Console logs the output (some extra stuff has been stripped out):

However, if you try the same procedure with an array containing things that can't be saved in this way (like NSColor) the file write method fails silently, with no indication of why it failed. You must do something like this:

The actual archiving step is a single line. In this case, however, the array is a mixture of different types. For the archiving step, I can test "if ([[obj class] isEqual:[c class]])", but on unarchiving, I think I have to know which objects need to be unarchived. Cocoa knows what they are, but I don't.

There is probably a better way to keep it all straight. Tell me if you know.

- (void)awakeFromNib { |

The Console logs the output (some extra stuff has been stripped out):

.. ( |

However, if you try the same procedure with an array containing things that can't be saved in this way (like NSColor) the file write method fails silently, with no indication of why it failed. You must do something like this:

- (void)awakeFromNib { |

.. NSCalibratedRGBColorSpace 0 0 1 1 |

The actual archiving step is a single line. In this case, however, the array is a mixture of different types. For the archiving step, I can test "if ([[obj class] isEqual:[c class]])", but on unarchiving, I think I have to know which objects need to be unarchived. Cocoa knows what they are, but I don't.

There is probably a better way to keep it all straight. Tell me if you know.

## Saturday, September 26, 2009

### Cocoa: TableView --- one more thing

Continuing the last post, there is one more thing.

On the question of how to change the Table View programmatically, I finally read the relevant section of the docs, which is titled:

Make the array controller an outlet, then respond to the add button by modifying it like so:

The change will propagate back to the data source automatically. Note that you will have to do a little more fiddling to deal with a multiple selection, or just disable it.

On the question of how to change the Table View programmatically, I finally read the relevant section of the docs, which is titled:

**Programmatically Modifying a Controller’s Contents**Make the array controller an outlet, then respond to the add button by modifying it like so:

NSInteger i; |

The change will propagate back to the data source automatically. Note that you will have to do a little more fiddling to deal with a multiple selection, or just disable it.

### Cocoa: TableView bindings---simplest possible example

This is without doubt the world's simplest NSTableView bindings example. To try it out, create a standard XCode Cocoa application and add the relevant items from this post to it.

The AppDelegate has an init method, which calls another function to load some preliminary data from a plist file. This has to happen before "awakeFromNib" or the TV won't display anything when it launches. I put the data in a plist file in resources for convenience, but you could easily construct it from scratch. I show the scratch version because the plist won't display properly in html:

- (id)init { |

If you wanted to load the data from a plist resource, you would do something like this instead:

- (void)loadArray{ |

The data variable is declared in the header as usual (no getters or setters or @property stuff):

#import <Cocoa/Cocoa.h> |

The AppDelegate also has a method so I can see what has happened to the data source.

- (IBAction)report:(id)sender{ |

That's all the code there is! The window of the running application, again:

In IB, drag an array controller onto the nib:

Here are the bindings. Be sure the table columns are selected when you bind to the array controller.

As shown in the screenshot, there is a Table View with two columns. Editing works, and the + and - buttons add new rows or delete the selected row. Connect the + and - buttons by control drag to the controller, and report to the App Delegate, as usual. Check the connections for the array controller.

Make sure the array controller knows the right class to add to the array:

One thing I don't know how to do yet is to change the default behavior, which only adds at the end, to add a new row after the selected row, say, at the second position. I suppose the way to do that is to connect the buttons to the App Delegate and modify the data source.

## Thursday, September 24, 2009

### Cocoa: sorting an array

I went poking around in the header file "NSArray.h" and found some methods that were new to me.

**• firstObjectCommonWithArray:**

• removeObject:

• exchangeObjectAtIndex: withObjectAtIndex:

• sortedArrayUsingDescriptors:• removeObject:

• exchangeObjectAtIndex: withObjectAtIndex:

• sortedArrayUsingDescriptors:

// gcc -o arrays arraystuff.m -framework Foundation |

.. $ ./arrays |

### Cocoa: strip for NSString

A few weeks ago I was complaining that NSString doesn't have a strip method like I use all the time in Python. I was wrong. It's called stringByTrimmingCharactersInSet:. Here is a bit of code (run from the command line) that exercises three useful NSString functions:

Here is the output:

**• componentsSeparatedByString**

• componentsSeparatedByCharactersInSet

• stringByTrimmingCharactersInSet• componentsSeparatedByCharactersInSet

• stringByTrimmingCharactersInSet

// gcc -o strings stringstuff.m -framework Foundation |

Here is the output:

.. $ ./strings |

### Cocoa: command line arguments

I found myself trying to write a "Foundation tool" that would process a command line argument. It's not really clear to me why I wouldn't use Python to do this, but that's another story. So I wrote the following code in a file "CL1.m" on my Desktop:

Compile like this:

and run from the command line:

I looked at the data directly, because I was (wrongly) using NSLog as shown in the last call, and I wanted to look at the bytes directly. As expected, hex 78 is decimal 7*16 + 8 = 120, which is 'x' in ascii.

However, there is a better way to do this, as discussed in this post. NSUserDefaults will read command line arguments. It works like so:

As discussed in the post, this method is really versatile, it can parse for integers or floats or booleans. (If you try to copy and paste this code, be sure to fix the < symbol in the import statement).

You can get an idea what is in the dictionary by doing this from the command line:

#import <Foundation/Foundation.h> |

Compile like this:

gcc -o CL1 CL1.m -framework Foundation |

and run from the command line:

.. $ ./CL1 xyz |

I looked at the data directly, because I was (wrongly) using NSLog as shown in the last call, and I wanted to look at the bytes directly. As expected, hex 78 is decimal 7*16 + 8 = 120, which is 'x' in ascii.

However, there is a better way to do this, as discussed in this post. NSUserDefaults will read command line arguments. It works like so:

#import <Foundation/Foundation.h> |

.. $ ./CL2 -input xyz |

As discussed in the post, this method is really versatile, it can parse for integers or floats or booleans. (If you try to copy and paste this code, be sure to fix the < symbol in the import statement).

You can get an idea what is in the dictionary by doing this from the command line:

defaults read > ~/Desktop/defaults.txt |

## Monday, September 21, 2009

### More on parabolas

Let's continue with the previous problem. We have the parabola

The slope at any point is 2x. To find the focus, we require the y-value where the slope equals 1, that occurs when

So the focus is at the point:

Now, we want to consider all points x. At every such point

The line from the focus (superimposed in magenta on our old diagram) has the slope at every point of:

Rather than deal explicitly with calculating angles, I'm going to use vectors. There are three of them in this problem. It doesn't matter whether we take the vectors in their forward or reverse directions, so I'll consider IN as

the reverse of the unit vector of light coming in:

The reverse of the vector of light coming out calculated above, and the slope are:

What we are trying to prove is that the angle between OUT (magenta arrow) and M (slope or tangent to the curve at the magenta point) is the same as the angle between IN (blue dotted line) and M.

In vector algebra, the dot product

where the absolute value of the vectors comes from Pythagoras, and θ is the angle between them. In the language of vectors, we claim that the angles for the two vector comparisons are the same, and therefore:

So the left-hand side is just 2x.

The right-hand side looks complicated but it is easily simplified. The numerator is:

The denominator is:

Cancel x

y = x |

The slope at any point is 2x. To find the focus, we require the y-value where the slope equals 1, that occurs when

x = 1/2, y = 1/4 |

So the focus is at the point:

x = 0, y = 1/4 |

Now, we want to consider all points x. At every such point

y = x |

The line from the focus (superimposed in magenta on our old diagram) has the slope at every point of:

(x |

Rather than deal explicitly with calculating angles, I'm going to use vectors. There are three of them in this problem. It doesn't matter whether we take the vectors in their forward or reverse directions, so I'll consider IN as

the reverse of the unit vector of light coming in:

IN = [0,1] |

The reverse of the vector of light coming out calculated above, and the slope are:

OUT = [x, x |

What we are trying to prove is that the angle between OUT (magenta arrow) and M (slope or tangent to the curve at the magenta point) is the same as the angle between IN (blue dotted line) and M.

In vector algebra, the dot product

A • B = Σ A |

where the absolute value of the vectors comes from Pythagoras, and θ is the angle between them. In the language of vectors, we claim that the angles for the two vector comparisons are the same, and therefore:

IN • M / |IN| |M| = OUT • M / |OUT| |M| |

So the left-hand side is just 2x.

The right-hand side looks complicated but it is easily simplified. The numerator is:

x + 2x * (x |

The denominator is:

√ [x |

Cancel x

^{2}+ 1/4 from both top and bottom, leaving 2x, and the identity is verified! There is one more question, however, and that is whether we can generalize this result to*any*parabola. That will have to wait.### Focus on parabolas

In Strang I read that a parabola has a point called the focus.

Imagine that light rays are coming from the stars down a telescope to its reflective mirror, that is, vertically down to the inside surface of a parabola. All such rays are supposed to be reflected to the same point, which is the focus.

For one particular (positive) x, the vertical rays will be reflected along a horizontal line.

In the figure, I plotted a part of the parabola y = x

The solution for this particular point is easy. According to the law of reflection, the angle between the vertical blue line of the incoming ray and the slope line (red) is equal to the angle between the outgoing horizontal blue line and the slope. This happens when the red line has a slope of 1 and the angle (call it θ) is π/4.

At any other point (except x = - 0.5), the angle the vertical line makes with the slope is not π/4 and the outgoing ray is not horizontal. But the claim is that the outgoing ray still passes through the point (0,0.25).

I'm going to see if I can prove that. I'll report back later.

R code:

Imagine that light rays are coming from the stars down a telescope to its reflective mirror, that is, vertically down to the inside surface of a parabola. All such rays are supposed to be reflected to the same point, which is the focus.

For one particular (positive) x, the vertical rays will be reflected along a horizontal line.

In the figure, I plotted a part of the parabola y = x

^{2}, and also its tangent line at the point (0.5,0.25) which has a slope of 1 (2 times x).The solution for this particular point is easy. According to the law of reflection, the angle between the vertical blue line of the incoming ray and the slope line (red) is equal to the angle between the outgoing horizontal blue line and the slope. This happens when the red line has a slope of 1 and the angle (call it θ) is π/4.

At any other point (except x = - 0.5), the angle the vertical line makes with the slope is not π/4 and the outgoing ray is not horizontal. But the claim is that the outgoing ray still passes through the point (0,0.25).

I'm going to see if I can prove that. I'll report back later.

R code:

f <- function(x) { x**2 } |

## Tuesday, September 15, 2009

### Calculus in 5 minutes (last part)

I am unable to resist saying a word or two about how we get the standard method. I can't emphasize enough that you don't need to know this to use calculus! But it might be interesting. Here goes...

Remember:

y = x |

Where does this come from?

Well, what is the slope of the curve at any point x? Imagine that we increase x by a small amount, we'll call that amount h. The slope of the curve is the

*difference*in y [ the value of the function f(x) ], between the two points x and x + h. How much does it change?

Suppose:

y = x |

Well,

(a + b) |

So...

(x + h) |

And there are three quick points:

• (1) The first term x

^{n}is what we need to subtract, it is f(x)

• (2) The third and following terms involve h

^{2}(and higher powers). We

*ignore these terms*!

Suppose h = 10 |

The point is that h

^{2}goes away faster than h as h gets very small, and if you don't think it's getting small fast enough, just choose h to be even smaller...

• (3) What remains is the first term of the binomial expansion:

n x |

To get the slope, we need to divide by h:

slope = n x |

The h / h part is still equal to 1 even when h gets very small. So it goes away!

slope = n x |

There you have it.

As I said, this is for my son. Here is a picture from an earlier time:

Labels:
calculus,
simple math

### Calculus in 5 minutes (part 4)

If you haven't read the earlier posts, they are here, here and here.

Now that was interesting, you say. But how about a little

We want to know the area under the curve.

I know how to do that, you say. Remembering that the curve itself is the derivative of the area function f(x), we have:

That was way too easy. But consider this: how about the area

Notice that we have

I get a little freaked out seeing x as a function of y, so I am going to mentally turn the curve through 90 degrees and then make its mirror image reflection. I get this:

Now, our differentiation trick works for fractional exponents. So we have:

And, as we might hope and expect, 2/3 + 1/3 does equal the area of the unit square. And note that it will work for any power of x. If, for example, we start with the curve y = x

As we guessed, we see that b/c + a/d = 1.

(Of course, it helps that we chose the upper limit for measuring the area at x = 1, y = 1. Evaluation for some other bound would involve a bit more calculation).

Ladies and gentlemen, will you please…give it up for Mr. Leibnitz and Mr. Newton.

[Update: blogger messed with my code. Think I fixed it:]

R code:

Now that was interesting, you say. But how about a little

*proof*? For a mathematician, the word "proof" is like waving the red handkerchief to a bull at Pamplona, but I'm not going there. However, it is always a good idea to check things a bit to see if they make sense. Consider the simple equation:y = x |

We want to know the area under the curve.

I know how to do that, you say. Remembering that the curve itself is the derivative of the area function f(x), we have:

y' = x |

That was way too easy. But consider this: how about the area

*above*the curve?Notice that we have

y = x |

I get a little freaked out seeing x as a function of y, so I am going to mentally turn the curve through 90 degrees and then make its mirror image reflection. I get this:

Now, our differentiation trick works for fractional exponents. So we have:

y' = x |

And, as we might hope and expect, 2/3 + 1/3 does equal the area of the unit square. And note that it will work for any power of x. If, for example, we start with the curve y = x

^{3}, then the first area is 1/4 x^{4}, and the second area is 3/4 x^{4/3}. It's easy to see that it works for any rational power of x. Suppose we have:y' = x |

As we guessed, we see that b/c + a/d = 1.

(Of course, it helps that we chose the upper limit for measuring the area at x = 1, y = 1. Evaluation for some other bound would involve a bit more calculation).

Ladies and gentlemen, will you please…give it up for Mr. Leibnitz and Mr. Newton.

[Update: blogger messed with my code. Think I fixed it:]

R code:

f <- function(x) { return (x**2) } |

Labels:
calculus,
simple math

### Calculus in 5 minutes (part 3)

This is a series about the essence, the merest whiff of the perfume of calculus. The first and second posts are here and here. Differentiation is useful, but integration allows us to do things which are nothing short of miraculous. For example, consider this modestly complex equation, and its curve.

The integral calculus (the second part) allows us to easily calculate the area under this curve (between the curve and the x-axis), as shown in gray.

Remember what we said before: the relationship between the function which we plot as a curve, and its slope at any point is found by differentiating f(x) to f '(x). The slope is f '(x). The secret of integral calculus (don't tell anybody) is that the

If we know f '(x), how do we find f(x)? Sometimes it's easy and sometimes it's hard. Suppose that every time we have a function f(x) and we find f '(x), we write the result down and save it in our little black book. When we encounter a function in an integration problem, we look in the book.

For the example, we need a function f(x), which when differentiated gives:

We look in our book, and there it is:

Of course, the area depends on which endpoints we choose. (Looking at the figure should make this clear). So evaluate the integrated function between the limits x = 7 and x = -5. We have:

I get:

I'm too lazy to finish it. But I'll check the method itself by an interesting approach in the next post.

Why do I say it's a miracle? Because we get the area from the integrated equation just by using the endpoints. We don't have to worry about what lies between. That is amazing.

y = x |

The integral calculus (the second part) allows us to easily calculate the area under this curve (between the curve and the x-axis), as shown in gray.

Remember what we said before: the relationship between the function which we plot as a curve, and its slope at any point is found by differentiating f(x) to f '(x). The slope is f '(x). The secret of integral calculus (don't tell anybody) is that the

*same*relationship holds between the area under a curve, and the curve itself, but in reverse. That is, if the curve is f '(x), the area is f(x). It's that simple.If we know f '(x), how do we find f(x)? Sometimes it's easy and sometimes it's hard. Suppose that every time we have a function f(x) and we find f '(x), we write the result down and save it in our little black book. When we encounter a function in an integration problem, we look in the book.

For the example, we need a function f(x), which when differentiated gives:

y' = x |

We look in our book, and there it is:

y = x |

Of course, the area depends on which endpoints we choose. (Looking at the figure should make this clear). So evaluate the integrated function between the limits x = 7 and x = -5. We have:

7 |

I get:

2401/4 - 343/3 - 49/2 + 1050 - 625/4 + 125/3 - 25/2 - 750 |

I'm too lazy to finish it. But I'll check the method itself by an interesting approach in the next post.

Why do I say it's a miracle? Because we get the area from the integrated equation just by using the endpoints. We don't have to worry about what lies between. That is amazing.

R code: |

Labels:
calculus,
simple math

### Calculus in 5 minutes (part 2)

In the first post of this series I mentioned that a car's odometer and speedometer perform related functions :), and these functions are a good way to think about the fundamental operations of calculus. Suppose a car is going in a straight line (say, on the Bonneville salt flats). We need to deal only with the positive x-axis.

Distance (often labeled s) is a function of time:

s = f(t) |

If the velocity is constant and we start from s = 0 then:

s = v * t |

Distance equals velocity times time. (60 miles per hour for 2 hours = 120 miles).

Now, velocity

*might*be changing, it might be a function of time. Let's say we'll figure out how it changes later, and just write in a general way:

v = f(t) |

If the velocity is changing, we call the rate of change in velocity the acceleration. (It is the slope of the curve for v as a function of t). If the acceleration is constant (like gravity), then:

v = a * t |

For a car, imagine increasing the pressure on the gas pedal steadily so that after 1 second you are going 10 mph, after 2 seconds 20 mph, after 3 seconds 30 mph. If we continue at the same rate, we'll accelerate from 0 to 60 mph in 6 seconds.

As I said before, there is a special trick symbolized with a prime mark placed next to the s (the physicists put a dot on top). The trick is called differentiation:

s' = ... something. |

What it is depends on the exact form of s as a function of time. If the acceleration is constant:

s = 1/2 a t |

Do you remember the rule from last time?

y = c x |

Or, using the time and distance symbols:

s = 1/2 a t |

So that is where the factor of 1/2 comes from in the equation involving acceleration. It is needed to cancel the the 2 that comes out of the exponent when we differentiate. One way to think about this is to say that the velocity after a period of constant acceleration is the

*average*of the initial acceleration and the final acceleration, times the time. But this differentiation mumbo jumbo will work even if the velocity and acceleration are more complicated functions of time.

Labels:
calculus,
simple math

## Sunday, September 13, 2009

### Toolbars in Interface Builder

Making a toolbar for a Cocoa application has become as simple as 1-2-3, with the use of Interface Builder. You just:

**• drag a toolbar onto your window**

• double click it to show "Allowed Toolbar Items"

• drag an "Image Toolbar Item" to the "Allowed Toolbar Items"

• set its Image Name to one present in your project resources

• drag the item from the "Allowed Toolbar Items" to the toolbar (not obvious at first)

• connect it to an IBAction in your controller

• double click it to show "Allowed Toolbar Items"

• drag an "Image Toolbar Item" to the "Allowed Toolbar Items"

• set its Image Name to one present in your project resources

• drag the item from the "Allowed Toolbar Items" to the toolbar (not obvious at first)

• connect it to an IBAction in your controller

I have to confess I fooled around for a while because I didn't find the right Apple docs for this. Once you know how, it is truly painless.

## Thursday, September 10, 2009

### Calculus in 5 minutes (part 1)

### Slope

Here is a post I wrote for my son. I hope he reads it! The essential ideas of calculus are surprisingly simple. See if you don't agree.We can talk about the slope of a curve

*at a single point*. This seems odd because "slope" refers to a change in y divided by a change in x. We ought to need two points, not just one. But we don't.

A single point can have a slope for the same reason that the earth seems to be flat where I'm standing right now even though I know it is curved---

*it is flat*, on the ocean or the Mohave desert anyway. The carpenters who built your house assumed that the earth's curvature is negligible, and we will too. We can mentally zoom in indefinitely (ask an ant if the earth is flat).

So for any given point on a curve, we can always find another point very close nearby which has the same slope, and then we know the slope between them is constant (within any limits you want to establish).

### Like driving a car

You can understand the basic procedures in calculus by thinking about driving a car (Strang). Most drivers refer frequently to the speedometer (measures velocity), if they're measuring distance they refer to the odometer.If we plot accumulated distance as a function of time, the slope of that curve is the velocity shown on the speedometer. [This analogy will become useful in part 2].

### Simple tricks

There are tricks to use to find the slope from the equation for a curve. Where the tricks come from isn't hard to understand, but it's not necessary---just use the trick. Consider the equation:(y-1) = (x-2) |

Multiply it out to make things a bit more interesting:

y = x |

The trick is that the slope of the curve (designated as y') is easily calculated:

y = x |

We used three rules together:

(i) if we have various parts being added together, we take the slope for each part separately and then add them up.

(ii) the slope of a constant term (like y = 3) is zero (obviously, a horizontal line is flat, and has slope = 0).

(iii) if (c stands for constant):

y = c x |

### So what

One reason this is useful is to find maximum and minimum points of a curve. These are points at which*the slope is zero*. For our example

y' = 2x - 4 |

This happens when

y = x |

This is easy to see by going back to the first form of the equation. The minimum is when the term in parentheses on the right is zero.

(y-1) = (x-2) |

There are other simple tricks for terms like 2

^{x}and sin x.

R code:

f <- function(x) { x**2 - 4*x + 5} |

Labels:
calculus,
simple math

## Tuesday, September 8, 2009

### Heat Mapper rises from the ashes

This is the second of two posts about Apple-specific programming issues, so feel free to move on if you don't care about both subjects. I spent the labor day weekend re-doing my program to draw heat maps in Objective-C, and finally have a minimally functional version.

As usual, most of the time was wasted running down stupid errors, but I seem to be getting a little better about recognizing them. One of these had to do with a call like:

IBOutlet id myController; |

in a header file. This only works if said file is in the "Classes" section of Xcode. If it's in "Resources," as happened once by mistake, there is an error message from the compiler because the IB cannot actually connect to the outlet.

But the biggest time-waster (and probably the silliest bug) was caused by using spaces (long ago) to pad the the row names in the sample data which I feed to the application. It makes the text version look prettier (tabs don't always line up), as you can see in this sample without ljust:

DB DC DM DA |

The problem came when I used a dictionary with genus names as keys to specify colors to draw the strings. The names I read from the data file were padded out to the length of the longest one:

"bacteroidales" |

So the key lookup failed when searching for the second key

*but not for the first*. It kinda worked… I spent at least 10 hours on this. Since writing code is laborious in Objective-C, writing testing code is also laborious.

On the other hand, the bug is solved, and if it ever comes again I hope to recognize the issue. Of course, if NSString had a strip method I would have used it it automatically as I do in Python, and it never would have happened.

## Friday, September 4, 2009

### Goodbye to all that

This post is about Apple-specific programming issues, so feel free to move on if you don't care about both subjects. Perhaps the title is premature, and it is certainly melodramatic. But my recent upgrade to Snow Leopard broke my programs written using the PyObjC bridge (like HeatMapper), and what it looks like to me is that PyObjC is headed for the ash heap of history.

That pisses me off. The advantage of doing what I have been doing is to get a shiny GUI almost for free. Now comes the hurt, everything has to be redone, no matter what. If I have to

What happened: the app failed to launch, but that was no big surprise. Upgrade and s**t happens. So I go to XCode (the latest, v 3.2), and try to re-compile the project.

..._bridgesupport.py", line 53, in _parseBridgeSupport |

This happens when I do "import Foundation", which works, by the way, from the command line. I am suspicious, because Snow Leopard is not such a simple upgrade. 64-bit is wild. (Read Ars Technica).

But that's fine, I say, I can just fix what's wrong. So first I need a working PyObjC application. I go to create a new Project, but it turns out the templates for PyObjC stuff are no longer included in XCode.

You'll need to download and install the templates from the PyObjC repository or web site.

The templates were pulled from the release because the template development moves at a different pace & schedule than the Xcode releases. Too often, the templates have been out of date by the time the discs were pressed.

b.bum

No problem, I say, I'll just download the templates...

svn checkout http://svn.red-bean.com/pyobjc/trunk/pyobjc/pyobjc-xcode/Project%20Templates/ |

Follow the instructions in the readme...Look in XCode: there is a new thingie called User Templates. Make a new project using the template...it dies with the

**same**error.

So I google: "leopard ValueError: Unknown typestr" and I find this:

As the maintainer of PyObjC for nearly 15 years, I will say it bluntly. Use Objective-C. You will need to know Objective-C to really understand Cocoa anyway and PyObjC is just going to add a layer of bugs & issues that are alien to 99% of Cocoa programmers.

– bbum 2 days ago

Can't get any more blunt than that. And I find this:

To be blunt:It is early days yet for Snow Leopard. Maybe it'll get fixed. You have to understand: Bill Bumgarner is the man. Well, him and Ronald Oussoren.

If you want to be an effective Cocoa programmer, you must learn Objective-C. End of story.

Neither Python or Ruby are a substitute for Objective-C via their respective bridges. You still have to understand the Objective-C APIs, the behaviors inherent to NSObject derived classes, and many other details of Cocoa.

PyObjC and RubyCocoa are a great way to access Python or Ruby functionality from a Cocoa application, including building a Cocoa application mostly -- if not entirely -- in Python or Ruby. But success therein is founded upon a thorough understanding of Cocoa and the Objective-C APIs it is composed of.

b.bum

So what it looks like is that:

• Python is great on the Mac---from the command line

• PyObjC

*was*fun, and great for the amateur programmer

• but, it was basically a complicated hack (thanks Bill and Ronald)

• I should follow bbum's advice and learn Objective C (it'll take time)

• you cannot depend on PyObjC to get you to Cocoa

• in the meanwhile, I am going to make my graphics with SVG

One bonus of this, of course, is that it'll be useful for people with PCs. But I think it's a sad day. Apple should think more about people who play on their computers but are not (smart enough or don't have the time to be) experts.

## Thursday, September 3, 2009

### More on the three-fold way

A while ago I posted about what seems to be a simple calculus problem---to find the area of a circle by integration. In fact we looked at three ways, and two were easy. But the first way is harder, and that involves y as a function of x with the goal to integrate y(x) from x = -R to x = R. At the time, I solved the problem by numerical integration.

The function I could not integrate is

y = √(R |

or sticking with a unit circle:

y = √(1 - x |

Reading further in Strang's

*Calculus*, I find that there

*is*a way to do it. The method has two parts: (i) a trigonometric substitution and (ii) integration by parts, which is a reversal of the product rule for differentiation.

### Integration by parts

If we have two functions of x, u and v, and we want d/dx of uv, by the product rule we get:

d/dx uv = u dv/dx + v du/dx |

Thinking about integrating this (without the x's):

uv = ∫u dv + ∫v du |

So the trick is, when given a difficult integral, to try to imagine it transformed into ∫u dv. If ∫v du is easy or just easier, we have helped ourselves. Suppose we have:

∫cos |

Then let

u = cos x |

And a trick:

∫cos |

And another trick!:

2 ∫cos |

Amazing. And:

∫sin |

### The "double angle" method

I quoted Strang the other day that:

sin(s + t) = sin s cos t + cos s sin t |

These formulas lead to a pretty straightforward derivation of the integral of

cos

^{2}t (happily, we get the same result as above):

if s = t then we have:

sin 2t = 2 sin t cos t |

Substitute:

1 - sin |

We can integrate that easily:

∫sin |

and

∫cos |

But wait, we haven't solved the problem. We want to integrate:

dy = √(1 - x |

substitute

x = sin θ |

then we have

y = ∫ √(1 - sin |

change back to x

y = 1/2 [ sin |

(Notice it's the inverse sine). Now, evaluate between x = 0 and x = 1:

y = 1/2[ π/2 + 0 - 0 - 0] = π / 4 |

I still haven't worked out the R

^{2}part.

## Wednesday, September 2, 2009

### Quadratic formula

I have one last post on the topic of "simple math." The quadratic equation which we can use to find the roots of an equation like:

is well-known to anyone who has studied algebra. It is:

So where does this come from? As detailed in the wikipedia entry, it comes from the method of "completing the square." The idea is that if we can transform the first equation above to:

Then the left-hand side is

If we take the square root of the right side and subtract h, we've solved for x. The first step is to divide by a (which is non-zero or we wouldn't be bothering with this) and move the constant part to the right side:

So the h we are looking for is:

We need to add h

Express the right side as a single fraction

Take square roots and isolate x:

As quoted in the wikipedia entry:

(Brahmasphutasiddhanta (Colebrook translation, 1817, page 346)

I am puzzled by the little problem of the sign of the term 4ac in this quoted version. [UPDATE: I see. <Bonks self on head> They just set up the equation with c on the right-hand side to start with]

ax |

is well-known to anyone who has studied algebra. It is:

[ -b +/- √(b |

So where does this come from? As detailed in the wikipedia entry, it comes from the method of "completing the square." The idea is that if we can transform the first equation above to:

x |

Then the left-hand side is

(x + h) |

If we take the square root of the right side and subtract h, we've solved for x. The first step is to divide by a (which is non-zero or we wouldn't be bothering with this) and move the constant part to the right side:

x |

So the h we are looking for is:

h = b/2a |

We need to add h

^{2}, like so:x |

Express the right side as a single fraction

(x + b/2a) |

Take square roots and isolate x:

x + b/2a = +/- √(b |

As quoted in the wikipedia entry:

To the absolute number multiplied by four times the [coefficient of the] square, add the square of the [coefficient of the] middle term; the square root of the same, less the [coefficient of the] middle term, being divided by twice the [coefficient of the] square is the value.--Brahmagupta

(Brahmasphutasiddhanta (Colebrook translation, 1817, page 346)

I am puzzled by the little problem of the sign of the term 4ac in this quoted version. [UPDATE: I see. <Bonks self on head> They just set up the equation with c on the right-hand side to start with]

## Tuesday, September 1, 2009

### And finally about e

I have one last post about e. For the previous ones, see here, here, here, here, here and here.

I'm almost done. In fact the best advice I have for you is to get the online version of Strang's

In the last post we came to:

and flipping things around to look at x as a function of y:

It turns out that the constant c = log

In this case, y(x) = log

At the particular value x = 1:

If we substitute n = 1/h

The part in the brackets is e:

There are other definitions in the book, but this one about e as the limit of an infinite series is certainly fundamental. In exactly the same way we can develop:

and this will give us the famous series for e

I'm almost done. In fact the best advice I have for you is to get the online version of Strang's

*Calculus*, (or better yet, buy your own copy), and read Chapter 6.In the last post we came to:

y = b |

and flipping things around to look at x as a function of y:

x = log |

It turns out that the constant c = log

_{b}e, and then of course, c = 1 when b = e. We can get an expression for that. Since I get a little freaked out looking at dx/dy, let's express the log function in the normal way, where y = log_{b}x. So now we want dy/dx. As before, call Δx, the small change in x, h, then:dy/dx lim(h->0) [y(x+h) - y(x) ] / h] |

In this case, y(x) = log

_{b}x so we wantdy/dx = lim(h->0) [ log |

At the particular value x = 1:

dy/dx = lim(h->0) [ log |

If we substitute n = 1/h

= lim(h->0) log |

The part in the brackets is e:

e = (1+1/n) |

There are other definitions in the book, but this one about e as the limit of an infinite series is certainly fundamental. In exactly the same way we can develop:

e |

and this will give us the famous series for e

^{x}(although to be honest I am still confused about how that works):
Subscribe to:
Posts (Atom)