Skip to content
Source for many of The Omni Group's frameworks
Objective-C Swift C HTML Rich Text Format Ruby Other
Branch: master
Clone or download
tjw Updated with changes from OmniGroup svn [335266:335853]
- iOS dark mode support, work in progress
- Deprecation fixes

- Switched to using Swift 5.0

- Add validity checking for .stringsdict files

- A swift wrapper for the SecKeyUsage permission set

- Small performance win: Use the `entity` local variable we've previous computed rather than calling -entity on the ODOObjectID again.

- Exposed the divider colors for MultiPane clients.

- Fix race condition in collecting the OFFileEdit for a saving document and archiving it to recents.
Latest commit 728cc3a Jul 15, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
Configurations Updated with changes from OmniGroup svn [335266:335853] Jul 15, 2019
Scripts Updated with changes from OmniGroup svn [333448:334393] Jul 15, 2019
Tools Updated with changes from OmniGroup svn [334393:335266] Jul 15, 2019
.gitignore Ignore default.profraw files. Nov 9, 2018
.gitmodules Switch to the read-only git: URL for the submodule. Jul 4, 2012
OmniSourceLicense.html Adding a copy OmniSourceLicense.html at the top level to make it easi… Dec 30, 2008
README.markdown Updated with changes from OmniGroup svn [335266:335853] Jul 15, 2019
version Updated with changes from OmniGroup svn [335266:335853] Jul 15, 2019



Checking out the source

git clone git://
git submodule update --init


  • We currently use Xcode 10.11 for all platforms. You'll probably have the best results if you do too.
  • Add the projects you want to your workspace.
  • Take a look in the Workspaces directory for a sample workspace for the TextEditor iPad example app.

Supported Targets

  • We require macOS 10.14, iOS 13, and watchOS 6.0, with our deployment builds happening on macOS Mojave 10.14.4.

Configuring the Source

We place our project-wide configuration options in xcconfig files, under OmniGroup/Configurations. The naming scheme of the files is fairly straightforward, hopefully. Each project has Omni-Global-{Debug,Release,...}.xcconfig as the basis for the corresponding configuration. Each Mac target has Omni-{Bundle,Application,Tool,...}-{Debug,Release,...}.xcconfig and each iOS target has Touch-{Application,Library}-{Debug,Release,...}.xcconfig. Each of these end point configurations when #includes 'superclass' configurations (with "Common" in the name).


The Workspaces directory contains a couple sample workspace that can be built from Xcode.


You can’t perform that action at this time.