How do I install and run Eject on a .xib file?

Install via Homebrew with 'brew install eject', then use 'eject --file /path/to/file.xib' in the command line to generate Swift code. You'll need to manually copy the output into your project and remove the original .xib file.

Does Eject work with Storyboards or macOS projects?

No, Eject currently only supports iOS .xib files. Storyboard and AppKit support are listed as potential future enhancements, but not available now, limiting its use to specific iOS scenarios.

What should I do if Eject shows warnings for uninterpreted XML?

Open an issue on the GitHub repository with the warning details. The tool is designed to flag these for community feedback, helping improve coverage over time through user contributions.

How can I compare changes in .xib files using Eject?

Use the provided diff command in the README: create a temporary file with the previous .xib version and compare generated code outputs to visualize differences, which helps in version control and debugging.

Eject vs manual conversion: which is better for dynamic views?

Eject automates the initial conversion and can save time, but manual conversion offers more control and precision for highly dynamic or complex views. Eject is best as a starting point, not a complete solution.

Is Eject production-ready for large iOS projects?

Given its alpha status and manual steps, Eject is risky for large projects. It's better suited for experimental conversions or legacy .xib updates where errors can be tolerated and tested thoroughly.

What library does Eject use for Auto Layout constraints?

Eject uses the Anchorage library to generate programmatic Auto Layout constraints, translating Interface Builder constraints into Swift code that relies on Anchorage for layout management.

Open-Awesome

Eject

MITSwift

A command-line tool that generates Swift code from Interface Builder .xib files to transition to programmatic UI layout.

GitHub

520 stars24 forks0 contributors

What is Eject?

Eject is a command-line tool that converts Interface Builder .xib files into Swift code, allowing iOS developers to transition from visual UI design to programmatic view layout. It solves the pain point of Interface Builder becoming less useful as views grow more dynamic or complex, providing a generated codebase that replaces the .xib file entirely.

Target Audience

iOS developers who use Interface Builder but find it limiting for dynamic or programmatically managed views, and want a structured way to move to code-based UI without manual rewriting.

Value Proposition

Developers choose Eject because it automates the tedious process of converting .xib files to Swift, reducing manual effort and potential errors, while offering descriptive variable names and constraint handling via Anchorage for a smoother transition.

Overview

An eject button for Interface Builder to generate swift code

Use Cases

Best For

Converting static Interface Builder views to programmatic Swift code
Transitioning legacy .xib-based projects to code-first UI
Generating Auto Layout constraints programmatically from .xib files
Comparing changes in .xib files through generated code diffs
Removing Interface Builder dependencies for dynamic view management
Automating UI code generation for iOS development workflows

Not Ideal For

Projects requiring production-ready, bug-free code generation without manual intervention
Teams using Storyboards or AppKit who need comprehensive UI conversion tools
Developers needing guaranteed out-of-the-box compiling code from generated output

Pros & Cons

Pros

Automated XIB Conversion

Generates Swift code from .xib files, automating the tedious process of transitioning away from Interface Builder and reducing manual rewriting errors.

Anchorage-Based Constraints

Uses the Anchorage library to accurately translate Auto Layout constraints into programmatic code, ensuring reliable layout management in Swift.

Outlet Preservation

Handles both outlets and outlet collections, preserving connections in the generated code to maintain functionality without manual re-linking.

Descriptive Variable Naming

Employs user labels or snake-cased class names for variable names, improving code readability and making the generated output easier to understand.

Community Feedback System

Prints warnings for uninterpreted XML, encouraging users to report issues on GitHub, which fosters iterative improvement and community involvement.

Cons

Alpha Quality Tool

Marked as alpha, meaning it may have bugs, incomplete features, and is not recommended for stable production use without extensive testing.

No Compilation Guarantee

Explicitly states that generating code that compiles out of the box is a non-goal, often requiring manual fixes or user labels to avoid errors.

Limited Platform Support

Only supports iOS .xib files with no AppKit or Storyboard conversion, restricting its use to specific project types and ignoring common macOS or storyboard workflows.

Manual Workflow Overhead

Requires users to copy-paste generated code and manually delete .xib files, adding steps that can be error-prone and time-consuming compared to integrated tools.

Frequently Asked Questions

Related Projects

SwifterSwift

A handy collection of more than 500 native Swift extensions to boost your productivity.

Stars15,073

Forks1,669

Last commit1 month ago

BlocksKit

The Objective-C block utilities you always wish you had.

Stars6,840

Forks1,250

Last commit8 years ago

libextobjc

A Cocoa library to extend the Objective-C programming language.

Stars4,504

Forks460

Last commit7 years ago

Then

✨ Super sweet syntactic sugar for Swift initializers

Stars4,390

Forks300

Last commit2 months ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub