| Age | Commit message (Collapse) | Author | 
|---|
|  |  | 
|  | I think I have finally found out the reason for CocoaDocs ignoring
our markup: I have indented the documentation by four spaces, which
was interpreted as “code” by appledoc. Trying now without the indent,
that should finally help. | 
|  |  | 
|  |  | 
|  | A shortcut is a good value type, it makes good sense to represent it
using an immutable object like NSNumber or NSString. | 
|  | Using NSKeyedUnarchiver and NSKeyedArchiver directly is almost the
same amount of typing and it’s much clearer what goes on. | 
|  | It was never used and the recording can already be cancelled by Esc. | 
|  |  | 
|  | It’s a natural simplification of the MASShortcut class. All MASShortcutView
objects use a shared validator by default, but can be reconfigured to use a
different validator if needed through the shortcutValidator property. | 
|  | Plain functions are less prone to bugs, the compiler understands
them better and can offer better error messages, and plain functions
can be refactored more easily. | 
|  |  | 
|  | Packaging the code as a framework is mostly just a formality. It doesn’t
really change much, it just turns the code into a regular component.
What it does change is that the code now has its own Xcode settings,
which could make compatibility easier in the long run.
Including the demo in the main repository makes it easier to hack on
the library, since you can try the changes immediately. It also shows
how to bundle the framework into an app that uses it. |