Cappuccino has up till now used string paths instead of actual URL
objects like Cocoa. With the following commits this has changed:
http://github.com/280north/cappuccino/commit/98df1859af444ca4c3bbc9864164a7f5e3128dce
http://github.com/280north/cappuccino/commit/4f1d9fe83640efdb8b7bd2395771d6dc2d038a9d
http://github.com/280north/cappuccino/commit/a32368f89a007d94c282e9f01706395d6c79767e
http://github.com/280north/cappuccino/commit/c8ed0f543665a7bb686c31369841d4208c996af8
I believe I have made all the appropriate changes, but if you run into
any errors with your code that uses URLs, please let me know. In
theory, this change should be somewhat if not completely transparent,
as the main input for URLs, CPURLRequest, is "nice" and auto converts
string paths to URLs for you:
[CPURLRequest requestWithURL:[CPURL URLWithString:@"http://
something.com"]]
is equivalent to
[CPURLRequest requestWithURL:@"
http://something.com"]
CPURL is still not completely finished, but it should help out
greatly. For example, if should make it much easier to compare URLs ("/
x" may be the same as "whereveriam/x"). It also makes it easy to get
at parameters like scheme, protocol, query string, etc.