Rename frameworks according to Cocoa convention#60
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Apple adopts a naming convention for all of its system frameworks. Oddly, such convention is not documented officially. There is, however, an implicit understanding of the meaning of each suffix included in their names:
Low-level, client-agnostic framework providing support for general programming concepts, such as string or floating-point manipulation. This category of frameworks does not introduce a new domain; rather, it implements those that are already established in the discipline and can be used by any domain specific to whichever applications.
Similar to a foundation framework, differing in that it is specific to a domain of the operating system or application.
Provides client-specific implementations of the abstractions exposed by a core framework. E.g., a
DatabaseProtocolmay be defined in aDatabaseCoreframework; aDatabaseKitframework may, then, expose anSQLDatabaseimplementation conforming to that protocol.Less common as system frameworks, the primary role of a UI framework in Deus is to expose views for rendering on the screen of the device on which the application is being run. These views are not tied to a given domain of the application, and may be referenced by multiple feature frameworks.
Even less common than UI frameworks as system frameworks, feature frameworks provide one or multiple user interfaces of a domain of the application, which may be rendered on the screen. This type of framework may use views defined in a UI framework, and differs from the latter in that it is specific to a domain.