Swiftpack.co - Package - ArtSabintsev/FontBlaster

FontBlaster

Programmatically load custom fonts into your iOS and tvOS app.

Swift Support Platform

CocoaPods Carthage Compatible SwiftPM Compatible

About

Say goodbye to importing custom fonts via property lists as FontBlaster automatically imports and loads all fonts in your app's Bundles with one line of code.

Features

  • [x] CocoaPods Support
  • [x] Carthage Support
  • [x] Swift PM Support
  • [x] Automatically imports fonts from Bundle.main
  • [x] Able to import fonts from remote bundles
  • [x] Sample Project
  • [x] Documentation at http://sabintsev.com/FontBlaster/

Installation Instructions

| Swift Version | Branch Name | Will Continue to Receive Updates? | ------------- | ------------- | ------------- | 4.1 | master | Yes | 3.2 | swift3.2 | No | 3.1 | swift3.1 | No

CocoaPods

For Swift 4.1 support:

pod 'FontBlaster'

For Swift 3.2 support:

pod 'FontBlaster', :git => 'https://github.com/ArtSabintsev/FontBlaster.git', :branch => 'swift3.2'

For Swift 3.1 support:

pod 'FontBlaster', :git => 'https://github.com/ArtSabintsev/FontBlaster.git', :branch => 'swift3.1'

Carthage

For Swift 4.1 support:

github "ArtSabintsev/FontBlaster"

For Swift 3.2 support:

github "ArtSabintsev/FontBlaster", "swift3.2"

For Swift 3.1 support:

github "ArtSabintsev/FontBlaster", "swift3.1"

Swift Package Manager

.Package(url: "https://github.com/ArtSabintsev/FontBlaster.git", majorVersion: 4)

Manual

  1. Download FontBlaster.
  2. Copy FontBlaster.swift into your project.

Setup

Typically, all fonts are automatically found in Bundle.main. Even if you have a custom bundle, it's usually lodged inside of the mainBundle. Therefore, to load all the fonts in your application, irrespective of the bundle it's in, simply call:

FontBlaster.blast() // Defaults to Bundle.main if no arguments are passed

If you are loading from a bundle that isn't found inside your app's mainBundle, simply pass a reference to your Bundle in the blast(_:) method:

FontBlaster.blast(bundle:) // Takes one argument of type Bundle, or as mentioned above, defaults to Bundle.main if no arguments are passed

If you need a list of all of the loaded fonts, an overloaded version of the blast(_:) method has a completion handler that returns just that. Just like the original method, this method takes either a custom Bundle or defaults to Bundle.main if no argument is passed.


// Defaults to Bundle.main as no argument is passed
FontBlaster.blast() { (fonts) in
  print(fonts) // fonts is an array of Strings containing font names
}

// Custom bundle is passed as argument
FontBlaster.blast(bundle:) { (fonts) in
  print(fonts) // fonts is an array of Strings containing font names
}

To turn on console debug statements, simply set debugEnabled() = true before calling either blast() method:

FontBlaster.debugEnabled = true
FontBlaster.blast()

Sample Project

A Sample iOS project is included in the repo. When you launch the app, all fonts are configured to load custom fonts, but don't actually display them until you push the button. After pushing the button, FontBlaster imports your fonts and redraws the view.

Inspiration

This project builds upon an old solution that Marco Arment proposed and wrote about on his blog.

Created and maintained by

Arthur Ariel Sabintsev

Github

link
Stars: 908
Help us keep the lights on

Dependencies

Releases

4.0.4 - Mar 15, 2018

  • Updated Podspec file.
  • Removed .swift-version file, as it's been deprecated.

4.0.3 - Feb 28, 2018

Fixes a podspec issue that was introduced in 4.0.2.

4.0.2 - Feb 28, 2018

Fontblaster supported tvOS out of the box. The podspec now explicitly supports allows for installation of Fontblaster on apps that target tvOS 9+.

4.0.1 - Nov 10, 2017

  • #24
    • Removed deprecated code references to Character API as String and Character API changed in Swift 4 and is enforced in in Xcode 9.1 / iOS 11.1. (thanks to @andreyrd)

4.0.0 - Sep 13, 2017

FontBlaster v4.0.0 adds support for Swift 4 / iOS 11 / Xcode 9. Only minor changes were made under-the-hood.

Moving forward, only support for the Swift 4 codebase (on master) will be maintained.

| Swift Version | Branch Name | Will Continue to Receive Updates? | ------------- | ------------- | ------------- | 4.0 | master | Yes | 3.2 | swift3.2 | No | 3.1 | swift3.1 | No