Only a word: FANTASTIC!!! Many compliments for your job. I'm at start with swift coding .... but, it's possibile to have some tips to extract and use your Info page in other apps? If I copy class and View in a app coded with Object C, there are a lot of error. Which are dependencies for Info page?

Thanks

Fixed issues that will arise once Swift 3 is released, mainly relating to:

1. Removal of ++ and -- operators
   • --loadCount becomes loadCount -= 1
2. Use of string literal for Objective-C Selectors
   • let tapGestureRecognizer = UITapGestureRecognizer(target: self, action: "singleTapReceived:") becomes
     let tapGestureRecognizer = UITapGestureRecognizer(target: self, action: #selector(EnlargedPhotoGestureRecognizers.singleTapReceived(_:)))

just found your work! im newbie but i am amazed on what i have just seen!!! have read your comment on a previous "issue" and have made changes to the categories myself with your help of course!!

as for the first tab..how can i fetch news from my own rss website like on the sections? i mean when i go to "BlogsViewController" and enter my rss us and run the app the first tab says "error" and nothing else :(

When attempting to compile, an error stating that the subscript used to get a starredPosts object's identifier was ambiguous. This should fix that. (Emphasis on should: I'm new to Cocoa/CocoaTouch, and am not sure how to setup Parse so I can login to test the starred posts feature).

This way, the app at least compiles. I'm working on a branch to convert the rest of the deprecated Swift code, but those are only warnings.

https://www.parse.com/migration

Parse will be shutting down on January 28th, 2017. Suggestion: migrate to another database platform?

I'm new to Cocoa/CocoaTouch development, so I'm not sure as to what database platform would be best.

I am using xcode 6.1 on OSX 10.9.5 but when I am running simulator getting following error

iCarousel.h Swift Compiler Error Expected Identifier or '('

Can you help to resolve it?

Because it doesn't match the global font theme, and looks strange at certain points.

Generating attributed text directly from HTML was great to get things up and running, but now it looks subpar.

Encountered when briefly running on iPhone 4s iOS 7.1.1:

2014-07-16 22:52:24.090 The Oakland Post[212:60b] Unsupported pixel format in CSI
2014-07-16 22:52:24.098 The Oakland Post[212:60b] Unable to create unsliced image from csi bitmap data.
2014-07-16 22:52:24.222 The Oakland Post[212:60b] Could not load the "Circle" image referenced from a nib in the bundle with identifier "com.andrewclissold.The-Oakland-Post"

Occurs when rotating from landscape to portrait.

2014-07-04 16:23:20.749 The Oakland Post[299:36900] Unable to simultaneously satisfy constraints.
    Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) 
(
    "<NSAutoresizingMaskLayoutConstraint:0x156944c0 h=--& v=--& UITableViewWrapperView:0x15660b10.midY == + 480>",
    "<NSAutoresizingMaskLayoutConstraint:0x156944f0 h=--& v=--& V:[UITableViewWrapperView:0x15660b10(768)]>",
    "<NSAutoresizingMaskLayoutConstraint:0x156946a0 h=-&- v=-&- UITableView:0x15870e00.midY == UIViewControllerWrapperView:0x15664bf0.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x156946d0 h=-&- v=-&- UITableView:0x15870e00.height == UIViewControllerWrapperView:0x15664bf0.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x15690020 h=-&- v=-&- UIViewControllerWrapperView:0x15664bf0.midY == UINavigationTransitionView:0x15643b60.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15690050 h=-&- v=-&- UIViewControllerWrapperView:0x15664bf0.height == UINavigationTransitionView:0x15643b60.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x15694b90 h=-&- v=-&- UINavigationTransitionView:0x15643b60.midY == UILayoutContainerView:0x1563fe60.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15694bc0 h=-&- v=-&- UINavigationTransitionView:0x15643b60.height == UILayoutContainerView:0x1563fe60.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x156950a0 h=-&- v=-&- UILayoutContainerView:0x1563fe60.midY == UIViewControllerWrapperView:0x1564e6e0.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x156950d0 h=-&- v=-&- UILayoutContainerView:0x1563fe60.height == UIViewControllerWrapperView:0x1564e6e0.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x15695540 h=-&- v=-&- UIViewControllerWrapperView:0x1564e6e0.midY == UITransitionView:0x1564b1e0.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15695570 h=-&- v=-&- UIViewControllerWrapperView:0x1564e6e0.height == UITransitionView:0x1564b1e0.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x15695b00 h=-&- v=-&- UITransitionView:0x1564b1e0.midY == UILayoutContainerView:0x1564a420.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15695b30 h=-&- v=-&- UITransitionView:0x1564b1e0.height == UILayoutContainerView:0x1564a420.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x156961f0 h=-&- v=-&- UILayoutContainerView:0x1564a420.midY == UIWindow:0x15645d50.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15696220 h=-&- v=-&- UILayoutContainerView:0x1564a420.height == UIWindow:0x15645d50.height>",
    "<_UIWindowAnchoringConstraint:0x15696a90 h=--- v=--- UIWindow:0x15645d50.midY == + 384>",
    "<NSAutoresizingMaskLayoutConstraint:0x15696b20 h=--- v=--- V:[UIWindow:0x15645d50(768)]>"
)

Will attempt to recover by breaking constraint 
<NSAutoresizingMaskLayoutConstraint:0x156944c0 h=--& v=--& UITableViewWrapperView:0x15660b10.midY == + 480>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.
2014-07-04 16:23:20.782 The Oakland Post[299:36900] Unable to simultaneously satisfy constraints.
    Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) 
(
    "<NSAutoresizingMaskLayoutConstraint:0x156944c0 h=--& v=--& UITableViewWrapperView:0x15660b10.midY == + 480>",
    "<NSAutoresizingMaskLayoutConstraint:0x156944f0 h=--& v=--& V:[UITableViewWrapperView:0x15660b10(960)]>",
    "<NSAutoresizingMaskLayoutConstraint:0x156946a0 h=-&- v=-&- UITableView:0x15870e00.midY == UIViewControllerWrapperView:0x15664bf0.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x156946d0 h=-&- v=-&- UITableView:0x15870e00.height == UIViewControllerWrapperView:0x15664bf0.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x15690020 h=-&- v=-&- UIViewControllerWrapperView:0x15664bf0.midY == UINavigationTransitionView:0x15643b60.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15690050 h=-&- v=-&- UIViewControllerWrapperView:0x15664bf0.height == UINavigationTransitionView:0x15643b60.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x15694b90 h=-&- v=-&- UINavigationTransitionView:0x15643b60.midY == UILayoutContainerView:0x1563fe60.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15694bc0 h=-&- v=-&- UINavigationTransitionView:0x15643b60.height == UILayoutContainerView:0x1563fe60.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x156950a0 h=-&- v=-&- UILayoutContainerView:0x1563fe60.midY == UIViewControllerWrapperView:0x1564e6e0.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x156950d0 h=-&- v=-&- UILayoutContainerView:0x1563fe60.height == UIViewControllerWrapperView:0x1564e6e0.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x15695540 h=-&- v=-&- UIViewControllerWrapperView:0x1564e6e0.midY == UITransitionView:0x1564b1e0.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15695570 h=-&- v=-&- UIViewControllerWrapperView:0x1564e6e0.height == UITransitionView:0x1564b1e0.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x15695b00 h=-&- v=-&- UITransitionView:0x1564b1e0.midY == UILayoutContainerView:0x1564a420.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15695b30 h=-&- v=-&- UITransitionView:0x1564b1e0.height == UILayoutContainerView:0x1564a420.height>",
    "<NSAutoresizingMaskLayoutConstraint:0x156961f0 h=-&- v=-&- UILayoutContainerView:0x1564a420.midY == UIWindow:0x15645d50.midY>",
    "<NSAutoresizingMaskLayoutConstraint:0x15696220 h=-&- v=-&- UILayoutContainerView:0x1564a420.height == UIWindow:0x15645d50.height>",
    "<_UIWindowAnchoringConstraint:0x15696a90 h=--- v=--- UIWindow:0x15645d50.midY == + 384>",
    "<NSAutoresizingMaskLayoutConstraint:0x15696b20 h=--- v=--- V:[UIWindow:0x15645d50(1024)]>"
)

Will attempt to recover by breaking constraint 
<NSAutoresizingMaskLayoutConstraint:0x156944c0 h=--& v=--& UITableViewWrapperView:0x15660b10.midY == + 480>

Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKit/UIView.h> may also be helpful.