Objective-c code Apple style documentation set generator.

Related tags

Tools appledoc
Overview

About appledoc

IMPORTANT NOTICE: collaborators needed

appledoc is command line tool that helps Objective-C developers generate Apple-like source code documentation from specially formatted source code comments. It's designed to take as readable source code comments as possible for the input and use comments as well as surrounding source code to generate visually appealing documentation in the form of HTML as well as fully indexed and browsable Xcode documentation set. Although there are several tools that can create HTML documentation for Objective-C, all of those known to me fall short in meeting the minimum of goals described below.

Main goals of appledoc:

  • Human-readable source code comments.
  • Simple cross references to objects and members.
  • Generate Apple-like source code HTML documentation.
  • Generate and install fully indexed and browsable Xcode documentation set.
  • Single tool to drive generation from source code parsing to documentation set installation.
  • Easily customizable output.
  • 100% Objective-C implementation for easy debugging.

To make your experience with appledoc as smooth as possible, we warmly suggest reading this whole document as well as all online documentation mentioned in "using appledoc" section below!

Usage of appledoc is allowed under the terms listed in LICENSE section at the bottom of this file!

Want to keep updated? Follow us on Twitter - @gentlebytes.

Quick install

The recommended way is to clone GitHub project and compile the tool from Xcode. As cloning GitHub project will create the link to the main repository, it greatly simplifies future upgrading too. To install, type the following in the Terminal:

git clone git://github.com/tomaz/appledoc.git

This creates appledoc directory. Within you can find appledoc.xcworkspace Xcode workspace; open it and compile appledoc target - this should work out of the box, however your system must meet minimum system requirements, see below. I recommend you copy resulting appledoc executable from build directory to one of the directories in your path (echo $PATH) to make it easily accessible.

Optional: Appledoc is selfcontained and contains the necessary template files. IF you want to modify these default from Templates subdirectory to one of the expected locations:

  • ~/Library/Application Support/appledoc
  • ~/.appledoc

You can also use install-appledoc.sh script to perform quick installation. Open Terminal and switch to appledoc directory. Type following command:

sudo sh install-appledoc.sh (if you need templates add '-t default')

It compiles appledoc and installs its binary to /usr/local/bin and templates (if wanted) to ~/.appledoc by default. You can override this directories with -b and -t options respectively. For example:

sudo sh install-appledoc.sh -b /usr/bin -t ~/Library/Application\ Support/appledoc

Alternatively with Homebrew:

brew install appledoc

Homebrew does not install templates by default.

Using appledoc

Use appledoc --help to see the list of all command line switches. Read more about appledoc on appledoc site. Also read wiki pages for some more in-depth articles.

Use appledoc Google group as a forum for questions on usage or other general questions.

Use appledoc issues page to submit bug and feature requests. Before submitting new issues, check the forums to see if your question is answered there - unless you can confirm your issue as a new feature request or a bug, you should start at the forum to keep GitHub issues clean. Also read through issues to see if the issue is already there and vote on it or add a comment (don't forget about closed issues).

Installation tips

To keep up to date, just go to Terminal and cd into appledoc directory, issue git pull and recompile appledoc.xcodeproj. Don't forget to overwrite appledoc executable you've copied to $PATH :)

If you also want to compile and run AppledocTests (unit tests) target, you need to copy all the frameworks indicated within Libraries & Frameworks group to shared frameworks directory before building unit tests target! This is not required for building the appledoc tool itself.

Integrating with Xcode

You can setup Xcode to automate appledoc document creation. Find out how using a Run Script and your project's Build Phases.

Docset usage tips

Pre-generated documentation and docsets for most Cocoa frameworks are available at:

Once you have a docset, you might want to use it with a documentation browser:

Troubleshooting

Have problems? This is what you can do to troubleshoot:

  1. Make sure you have the latest appledoc version. Try git pull and run with latest version again.
  2. IF you have template files installed, make sure you're using the latest - delete the predefined folders and have appledoc copy the files from its embedded archive again (see Quick Install section above).
  3. Increase verbosity level with --verbose command line switch. Default level is 2, but you can progressively increment verbosity up to 6 with each level giving you more detailed information. As this will give you a lot more information, you may want to concentrate only on specific set of source files you have problem with. Note that increasing verbosity will result in slower performance so using levels above 4 for every day use is not recommended.
  4. Appledoc is open source project! You have all the source code available, so run it from Xcode. You can setup Xcode to pass the desired command line arguments and add breakpoints to help you isolate your issue. If you feel you'd like to contribute more to community, you are welcome to fork the project on GitHub and add features to it. Keep us posted so we can add these features to main repository as well - include unit tests if possible.
  5. If you think you found a bug or want to request new feature, go to appledoc issues page. First read existing issues to see if there is already a request there (if you're using master branch, also read closed issues as your request may have already been covered but isn't yet merged on master branch). You can vote on existing requests to help us decide which features to concentrate on or you can add a comment to aid in solving it. If you don't find the request there, create a new issue; include parts of source files that give you problems if possible and/or description or steps that lead to it.
  6. If you're having problems with some of your source files and don't want to publish them online, you can contact us through email below. We'll do our best to help you out, but bear in mind appledoc is not commercial product; it's created and maintained in our spare time, so resources are limited.

Developer notes

If you wish to contribute, see the Developer Notes file for short overview of how appledoc works internally.

Minimum system requirements

  • Xcode 4.5 or greater for compiling
  • OS X 10.7 for compiling and running

License

appledoc is licensed with modified BSD license. In plain language: you're allowed to do whatever you wish with the code, modify, redistribute, embed in your products (free or commercial), but you must include copyright, terms of usage and disclaimer as stated in the license, the same way as any other BSD licensed code. You can of course use documentation generated by appledoc for your products (free or commercial), but you must attribute appledoc either in documentation itself or other appropriate place such as your website.

If for whatever reason you cannot agree to these terms, contact us through contact form on our about page, we'll do our best to help you out you out and find a workable solution!

Copyright (c) 2009-2011, Gentle Bytes All rights reserved.

Redistribution and use in source, binary forms and generated documentation, with or without modification, are permitted provided that the following conditions are met:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

  • Redistributions of documentation generated by appledoc must include attribution to appledoc, either in documentation itself or other appropriate media.

  • Neither the name of the appledoc, Gentle Bytes nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Gentle Bytes [email protected]

Issues
  • Wrong Icons

    Wrong Icons

    File icons are used for classes (and everything produced by AppleDoc) in the "Browse" view of Organizer, yet when searching, they do come up with the class icon "C". Would be super great to have the browse show these also with the class icon. Thanks!

    opened by twobitunicorn 36
  • brew cannot compile appledoc / Xcode 5.1 deprecated garbage collection

    brew cannot compile appledoc / Xcode 5.1 deprecated garbage collection

    https://gist.github.com/anonymous/9741786

    Bug Known 
    opened by matthiasplappert 26
  • Xcode's QuickHelp not working with created DocSet

    Xcode's QuickHelp not working with created DocSet

    Xcode does not display QuickHelp for the DocSet I created with AppleDoc. The other parts of the Xcode integration work fine - I can see the project in the Help menu and the files are found when I right-click a keyword and choose "Find text in documentation".

    It does not seem to a problem with my setup - I asked other people to install my docset, and they reported the same results.

    Bug Known 
    opened by PrimaryFeather 25
  • Default DocSetPlatformFamily

    Default DocSetPlatformFamily

    Can you set the DocSetPlatformFamily key to default to "appledoc"? Having "appledoc" as the docset platform allows Dash (http://kapeli.com/dash) to recognise a docset as Appledoc-generated and enable extra features for it (table of contents and click-to-copy). Thanks!

    Feature 
    opened by Kapeli 23
  • OSX 10.8 Incompatibility

    OSX 10.8 Incompatibility

    Running appledoc on OSX 10.8 produces this crash:

    2012-03-08 18:31:51.507 appledoc[24139:707] -[__NSCFConstantString code]: unrecognized selector sent to instance 0x7fff76c3c590
    appledoc version: 2.0.4 (build 703)
    
    Oops, something went wrong...
    NSInvalidArgumentException: -[__NSCFConstantString code]: unrecognized selector sent to instance 0x7fff76c3c590
      @ 0   CoreFoundation                      0x00007fff8ceeaf06 __exceptionPreprocess + 198
      @ 1   libobjc.A.dylib                     0x00007fff8a71579a objc_exception_throw + 43
      @ 2   CoreFoundation                      0x00007fff8cf842aa -[NSObject(NSObject) doesNotRecognizeSelector:] + 186
      @ 3   CoreFoundation                      0x00007fff8ced956e ___forwarding___ + 414
      @ 4   CoreFoundation                      0x00007fff8ced9358 _CF_forwarding_prep_0 + 232
      @ 5   appledoc                            0x000000010c735e2b +[NSException(GBException) reasonWithError:message:] + 43
      @ 6   appledoc                            0x000000010c735dd0 +[NSException(GBException) raise:format:] + 480
      @ 7   Foundation                          0x00007fff89d15bd2 -[NSConcreteTask launchWithDictionary:] + 409
      @ 8   appledoc                            0x000000010c79c571 -[GBTask runCommand:arguments:block:] + 1617
      @ 9   appledoc                            0x000000010c798eba -[GBDocSetOutputGenerator indexDocSet:] + 426
      @ 10  appledoc                            0x000000010c796f7d -[GBDocSetOutputGenerator generateOutputWithStore:error:] + 541
      @ 11  appledoc                            0x000000010c775d03 __42-[GBGenerator runGeneratorStepsWithStore:]_block_invoke_0 + 803
      @ 12  CoreFoundation                      0x00007fff8cee3906 __NSArrayEnumerate + 582
      @ 13  appledoc                            0x000000010c775959 -[GBGenerator runGeneratorStepsWithStore:] + 713
      @ 14  appledoc                            0x000000010c77531e -[GBGenerator generateOutputFromStore:] + 414
      @ 15  appledoc                            0x000000010c72b963 -[GBAppledocApplication application:runWithArguments:] + 2419
      @ 16  appledoc                            0x000000010c7290d8 -[DDCliApplication runWithClass:] + 360
      @ 17  appledoc                            0x000000010c729427 DDCliAppRunWithClass + 103
      @ 18  appledoc                            0x000000010c728298 main + 56
      @ 19  appledoc                            0x000000010c728254 start + 52
    Command /bin/sh failed with exit code 250
    
    opened by odrobnik 22
  • Latest version doesn't install docset in XCode 5.0.1

    Latest version doesn't install docset in XCode 5.0.1

    I don't think the issue is Xcode, though.

    Symptom: Running Appledoc build does not result in docset being available in XCode's (still!) inferior docset viewer.

    Resolution: Reverting to commit aaca91b9b074d59718ea87e574fa4973022e2160 fixes the issue.

    opened by ExoticObjects 21
  • XCode does not show appledoc warnings

    XCode does not show appledoc warnings

    Hiyas

    If this has already been answered or asked before, I apologize, but a quick search for "xcode warnings" hasn't really dug up much. Anyways, I am sure this is a configuration problem on my own, but I can't figure it out how to make it correctly.

    What I want to do is to run appledoc and have it log everything it finds that isn't documented out so that XCode can pick it up when started using an Aggregate.

    I managed to make appledoc working and producing happily documentation with this run script in the aggregate:

    if [ -e "/usr/local/bin/appledoc" ]
    then
    /usr/local/bin/appledoc --create-html --install-docset --project-name "RMTXKit" --project-company "ABACUS Research AG" --company-id "ch.abacus" --output "/Users/misteli/dev/objc/iPhone/Libraries/RMTXKit/Documentation" --publish-docset –logformat=xcode --verbose xcode --keep-undocumented-objects --keep-undocumented-members --keep-intermediate-files --warn-undocumented-object --warn-undocumented-member --warn-empty-description --warn-unknown-directive --merge-categories --merge-category-comment --search-undocumented-doc --warn-missing-arg --no-repeat-first-par --no-warn-invalid-crossref --ignore "*.m" --ignore "*Test.h" --ignore "*Tests.h" --exit-threshold 2 --docset-package-url "http://www.abacus.ch/docs" --docset-feed-url "http://www.abacus.ch/docs" /Users/misteli/dev/objc/iPhone/Libraries/RMTXKit
    fi
    

    I experimented around using the $(PROJECTNAME) variables and more, but for the sake of being able to quickly run it in the console, this current version doesn't use that.

    So.. this builds up all my documentation but it doesn't log anything that isn't documented. Also, if I simply copy/paste the call to a console, appledoc happily runs, creates the documentation but whilst its running it doesn't log anything out other than its version and build number.

    What did I forget to add?

    Thanks!

    Bug 
    opened by fuggly 20
  • Heya, I made the html refs appledoc does generate mirror apple's style.

    Heya, I made the html refs appledoc does generate mirror apple's style.

    I still need to make it generate references for things like Classes, but this is a good first step.

    opened by beelsebob 17
  • GBDocSetInstallGenerator failed generating output, aborting!

    GBDocSetInstallGenerator failed generating output, aborting!

    I found this didn't work on Xcode 8

    opened by kevinls-coder 17
  • Documentation created with appledoc no longer shows quickhelp option to view in Xcode's organizer (4.4)

    Documentation created with appledoc no longer shows quickhelp option to view in Xcode's organizer (4.4)

    When a method is opt+click'd, there is a quickhelp bubble. There used to be an option in this bubble to read more in the organizer, but this option is no longer available for appledoc-generated documentation, starting with Xcode 4.4.

    Known 
    opened by ryanrhee 17
  • Apple Doc disabled

    Apple Doc disabled

    $ brew install appledoc

    Error: appledoc has been disabled because it does not build!

    OS : 11.1 Xcode : 12.4

    opened by SagarPrajapati98 2
  • 还能用吗这个东西

    还能用吗这个东西

    Caught: AppledocException: Path or file '--project-name' doesn't exist! 一直出现这个东西

    opened by huicang800 0
  • Applying XCTest

    Applying XCTest

    Development Environment

    • Xcode 11.3.1 (11C504)
    • macOS Catalina 10.15.4 Beta (19E234g)

    Deployment Target

    • macOS 10.7

    Change Log

    • GHUnit is removed because it's a deprecated project.
    • XCTest is applied.
    • Code coverage is enabled.
    • GBLogX... is replaced with GBLog.... GBLogX... is supposed to print the file name that has the log. But DDLog that GBLog... and GBLogX... are using has an issue to print character array. In order to set the file name to nil, some macros are copied into GBLog.h from DDLog. This is a workaround.

    Todo

    opened by jebeomgyeong 6
  • links in methods

    links in methods

    I wonder if it is possible that custom classes could link to its definitions inside of the method or property definitions?

    example:

    /** a list of objects */
    @property NSArray<MyObject*>* listOfObjects;
    

    MyObject should be a link to the classes definition.

    In Apples current docs, this works. NSColor and NSColorSystemEffect are links to the corresponding pages.

    - (NSColor *)colorWithSystemEffect:(NSColorSystemEffect)systemEffect;
    
    opened by schriftgestalt 1
  • Crashed when a property with class  Keyword

    Crashed when a property with class Keyword

    Define A property like
    @property (nonatomic, class, readonly) NSString *UUID; In @implementation

    • (NSString *)UUID { return @"xxxx"; }

    Oops, something went wrong... AppledocException: Failed merging @property xxxxxxxx.UUID to +[xxxxxxxx UUIDt]; method type doesn't match! @ 0 CoreFoundation 0x00007fff3ed4d43d __exceptionPreprocess + 256 @ 1 libobjc.A.dylib 0x00007fff6ac5a720 objc_exception_throw + 48 @ 2 CoreFoundation 0x00007fff3ed6808e +[NSException raise:format:arguments:] + 98 @ 3 appledoc 0x0000000108f35153 appledoc + 57683 @ 4 appledoc 0x0000000108f4c5a0 appledoc + 152992 @ 5 appledoc 0x0000000108f4c808 appledoc + 153608 @ 6 appledoc 0x0000000108f49335 appledoc + 140085 @ 7 CoreFoundation 0x00007fff3ece29e4 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 219 @ 8 appledoc 0x0000000108f49111 appledoc + 139537 @ 9 appledoc 0x0000000108f4e1ef appledoc + 160239 @ 10 appledoc 0x0000000108f40831 appledoc + 104497 @ 11 appledoc 0x0000000108f38dc0 appledoc + 73152 @ 12 appledoc 0x0000000108f3d7a3 appledoc + 92067 @ 13 appledoc 0x0000000108f3b04e appledoc + 81998 @ 14 appledoc 0x0000000108f3816e appledoc + 69998 @ 15 appledoc 0x0000000108f35fa8 appledoc + 61352 @ 16 appledoc 0x0000000108f3767b appledoc + 67195 @ 17 appledoc 0x0000000108f372ed appledoc + 66285 @ 18 appledoc 0x0000000108f374c1 appledoc + 66753 @ 19 appledoc 0x0000000108f36eaf appledoc + 65199 @ 20 appledoc 0x0000000108f358be appledoc + 59582 @ 21 appledoc 0x0000000108f2a640 appledoc + 13888 @ 22 appledoc 0x0000000108f28df6 appledoc + 7670 @ 23 appledoc 0x0000000108f28f53 appledoc + 8019 @ 24 appledoc 0x0000000108f290e7 appledoc + 8423 @ 25 appledoc 0x0000000108f283ec appledoc + 5100

    opened by Sunny-zhao 4
  • Assertion failure in +[GBMethodData methodDataWithType:result:arguments:], /Users/mac/zln/githubProjects/appledoc/Model/GBMethodData.m:44 appledoc version: 2.2.1 (build 1334)

    Assertion failure in +[GBMethodData methodDataWithType:result:arguments:], /Users/mac/zln/githubProjects/appledoc/Model/GBMethodData.m:44 appledoc version: 2.2.1 (build 1334)

    2018-11-16 10:57:27.027 appledoc[9849:1164779] *** Assertion failure in +[GBMethodData methodDataWithType:result:arguments:], /Users/mac/zln/githubProjects/appledoc/Model/GBMethodData.m:44
    appledoc version: 2.2.1 (build 1334)
    
    Oops, something went wrong...
    NSInternalInconsistencyException: Invalid parameter not satisfying: [arguments count] >= 1
      @ 0   CoreFoundation                      0x00007fff47d5866b __exceptionPreprocess + 171
      @ 1   libobjc.A.dylib                     0x00007fff6efa8942 objc_exception_throw + 48
      @ 2   CoreFoundation                      0x00007fff47d5e252 +[NSException raise:format:arguments:] + 98
      @ 3   Foundation                          0x00007fff49ea3340 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 193
      @ 4   appledoc                            0x000000010439ed5c appledoc + 142684
      @ 5   appledoc                            0x0000000104393272 appledoc + 94834
      @ 6   appledoc                            0x000000010439874b appledoc + 116555
      @ 7   appledoc                            0x0000000104392cc6 appledoc + 93382
      @ 8   appledoc                            0x000000010438ff4e appledoc + 81742
      @ 9   appledoc                            0x000000010438fe62 appledoc + 81506
      @ 10  appledoc                            0x000000010439874b appledoc + 116555
      @ 11  appledoc                            0x00000001043984c8 appledoc + 115912
      @ 12  appledoc                            0x000000010438fde6 appledoc + 81382
      @ 13  appledoc                            0x000000010438f9e4 appledoc + 80356
      @ 14  appledoc                            0x000000010439297f appledoc + 92543
      @ 15  appledoc                            0x0000000104390135 appledoc + 82229
      @ 16  appledoc                            0x000000010438d23e appledoc + 70206
      @ 17  appledoc                            0x000000010438b078 appledoc + 61560
      @ 18  appledoc                            0x000000010438c74b appledoc + 67403
      @ 19  appledoc                            0x000000010438c3bd appledoc + 66493
      @ 20  appledoc                            0x000000010438c591 appledoc + 66961
      @ 21  appledoc                            0x000000010438c591 appledoc + 66961
      @ 22  appledoc                            0x000000010438c591 appledoc + 66961
      @ 23  appledoc                            0x000000010438c591 appledoc + 66961
      @ 24  appledoc                            0x000000010438bf7f appledoc + 65407
      @ 25  appledoc                            0x000000010438a98e appledoc + 59790
      @ 26  appledoc                            0x000000010437f710 appledoc + 14096
      @ 27  appledoc                            0x000000010437dec6 appledoc + 7878
      @ 28  appledoc                            0x000000010437e023 appledoc + 8227
      @ 29  appledoc                            0x000000010437e1b7 appledoc + 8631
      @ 30  appledoc                            0x000000010437d4bc appledoc + 5308
    Command PhaseScriptExecution failed with a nonzero exit code
    
    opened by ProMonkeyZ 0
  • 1. fix GBEnumConstantData instance execute `matchesObject` method crash issue.

    1. fix GBEnumConstantData instance execute `matchesObject` method crash issue.

    1. Use Cocoapods 1.2.0 install.
    2. Specific Minizip/minishared commit id.
    3. fix AppledocTests linking error.
    opened by yanzhiwei147 1
  • No such file or directory

    No such file or directory

    when I execute the command sudo sh install-appledoc.sh I find an error install: /tmp/Build/Intermediates/ArchiveIntermediates/appledoc/InstallationBuildProductsLocation/usr/local/bin/appledoc: No such file or directory my xcode version is xcode 9 and my macOS version is 11 How do I handle this error?

    opened by waittttting 2
  • Command /bin/sh failed with exit code 126

    Command /bin/sh failed with exit code 126

    Hi,

    Not working for XCode 8.3.1. Returning the following error: Command /bin/sh failed with exit code 126

    opened by ghost 7
Releases(2.2.1)
The Swift code generator for your assets, storyboards, Localizable.strings, … — Get rid of all String-based APIs!

SwiftGen SwiftGen is a tool to automatically generate Swift code for resources of your projects (like images, localised strings, etc), to make them ty

null 7.6k Jan 5, 2022
Laurine - Localization code generator written in Swift. Sweet!

Author's note: Thanks everyone for making Laurine the TOP trending Swift repository in the world - this is amazing and very heart-warming! But this is

Jiri Trecak 1.3k Dec 28, 2021
Natalie - Storyboard Code Generator (for Swift)

Natalie Natalie - Storyboard Code Generator (for Swift) Swift Current codebase is Swift 4 compatible. Swift 3.x code may be found from swift3 branch S

Marcin Krzyzanowski 1.2k Dec 26, 2021
Easier to apply code based style guide to storyboard.

Nori Nori designs the view of the storyboard with source code. Usage Label Define the custom class that extends StyleableLabel as @IBDesignable. And i

yukiasai 299 Jun 3, 2021
Xcode .appiconset generator for Adobe Illustrator.

Creating AppIcon sets from Adobe Illustrator This repo is rewrited from original repo https://github.com/CaryChamplin/CreatingIconsFromAI. Just genera

gitmerge 73 Nov 8, 2020
AVXCAssets Generator takes path for your assets images and creates appiconset and imageset for you in just one click

AVXCAssets Generator Often while developing an app, We ran into a condition when we need to scale images to each and every aspect ratios for icons and

Angel Vasa 331 Nov 16, 2021
A license list generator of all your dependencies for iOS applications

LicensePlist LicensePlist is a command-line tool that automatically generates a Plist of all your dependencies, including files added manually(specifi

Masayuki Ono (mono) 2k Jan 5, 2022
Set of easy to use debugging tools for iOS developers & QA engineers.

DBDebugToolkit DBDebugToolkit is a debugging library written in Objective-C. It is meant to provide as many easily accessible tools as possible while

Dariusz Bukowski 1.1k Jan 13, 2022
Soulful docs for Swift & Objective-C

jazzy is a command-line utility that generates documentation for Swift or Objective-C About Both Swift and Objective-C projects are supported. Instead

Realm 7.1k Jan 4, 2022
An Xcode Plugin to convert Objective-C to Swift

XCSwiftr Convert Objective-C code into Swift from within Xcode. This plugin uses the Java applet of objc2swift to do the conversion. Noticed that the

Ignacio Romero Zurbuchen 341 Nov 17, 2021
A static analyzer for Java, C, C++, and Objective-C

Infer Infer is a static analysis tool for Java, C++, Objective-C, and C. Infer is written in OCaml. Installation Read our Getting Started page for det

Facebook 12.9k Jan 11, 2022
Trace Objective-C method calls by class or instance

Xtrace Note: This project has been superseeded by the more rigourous SwiftTrace. Trace Objective-C method calls by class or instance Xtrace is a heade

John Holdsworth 1.8k Nov 29, 2021
Swizzlean, an Objective-C Swizzle Helper Class.

Swizzlean A quick and "lean" way to swizzle methods for your Objective-C development needs. Adding Swizzlean to your project Cocoapods CocoaPods is th

Ryan Baumbach 103 Jun 29, 2021
Storyboard -> SwiftUI Converter 1.4 0.0 Objective-C is a converter to convert .storyboard and .xib to SwiftUI.

World's #1 Objective-C to Swift Converter Issues / Feedback / Feature Requests Swiftify Help Center Swiftify for Xcode Swiftify AppCode plugin Online

Swiftify 25 Oct 18, 2021
An Xcode plug-in to format your code using SwiftLint.

SwiftLintXcode An Xcode plug-in to format your code using SwiftLint. Runs swiftlint autocorrect --path CURRENT_FILE before *.swift file is saved. IMPO

Yuya Tanaka 338 Dec 21, 2021
The Benchmark⏲ module provides methods to measure and report the time used to execute Swift code.

Benchmark The Benchmark ⏲ module provides methods to measure and report the time used to execute Swift code. Installation Carthage // Cartfile github

WorldDownTown 85 Nov 6, 2021
Meta-programming for Swift, stop writing boilerplate code.

Sourcery is a code generator for Swift language, built on top of Apple's own SwiftSyntax. It extends the language abstractions to allow you to generat

Krzysztof Zabłocki 6.3k Dec 31, 2021
A tool for defining design systems and using them to generate cross-platform UI code, Sketch files, and other artifacts.

Lona (Developer Preview) This project is in an early stage and lacks documentation – however, with some effort, it can be used very effectively. If yo

Airbnb 7.5k Jan 14, 2022
A programming language for generating code for multiple platforms

Zolang • ZolangTemplates • Zolang IDE Table of Contents What is it? What Zolang is Not Documentation Installation Getting Started Example Language Ove

Zolang 132 Jan 4, 2022