I’ve decided to close my Twitter account. William Van Hecke makes a convincing case"))
61 | }
62 | }
63 |
64 | XCTAssertTrue(didFindTwitterQuitterArticle)
65 | }
66 |
67 | func testPixelEnvy() {
68 |
69 | let d = parserData("pxlnv", "json", "http://pxlnv.com/")
70 | let parsedFeed = try! FeedParser.parse(d)!
71 | XCTAssertEqual(parsedFeed.items.count, 20)
72 |
73 | }
74 |
75 | func testRose() {
76 | let d = parserData("rose", "json", "http://www.rosemaryorchard.com/")
77 | let parsedFeed = try! FeedParser.parse(d)!
78 | XCTAssertEqual(parsedFeed.items.count, 84)
79 | }
80 |
81 | func test3960() {
82 | let d = parserData("3960", "json", "http://journal.3960.org/")
83 | let parsedFeed = try! FeedParser.parse(d)!
84 | XCTAssertEqual(parsedFeed.items.count, 20)
85 | XCTAssertEqual(parsedFeed.language, "de-DE")
86 |
87 | for item in parsedFeed.items {
88 | XCTAssertEqual(item.language, "de-DE")
89 | }
90 | }
91 |
92 | func testAuthors() {
93 | let d = parserData("authors", "json", "https://example.com/")
94 | let parsedFeed = try! FeedParser.parse(d)!
95 | XCTAssertEqual(parsedFeed.items.count, 4)
96 |
97 | let rootAuthors = Set([
98 | ParsedAuthor(name: "Root Author 1", url: nil, avatarURL: nil, emailAddress: nil),
99 | ParsedAuthor(name: "Root Author 2", url: nil, avatarURL: nil, emailAddress: nil)
100 | ])
101 | let itemAuthors = Set([
102 | ParsedAuthor(name: "Item Author 1", url: nil, avatarURL: nil, emailAddress: nil),
103 | ParsedAuthor(name: "Item Author 2", url: nil, avatarURL: nil, emailAddress: nil)
104 | ])
105 | let legacyItemAuthors = Set([
106 | ParsedAuthor(name: "Legacy Item Author", url: nil, avatarURL: nil, emailAddress: nil)
107 | ])
108 |
109 | XCTAssertEqual(parsedFeed.authors?.count, 2)
110 | XCTAssertEqual(parsedFeed.authors, rootAuthors)
111 |
112 | let noAuthorsItem = parsedFeed.items.first { $0.uniqueID == "Item without authors" }!
113 | XCTAssertEqual(noAuthorsItem.authors, nil)
114 |
115 | let legacyAuthorItem = parsedFeed.items.first { $0.uniqueID == "Item with legacy author" }!
116 | XCTAssertEqual(legacyAuthorItem.authors, legacyItemAuthors)
117 |
118 | let modernAuthorsItem = parsedFeed.items.first { $0.uniqueID == "Item with modern authors" }!
119 | XCTAssertEqual(modernAuthorsItem.authors, itemAuthors)
120 |
121 | let bothAuthorsItem = parsedFeed.items.first { $0.uniqueID == "Item with both" }!
122 | XCTAssertEqual(bothAuthorsItem.authors, itemAuthors)
123 | }
124 |
125 | func testExtensions() {
126 | let d = parserData("jsonfeed-extension", "json", "https://example.com/")
127 | let parsedFeed = try! FeedParser.parse(d)!
128 |
129 | XCTAssertEqual(parsedFeed.extensions?.count, 1)
130 |
131 | let nonexistentExtension = parsedFeed.extensions?["_nonexistent"]
132 | XCTAssertNil(nonexistentExtension)
133 |
134 | let feedExtension = parsedFeed.extensions!["_contoso"]!
135 | XCTAssertEqual(feedExtension.name, "_contoso")
136 |
137 | // Test content access
138 | XCTAssertEqual(feedExtension["about"], "Contoso JSON feed extension. There is actually no such extension in real life. This file just tests if the JSONFeed parser can parse a feed with JSON Feed extensions.")
139 | XCTAssertEqual(feedExtension["someNumber"], 42)
140 | XCTAssertEqual(feedExtension["someBool"], true)
141 | XCTAssertEqual(feedExtension["someString"], "Hello Contoso")
142 |
143 | let chronologicalItems = parsedFeed.items.sorted { $0.datePublished! > $1.datePublished! }
144 |
145 | let itemExtension = chronologicalItems[0].extensions!["_contoso"]!
146 | XCTAssertEqual(itemExtension.name, "_contoso")
147 | XCTAssertEqual(itemExtension["someKey"], "SomeValue2")
148 | XCTAssertEqual(itemExtension["someBoolKey"], true)
149 | XCTAssertEqual(itemExtension["anotherKey"], "AnotherValue2")
150 |
151 | XCTAssertEqual(itemExtension["someKey"], "SomeValue2")
152 |
153 | let secondItemExtension = chronologicalItems[1].extensions!["_contoso"]!
154 | XCTAssertEqual(secondItemExtension["someBoolKey"], false)
155 | XCTAssertEqual(secondItemExtension["someIntKey"], 43)
156 |
157 | let thirdItemExtensions = chronologicalItems[2].extensions
158 | XCTAssertNil(thirdItemExtensions)
159 | }
160 | }
161 |
--------------------------------------------------------------------------------
/Tests/RSParserTests/OPMLTests.swift:
--------------------------------------------------------------------------------
1 | //
2 | // OPMLTests.swift
3 | // RSParser
4 | //
5 | // Created by Brent Simmons on 6/25/17.
6 | // Copyright © 2017 Ranchero Software, LLC. All rights reserved.
7 | //
8 |
9 | import XCTest
10 | import RSParser
11 | import RSParserObjC
12 |
13 | class OPMLTests: XCTestCase {
14 |
15 | let subsData = parserData("Subs", "opml", "http://example.org/")
16 |
17 | func testOPMLParsingPerformance() {
18 |
19 | // 0.002 sec on my 2012 iMac.
20 | self.measure {
21 | let _ = try! RSOPMLParser.parseOPML(with: self.subsData)
22 | }
23 | }
24 |
25 | func testNotOPML() {
26 |
27 | let d = parserData("DaringFireball", "rss", "http://daringfireball.net/")
28 | XCTAssertThrowsError(try RSOPMLParser.parseOPML(with: d))
29 | }
30 |
31 | func testSubsStructure() {
32 | let opmlDocument = try! RSOPMLParser.parseOPML(with: subsData)
33 | XCTAssertEqual("Subs", opmlDocument.title)
34 | XCTAssertEqual("http://example.org/", opmlDocument.url)
35 | recursivelyCheckOPMLStructure(opmlDocument)
36 | }
37 |
38 |
39 | func testFindingTitles() {
40 | // https://github.com/brentsimmons/NetNewsWire/issues/527
41 | // Fix a bug where titles aren’t found when there’s no title attribute in the OPML,
42 | // which appears to be true with OPML generated by The Old Reader.
43 |
44 | let d = parserData("SubsNoTitleAttributes", "opml", "http://example.org/")
45 | let opmlDocument = try! RSOPMLParser.parseOPML(with: d)
46 | recursivelyCheckOPMLStructure(opmlDocument)
47 | }
48 |
49 | }
50 |
51 | private extension OPMLTests {
52 |
53 | func recursivelyCheckOPMLStructure(_ item: RSOPMLItem) {
54 | let feedSpecifier = item.feedSpecifier
55 | if !(item is RSOPMLDocument) {
56 | XCTAssertNotNil((item.attributes! as NSDictionary).opml_text)
57 | }
58 |
59 | // If it has no children, it should have a feed specifier. The converse is also true.
60 | var isFolder = item.children != nil && item.children!.count > 0
61 | if !isFolder && (item.attributes! as NSDictionary).opml_title == "Skip" {
62 | isFolder = true
63 | }
64 |
65 | if !isFolder {
66 | XCTAssertNotNil(feedSpecifier!.title)
67 | XCTAssertNotNil(feedSpecifier!.feedURL)
68 | }
69 | else {
70 | XCTAssertNil(feedSpecifier)
71 | }
72 |
73 | if item.children != nil && item.children!.count > 0 {
74 | for oneItem in item.children! {
75 | recursivelyCheckOPMLStructure(oneItem)
76 | }
77 | }
78 | }
79 | }
80 |
--------------------------------------------------------------------------------
/Tests/RSParserTests/RSDateParserTests.swift:
--------------------------------------------------------------------------------
1 | //
2 | // RSDateParserTests.swift
3 | //
4 | //
5 | // Created by Maurice Parker on 4/1/21.
6 | //
7 |
8 | import Foundation
9 | import XCTest
10 | import RSParser
11 |
12 | class RSDateParserTests: XCTestCase {
13 |
14 | static func dateWithValues(_ year: Int, _ month: Int, _ day: Int, _ hour: Int, _ minute: Int, _ second: Int, _ milliseconds: Int = 0) -> Date {
15 | var dateComponents = DateComponents()
16 | dateComponents.calendar = Calendar.current
17 | dateComponents.timeZone = TimeZone(secondsFromGMT: 0)
18 |
19 | dateComponents.year = year
20 | dateComponents.month = month
21 | dateComponents.day = day
22 | dateComponents.hour = hour
23 | dateComponents.minute = minute
24 | dateComponents.second = second
25 | dateComponents.nanosecond = milliseconds * 1000000
26 |
27 | return dateComponents.date!
28 | }
29 |
30 | func testDateWithString() {
31 | var expectedDateResult = Self.dateWithValues(2010, 5, 28, 21, 3, 38)
32 |
33 | var d = RSDateWithString("Fri, 28 May 2010 21:03:38 +0000")
34 | XCTAssertEqual(d, expectedDateResult)
35 |
36 | d = RSDateWithString("Fri, 28 May 2010 21:03:38 +00:00")
37 | XCTAssertEqual(d, expectedDateResult)
38 |
39 | d = RSDateWithString("Fri, 28 May 2010 21:03:38 -00:00")
40 | XCTAssertEqual(d, expectedDateResult)
41 |
42 | d = RSDateWithString("Fri, 28 May 2010 21:03:38 -0000")
43 | XCTAssertEqual(d, expectedDateResult)
44 |
45 | d = RSDateWithString("Fri, 28 May 2010 21:03:38 GMT")
46 | XCTAssertEqual(d, expectedDateResult)
47 |
48 | d = RSDateWithString("2010-05-28T21:03:38+00:00")
49 | XCTAssertEqual(d, expectedDateResult)
50 |
51 | d = RSDateWithString("2010-05-28T21:03:38+0000")
52 | XCTAssertEqual(d, expectedDateResult)
53 |
54 | d = RSDateWithString("2010-05-28T21:03:38-0000")
55 | XCTAssertEqual(d, expectedDateResult)
56 |
57 | d = RSDateWithString("2010-05-28T21:03:38-00:00")
58 | XCTAssertEqual(d, expectedDateResult)
59 |
60 | d = RSDateWithString("2010-05-28T21:03:38Z")
61 | XCTAssertEqual(d, expectedDateResult)
62 |
63 | expectedDateResult = Self.dateWithValues(2010, 7, 13, 17, 6, 40)
64 | d = RSDateWithString("2010-07-13T17:06:40+00:00")
65 | XCTAssertEqual(d, expectedDateResult)
66 |
67 | expectedDateResult = Self.dateWithValues(2010, 4, 30, 12, 0, 0)
68 | d = RSDateWithString("30 Apr 2010 5:00 PDT")
69 | XCTAssertEqual(d, expectedDateResult)
70 |
71 | expectedDateResult = Self.dateWithValues(2010, 5, 21, 21, 22, 53)
72 | d = RSDateWithString("21 May 2010 21:22:53 GMT")
73 | XCTAssertEqual(d, expectedDateResult)
74 |
75 | expectedDateResult = Self.dateWithValues(2010, 6, 9, 5, 0, 0)
76 | d = RSDateWithString("Wed, 09 Jun 2010 00:00 EST")
77 | XCTAssertEqual(d, expectedDateResult)
78 |
79 | expectedDateResult = Self.dateWithValues(2010, 6, 23, 3, 43, 50)
80 | d = RSDateWithString("Wed, 23 Jun 2010 03:43:50 Z")
81 | XCTAssertEqual(d, expectedDateResult)
82 |
83 | expectedDateResult = Self.dateWithValues(2010, 6, 22, 3, 57, 49)
84 | d = RSDateWithString("2010-06-22T03:57:49+00:00")
85 | XCTAssertEqual(d, expectedDateResult)
86 |
87 | expectedDateResult = Self.dateWithValues(2010, 11, 17, 13, 40, 07)
88 | d = RSDateWithString("2010-11-17T08:40:07-05:00")
89 | XCTAssertEqual(d, expectedDateResult)
90 | }
91 |
92 | func testAtomDateWithMissingTCharacter() {
93 | let expectedDateResult = Self.dateWithValues(2010, 11, 17, 13, 40, 07)
94 | let d = RSDateWithString("2010-11-17 08:40:07-05:00")
95 | XCTAssertEqual(d, expectedDateResult)
96 | }
97 |
98 | func testFeedbinDate() {
99 | let expectedDateResult = Self.dateWithValues(2019, 9, 27, 21, 01, 48)
100 | let d = RSDateWithString("2019-09-27T21:01:48.000000Z")
101 | XCTAssertEqual(d, expectedDateResult)
102 | }
103 |
104 | func testHighMillisecondDate() {
105 | let expectedDateResult = Self.dateWithValues(2021, 03, 29, 10, 46, 56, 516)
106 | let d = RSDateWithString("2021-03-29T10:46:56.516941+00:00")
107 | XCTAssertEqual(d!.timeIntervalSince1970, expectedDateResult.timeIntervalSince1970, accuracy: 0.000001)
108 | }
109 | }
110 |
--------------------------------------------------------------------------------
/Tests/RSParserTests/RSSInJSONParserTests.swift:
--------------------------------------------------------------------------------
1 | //
2 | // RSSInJSONParserTests.swift
3 | // RSParser
4 | //
5 | // Created by Brent Simmons on 6/26/17.
6 | // Copyright © 2017 Ranchero Software, LLC. All rights reserved.
7 | //
8 |
9 | import XCTest
10 | import RSParser
11 |
12 | class RSSInJSONParserTests: XCTestCase {
13 |
14 | func testScriptingNewsPerformance() {
15 |
16 | // 0.003 sec on my 2012 iMac.
17 | let d = parserData("ScriptingNews", "json", "http://scripting.com/")
18 | self.measure {
19 | let _ = try! FeedParser.parse(d)
20 | }
21 | }
22 |
23 | func testFeedLanguage() {
24 | let d = parserData("ScriptingNews", "json", "http://scripting.com/")
25 | let parsedFeed = try! FeedParser.parse(d)!
26 | XCTAssertEqual(parsedFeed.language, "en-us")
27 | }
28 | }
29 |
--------------------------------------------------------------------------------
/Tests/RSParserTests/RSSParserTests.swift:
--------------------------------------------------------------------------------
1 | //
2 | // RSSParserTests.swift
3 | // RSParser
4 | //
5 | // Created by Brent Simmons on 6/26/17.
6 | // Copyright © 2017 Ranchero Software, LLC. All rights reserved.
7 | //
8 |
9 | import XCTest
10 | import RSParser
11 |
12 | class RSSParserTests: XCTestCase {
13 |
14 | func testScriptingNewsPerformance() {
15 |
16 | // 0.004 sec on my 2012 iMac.
17 | let d = parserData("scriptingNews", "rss", "http://scripting.com/")
18 | self.measure {
19 | let _ = try! FeedParser.parse(d)
20 | }
21 | }
22 |
23 | func testKatieFloydPerformance() {
24 |
25 | // 0.004 sec on my 2012 iMac.
26 | let d = parserData("KatieFloyd", "rss", "http://katiefloyd.com/")
27 | self.measure {
28 | let _ = try! FeedParser.parse(d)
29 | }
30 | }
31 |
32 | func testEMarleyPerformance() {
33 |
34 | // 0.001 sec on my 2012 iMac.
35 | let d = parserData("EMarley", "rss", "https://medium.com/@emarley")
36 | self.measure {
37 | let _ = try! FeedParser.parse(d)
38 | }
39 | }
40 |
41 | func testMantonPerformance() {
42 |
43 | // 0.002 sec on my 2012 iMac.
44 | let d = parserData("manton", "rss", "http://manton.org/")
45 | self.measure {
46 | let _ = try! FeedParser.parse(d)
47 | }
48 | }
49 |
50 | func testNatashaTheRobot() {
51 |
52 | let d = parserData("natasha", "xml", "https://www.natashatherobot.com/")
53 | let parsedFeed = try! FeedParser.parse(d)!
54 | XCTAssertEqual(parsedFeed.items.count, 10)
55 | }
56 |
57 | func testTheOmniShowAttachments() {
58 |
59 | let d = parserData("theomnishow", "rss", "https://theomnishow.omnigroup.com/")
60 | let parsedFeed = try! FeedParser.parse(d)!
61 |
62 | for article in parsedFeed.items {
63 | XCTAssertNotNil(article.attachments)
64 | XCTAssertEqual(article.attachments!.count, 1)
65 | let attachment = Array(article.attachments!).first!
66 | XCTAssertNotNil(attachment.mimeType)
67 | XCTAssertNotNil(attachment.sizeInBytes)
68 | XCTAssert(attachment.url.contains("cloudfront"))
69 | XCTAssertGreaterThanOrEqual(attachment.sizeInBytes!, 22275279)
70 | XCTAssertEqual(attachment.mimeType, "audio/mpeg")
71 | }
72 | }
73 |
74 | func testTheOmniShowUniqueIDs() {
75 |
76 | let d = parserData("theomnishow", "rss", "https://theomnishow.omnigroup.com/")
77 | let parsedFeed = try! FeedParser.parse(d)!
78 |
79 | for article in parsedFeed.items {
80 | XCTAssertNotNil(article.uniqueID)
81 | XCTAssertTrue(article.uniqueID.hasPrefix("https://theomnishow.omnigroup.com/episode/"))
82 | }
83 | }
84 |
85 | func testMacworldUniqueIDs() {
86 |
87 | // Macworld’s feed doesn’t have guids, so they should be calculated unique IDs.
88 |
89 | let d = parserData("macworld", "rss", "https://www.macworld.com/")
90 | let parsedFeed = try! FeedParser.parse(d)!
91 |
92 | for article in parsedFeed.items {
93 | XCTAssertNotNil(article.uniqueID)
94 | XCTAssertEqual(article.uniqueID.count, 32) // calculated unique IDs are MD5 hashes
95 | }
96 | }
97 |
98 | func testMacworldAuthors() {
99 |
100 | // Macworld uses names instead of email addresses (despite the RSS spec saying they should be email addresses).
101 |
102 | let d = parserData("macworld", "rss", "https://www.macworld.com/")
103 | let parsedFeed = try! FeedParser.parse(d)!
104 |
105 | for article in parsedFeed.items {
106 |
107 | let author = article.authors!.first!
108 | XCTAssertNil(author.emailAddress)
109 | XCTAssertNil(author.url)
110 | XCTAssertNotNil(author.name)
111 | }
112 | }
113 |
114 | func testMonkeyDomGuids() {
115 |
116 | // https://coding.monkeydom.de/posts.rss has a bug in the feed (at this writing):
117 | // It has guids that are supposed to be permalinks, per the spec —
118 | // except that they’re not actually permalinks. The RSS parser should
119 | // detect this situation, and every article in the feed should have a permalink.
120 |
121 | let d = parserData("monkeydom", "rss", "https://coding.monkeydom.de/")
122 | let parsedFeed = try! FeedParser.parse(d)!
123 |
124 | for article in parsedFeed.items {
125 | XCTAssertNil(article.url)
126 | XCTAssertNotNil(article.uniqueID)
127 | }
128 | }
129 |
130 | func testEmptyContentEncoded() {
131 | // The ATP feed (at the time of this writing) has some empty content:encoded elements. The parser should ignore those.
132 | // https://github.com/brentsimmons/NetNewsWire/issues/529
133 |
134 | let d = parserData("atp", "rss", "http://atp.fm/")
135 | let parsedFeed = try! FeedParser.parse(d)!
136 |
137 | for article in parsedFeed.items {
138 | XCTAssertNotNil(article.contentHTML)
139 | }
140 | }
141 |
142 | func testFeedKnownToHaveGuidsThatArentPermalinks() {
143 | let d = parserData("livemint", "xml", "https://www.livemint.com/rss/news")
144 | let parsedFeed = try! FeedParser.parse(d)!
145 | for article in parsedFeed.items {
146 | XCTAssertNil(article.url)
147 | }
148 | }
149 |
150 | func testAuthorsWithTitlesInside() {
151 | // This feed uses atom authors, and we don’t want author/title to be used as item/title.
152 | // https://github.com/brentsimmons/NetNewsWire/issues/943
153 | let d = parserData("cloudblog", "rss", "https://cloudblog.withgoogle.com/")
154 | let parsedFeed = try! FeedParser.parse(d)!
155 | for article in parsedFeed.items {
156 | XCTAssertNotEqual(article.title, "Product Manager, Office of the CTO")
157 | XCTAssertNotEqual(article.title, "Developer Programs Engineer")
158 | XCTAssertNotEqual(article.title, "Product Director")
159 | }
160 | }
161 |
162 | func testTitlesWithInvalidFeedWithImageStructures() {
163 | // This invalid feed has Here’s a partial collection of links from my talk today… “The [software developer tool] team clearly doesn’t use [that tool] themselves.” I lose things a lot. Sometimes they’re just misplaced, sometimes gone forever. I don’t know if I have ever run out of ink in a pen—there’s… Keyboard shortcuts, and other little details may be programmatically simple to set up, but they are still an important part of an app’s… I moved from Senior Test Pilot to Software Engineer last month. This is only a test. When I wrote the post about ordering Mac modifier keys a few days ago, I was thinking primarily about the proper order of the symbols when writing about a keyboard shortcut, like ⌃⌥⌘P.1. I mentioned parenthetically that this order isn’t always observed when people speak about keyboard shortcuts or when they write the names of the keys out fully, as in “Command-Shift-3 takes a screenshot.” Jason Snell, in both a post at Six Colors and in conversation with John Siracusa on the lastest episode of Upgrade, took a stand against Apple’s ordering:2 Command is the commander! Command is the monarch of all keys! Command always comes first, in my book. Siracusa agreed, and so do I. The ⌘ key is, and has always been, the key that signals a keyboard shortcut. While other modifier keys are sometimes used without ⌘—in cursor control and text selection, for example—I can’t think of any Apple applications that don’t use ⌘ to signal a keyboard shortcut for a menu item. And that primacy in shortcuts to menu items is, I think, why Apple puts it last rather than first. Keyboard shortcuts are always presented right-justified along the right edge of the menu. The most common shortcuts are just ⌘ and a letter, like ⌘N to start a new document, for example. It’s typically the variations on the basic command that get additional modifier keys, like ⌥⌘N to start a new project. If that were presented in a menu as ⌘⌥N, the menu would look wrong because the ⌘ symbols wouldn’t line up. Here’s the menu in Safari: There are two different commands and three different commands. This, in Apple’s opinion (and mine), wouldn’t be right: It’s not just having the ⌘ symbols aligned. The additional modifier symbols go in front because ⌘ is king and must sit next to the N or the W. The importance of the modifier decreases as you move away from the letter. It should go without saying—but I’ll say it anyway—that the letter (or number or whatever) key is the most important because nothing happens until it’s pressed. Having said all this, and despite agreeing with Apple’s symbol ordering, my ear for shortcut ordering works just like Jason’s and John’s. The main reason I use keyboard shortcut symbols in my posts instead of words is that I can read ⌥⇧⌘W and not be bothered because I don’t “hear” it as I read the symbols. “Option-Shift-Command-W,” on the other hand, gets sounded out in my head, and it sounds wrong. I suspect that’s why Apple’s own documentation sometimes gets the order wrong when the modifiers get written out as words. In speaking out the keys, “Command” is natural to put first because it announces that what’s coming is a keyboard shortcut. Which happens to be the shortcut I use for previewing a blog post locally before publishing it. ↩︎ In the original post, I said I didn’t know where the order was documented. A few people pointed me to both the Human Interface Guidelines and the Style Guide, where Apple gives the proper order explicitly. ↩︎ [If the formatting looks odd in your feed reader, visit the original article] Will probably be an iMac. I guess that spoils the suspense, doesn’t it? My iMac at work is the 27″ Late 2012 model, the one that came out one step before Retina came to the iMac. I don’t regret buying it, as my previous iMac (a 2006 model, I think) was absolutely on its last legs—constantly swapping to hard disk and running hot. I hadn’t meant to wait so long to replace it, but there was a long delay before that 2012 model came out, and I didn’t want to buy something that would be last year’s model almost as soon as I set it up. My home Mac is the venerable 2010 13″ MacBook Air, the first good Air. In the normal course of things, this would be the Mac I replace next, and I’ve been expecting to do so for a few years now. but… But Apple never came out with a Retina MacBook Air, choosing instead to go with the MacBook, which I find a little too far on the portable side of the portability/power spectrum. A couple of years ago, I had a crisis when my Air crapped out on me. It seemed wrong to put money into a five-year-old machine, but I wasn’t enthused about any of the MacBooks in the lineup at the time. I didn’t know the just-released 2015 MacBook Pro would turn out to be the best laptop ever made, I didn’t want to spend MacBook Pro money on my home/travel machine. The $280 logic board upgrade turned out to be a good investment, as I’m now 2½ years into my rejuvenated Air. Yes, it takes a while to wake up when I open the lid. Yes, its 128 GB SSD is tiny. No, it can’t take advantage of many of the iOS integration features that newer Macs can. And no, I don’t think it’s a good idea to install High Sierra on it. But it’s given me 30 months of faithful use, much more than I expected at the time. The announcement of the Touch Bar last year made me certain I’d be getting a MacBook Pro with it. A software-configurable set of controls seemed perfect for someone who’s always ginning up little scripts. But no one seems to like it, possibly because its configurability isn’t especially open to users. Bummer. I’ve delayed the decision on my home Mac for such a long time that now my office Mac is long in the tooth, too. Still working fine for most tasks, but just a Core 2 Duo machine that often makes me wait to scroll through long PDFs of scanned engineering and architectural drawings, something I need to do at work quite often. And no Retina. So it looks like my best bet is to buy a new iMac for work and bring my current office iMac home. This will put the power where I need it the most and will give me extra ooomph here at home. Especially with disk space (3 TB vs. 128 GB) and RAM (24GB vs. 4GB). It will be weird, though, as I haven’t had a desktop computer here at home in a dozen years. Will I enjoy being tethered to one spot in the house? And what about a travel computer? Both of these questions are made less pressing by the device I’m typing this on: a 9.7″ iPad Pro. While I agree with Gabe that it is by no means a Mac substitute, it can handle a lot of what I do at home and virtually everything I need to do on the road.1 As for which iMac, I think I’ll settle on a middle-of-the-road 27″ configuration with a 3TB Fusion drive. Sort of the 2017 of what I bought in 2012. I bought the iPad Pro last year as a sort of experiment to find out how comfortable I’d be working on it. I intend to write a full post about the results of that experiment soon, but in the meantime, you really should read Gabe’s post over at Macdrifter. I’ll probably use his post as a jumping-off point. And there may be a quiz. ↩︎ [If the formatting looks odd in your feed reader, visit the original article] If you write about Mac keyboard shortcuts, as I did yesterday, you should know how to do it right. Just as there’s a proper order for adjectives in English, there’s a proper order for listing the modifier keys in a shortcut. I haven’t found any documentation for this, but Apple’s preferred order is clear in how they show the modifiers in menus and how they’re displayed in the Keyboard Shortcuts Setting. The order is similar to how you see them down at the bottom left of your keyboard. Control (⌃), Option (⌥), and Command (⌘) always go in that order. The oddball is the Shift(⇧) key, which sneaks in just in front of Command. Keyboard Maestro recognizes this standard order and presents its “hot key” shortcut the same way. (When people speak about keyboard shortcuts, it’s not uncommon to put Command first, e.g., “Command-Shift-3 takes a screenshot.” I’ve seen it written out that way, too. Apple is usually pretty careful to use the same order when using words as when using symbols. This page, for example, uses “Shift-Command-3,” to match the ⇧⌘3 you’d see in the Keyboard Shortcut Setti
2 |
--------------------------------------------------------------------------------
/Tests/RSParserTests/Resources/authors.json:
--------------------------------------------------------------------------------
1 | {
2 | "version": "https://jsonfeed.org/version/1.1",
3 | "title": "Author test feed",
4 | "authors": [{ "name": "Root Author 1"}, { "name": "Root Author 2" }],
5 | "author": { "name": "Legacy Root Author" },
6 | "items": [
7 | {
8 | "id": "Item without authors",
9 | "content_html": ""
10 | },
11 | {
12 | "id": "Item with legacy author",
13 | "author": { "name": "Legacy Item Author" },
14 | "content_html": ""
15 | },
16 | {
17 | "id": "Item with modern authors",
18 | "authors": [{ "name": "Item Author 1" }, { "name": "Item Author 2" }],
19 | "content_html": ""
20 | },
21 | {
22 | "id": "Item with both",
23 | "authors": [{ "name": "Item Author 1" }, { "name": "Item Author 2" }],
24 | "author": { "name": "Legacy Item Author" },
25 | "content_html": ""
26 | }
27 | ]
28 | }
29 |
--------------------------------------------------------------------------------
/Tests/RSParserTests/Resources/donthitsave.xml:
--------------------------------------------------------------------------------
1 |
I was nearly murdered by a coconut today. For real. This happened as I took the dogs on their morning poop stroll (I can no longer speak or spell the word “walk” in my home). I wandered up and down the sidewalk, on some grass, and headed back home. Near the end of the walk, I stopped to fiddle with my phone. I was listening to a podcast, and needed to skip the commercials. I stood in place for 30, maybe 40 seconds. When I was done, I took two steps... [read more] It's time I woke up before dawn again. Voluntarily. It not easy to beat the sun at its own game. Most of my social and computer life has been dominated by a late nights. I work during the day because I have to, then stay up as late as I want because I'm a grown up. Every once in a while, however, I will mix things up: I bought a hammer this week. My first Hawaiian hammer. I will use it not to hang something, not to bang something, but to remove a nail. I hate that nail. Today is a good day. How's your night vision? When I was little, mine was excellent. I could spot animals while walking at night, read in low light conditions, and effectively navigate the house based on the light of digital clocks. It only got better with time. This wasn't a super power. I was adjusting to my surroundings. I spent my younger years in upstate NY. Winter and cloudy weather seemed to last 9 months, which meant that I got used to gloomy conditions. Our house... [read more] Game of Thrones is back, Avengers are back, and the Tick Season 2 is out. It is a good month for amusing ourselves. So why are you spending your time here? Oh I know, you need some sort of control sample. What’s the point of having compelling and enjoyable entertainment if you don’t have something dull to compare it to? I see. It all makes sense now. Wow. I can’t believe you think this comic dull. Nice, reader, reeeeeaaaal nice. I’ll remember... [read more] Apologies for the extraordinarily late comic. This is the first one ever delayed at length by my news. Here's why: I wrote the comic on Thursday night. When I went to write the news in the morning, I decided to focus on the adorable habits of my two dogs. One of the monsters was acting weird. Comically weird. I decided to write the news about that. I found it quite funny. I wrote a page and a half about how my dog was suddenly scared of everything. She ran from... [read more] I made Tofacos for dinner-- tofu tacos that are absolutely abhorrent. I love the food here in Hawaii, but when breakfast, lunch, and dinner consists of fish and noodles, things tend to get weird when I deviate. I left about as big a mess as you can imagine while stirring the “food”. I’m not a great cook, I’m an adequate one. My system involves hopping from one nearly burning pile of food to another, narrowly staying ahead of a charred, blackened meal. I’m... [read more] To prove that I can. Today’s comic is dedicated to my very sick team lead. Too bad you’re too sick to check and see if today’s comic is true. For everyone else out there, welcome to the last 3 days you have to enter my sweepstakes thingy. If you want me to draw you, the deadline is Sunday, March 31st. Get to it! If you’re reading after that date, or if you don’t care about my sweepstakes, I have only one... [read more] It's 2am here. What time is it there? I'll post some news in some time. … Okay, I’m back… at 2am. A different 2am. Let’s make this quick: For those checking later, or too busy to google, here is an article about Facebook’s latest mishap, as mentioned in today’s comic. In personal news, I've been thorough enjoying the new... [read more]
\n
\n![\"Safari](\"http://leancrew.com/all-this/images2017/20171123-Safari%20File%20menu.png\" "\\"Safari")
![\"Altered](\"http://leancrew.com/all-this/images2017/20171123-Altered%20Safari%20File%20menu.png\" "\\"Altered")
\n\n
\n
\n
\n\n
\n
\n![\"Canonical](\"http://leancrew.com/all-this/images2017/20171119-Canonical%20Mac%20modifier%20key%20order.png\" "\\"Canonical")
![\"Modifier](\"http://leancrew.com/all-this/images2017/20171119-Modifier%20keys.jpg\" "\\"Modifier")
![\"Keyboard](\"http://leancrew.com/all-this/images2017/20171119-Keyboard%20Maestro%20hot%20key%20field.png\" "\\"Keyboard")
17 |
Second item.
", 14 | "date_published": "2021-03-05T13:04:04+02:00", 15 | "_contoso": { 16 | "someKey": "SomeValue2", 17 | "someBoolKey": true, 18 | "anotherKey": "AnotherValue2" 19 | }, 20 | "attachments": [ 21 | { 22 | "url": "https://example.com/SomeFile2.app.zip", 23 | "mime_type": "application/zip" 24 | } 25 | ] 26 | }, 27 | { 28 | "id": "1", 29 | "content_html": "First item.
", 30 | "date_published": "2021-02-26T15:04:04+02:00", 31 | "_contoso": { 32 | "someKey": "SomeValue1", 33 | "someBoolKey": false, 34 | "someIntKey": 43, 35 | "anotherKey": "AnotherValue1" 36 | }, 37 | "attachments": [ 38 | { 39 | "url": "https://example.com/SomeFile1.app.zip", 40 | "mime_type": "application/zip" 41 | } 42 | ] 43 | }, 44 | { 45 | "id": "0", 46 | "content_html": "Third item. Without an extension.
", 47 | "date_published": "2021-02-25T15:04:04+02:00" 48 | } 49 | ] 50 | } 51 | -------------------------------------------------------------------------------- /Tests/RSParserTests/Resources/kc0011.rss: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Ranchero-Software/RSParser/1e73a4694fa5972b92e3d0012302e77770c32915/Tests/RSParserTests/Resources/kc0011.rss --------------------------------------------------------------------------------