├── icon.png ├── Screenies └── screenshot.png ├── .travis.yml ├── PBJDebuggingTools └── Classes │ └── PBJDLog │ └── PBJDLog.h ├── PBJDebuggingTools.podspec ├── LICENSE ├── CONTRIBUTING.md ├── README.md └── CODE_OF_CONDUCT.md /icon.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/SnugJoker/PBJDebuggingTools/HEAD/icon.png -------------------------------------------------------------------------------- /Screenies/screenshot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/SnugJoker/PBJDebuggingTools/HEAD/Screenies/screenshot.png -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: objective-c 2 | osx_image: xcode9 3 | 4 | env: 5 | global: 6 | - LC_CTYPE=en_US.UTF-8 7 | - LANG=en_US.UTF-8 8 | -------------------------------------------------------------------------------- /PBJDebuggingTools/Classes/PBJDLog/PBJDLog.h: -------------------------------------------------------------------------------- 1 | // 2 | // PBJDLog.h 3 | // MishlochimNative 4 | // 5 | // Created by Joseph Razon on 11/08/2016. 6 | // Copyright © 2016 zap. All rights reserved. 7 | // 8 | 9 | 10 | #ifndef PBJDLog_h 11 | #define PBJDLog_h 12 | 13 | 14 | #ifdef DEBUG 15 | 16 | #define DLog(...) NSLog(@"%s [Line %d]: %@", __PRETTY_FUNCTION__, __LINE__, [NSString stringWithFormat:__VA_ARGS__]) 17 | 18 | #define ALog(fmt, ...) NSLog((@"%s [Line %d] " fmt), __PRETTY_FUNCTION__, __LINE__, ##__VA_ARGS__); 19 | 20 | #define ULog(fmt, ...) { UIAlertView *alertLog = [[UIAlertView alloc] initWithTitle:[NSString stringWithFormat:@"%s\n [Line %d] ", __PRETTY_FUNCTION__, __LINE__] message:[NSString stringWithFormat:fmt, ##__VA_ARGS__] delegate:nil cancelButtonTitle:@"Ok" otherButtonTitles:nil]; [alertLog show]; } 21 | 22 | 23 | #else 24 | 25 | 26 | 27 | #endif 28 | 29 | #endif 30 | -------------------------------------------------------------------------------- /PBJDebuggingTools.podspec: -------------------------------------------------------------------------------- 1 | # 2 | # Be sure to run `pod lib lint PBJAnimations.podspec' to ensure this is a 3 | # valid spec before submitting. 4 | # 5 | # Any lines starting with a # are optional, but their use is encouraged 6 | # To learn more about a Podspec see http://guides.cocoapods.org/syntax/podspec.html 7 | # 8 | 9 | Pod::Spec.new do |s| 10 | s.name = 'PBJDebuggingTools' 11 | s.version = '1.0.1' 12 | s.summary = 'Animations & transitions framework.' 13 | s.description = 'PBJDebuggingTools is a simple framework for adding animations in no time.' 14 | s.homepage = 'https://github.com/SnugJoker/PBJDebuggingTools' 15 | s.license = { :type => 'MIT', :file => 'LICENSE' } 16 | s.author = { 'Joseph Razon' => 'razonjoe@gmail.com' } 17 | s.source = { :git => 'https://github.com/SnugJoker/PBJDebuggingTools.git', :tag => s.version.to_s } 18 | 19 | s.ios.deployment_target = '8.0' 20 | 21 | s.source_files = 'PBJDebuggingTools/Classes/PBJDLog/*' 22 | s.public_header_files = 'PBJDebuggingTools/Classes/PBJDLog/*.h' 23 | 24 | 25 | end 26 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Copyright (c) 2018 josephrazon 2 | 3 | Permission is hereby granted, free of charge, to any person obtaining a copy 4 | of this software and associated documentation files (the "Software"), to deal 5 | in the Software without restriction, including without limitation the rights 6 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 7 | copies of the Software, and to permit persons to whom the Software is 8 | furnished to do so, subject to the following conditions: 9 | 10 | The above copyright notice and this permission notice shall be included in 11 | all copies or substantial portions of the Software. 12 | 13 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 14 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 15 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 16 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 17 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 18 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN 19 | THE SOFTWARE. 20 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | We love contributions from everyone. 4 | By participating in this project, 5 | you agree to abide by the thoughtbot [code of conduct]. 6 | 7 | [code of conduct]: https://thoughtbot.com/open-source-code-of-conduct 8 | 9 | We expect everyone to follow the code of conduct 10 | anywhere in thoughtbot's project codebases, 11 | issue trackers, chatrooms, and mailing lists. 12 | 13 | ## Contributing Code 14 | 15 | $(INSTALL_DEPENDENCIES) 16 | 17 | Fork the repo. 18 | 19 | Make sure the tests pass: 20 | 21 | $(TEST_RUNNER) 22 | 23 | Make your change, with new passing tests. Follow the [style guide][style]. 24 | 25 | [style]: https://github.com/thoughtbot/guides/tree/master/style 26 | 27 | Mention how your changes affect the project to other developers and users in the 28 | `NEWS.md` file. 29 | 30 | Push to your fork. Write a [good commit message][commit]. Submit a pull request. 31 | 32 | [commit]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html 33 | 34 | Others will give constructive feedback. 35 | This is a time for discussion and improvements, 36 | and making the necessary changes will be required before we can 37 | merge the contribution. 38 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # PBJDebuggingTools 2 | 3 | [![Build Status](https://travis-ci.org/SnugJoker/PBJDebuggingTools.svg?branch=master)](https://travis-ci.org/SnugJoker/PBJDebuggingTools) 4 | [![Version](https://img.shields.io/cocoapods/v/PBJDebuggingTools.svg?style=flat)](http://cocoapods.org/pods/PBJDebuggingTools) 5 | [![License](https://img.shields.io/cocoapods/l/PBJDebuggingTools.svg?style=flat)](http://cocoapods.org/pods/PBJDebuggingTools) 6 | [![Platform](https://img.shields.io/cocoapods/p/PBJDebuggingTools.svg?style=flat)](http://cocoapods.org/pods/PBJDebuggingTools) 7 | ![Languages](https://img.shields.io/badge/Language-Objective%20C-orange.svg?longCache=true&style=flat) 8 | [![BCH compliance](https://bettercodehub.com/edge/badge/SnugJoker/PBJDebuggingTools?branch=master)](https://bettercodehub.com/) 9 | ![CocoaPods](https://img.shields.io/cocoapods/dt/PBJDebuggingTools.svg) 10 | [![Donate](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://paypal.me/JoeRazon) 11 | 12 | 13 | ### Content 14 | * DLog 15 | 16 | ## Requirements 17 | No requirements needed. 18 | 19 | ## Example 20 | ![Screenshot](Screenies/screenshot.png) 21 | 22 | ## Installation 23 | PBJDebuggingTools is available through [CocoaPods](http://cocoapods.org). To install 24 | it, simply add the following line to your Podfile: 25 | 26 | ```ruby 27 | pod 'PBJDebuggingTools' 28 | ``` 29 | 30 | ## How To Use 31 | To use PBJDebuggingTools first import the class: 32 | 33 | *Import 34 | ```objectivec 35 | #import 36 | ``` 37 | 38 | Then simply add one of the methods to your code: 39 | ```objectivec 40 | DLog(@""); 41 | ``` 42 | ```objectivec 43 | ALog(@""); 44 | ``` 45 | ```objectivec 46 | ULog(@""); 47 | ``` 48 | 49 | ## Author 50 | Joseph Razon, razonjoe@gmail.com 51 | 52 | ## License 53 | PBJDebuggingTools is available under the MIT license. See the LICENSE file for more info. 54 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | * Using welcoming and inclusive language 12 | * Being respectful of differing viewpoints and experiences 13 | * Gracefully accepting constructive criticism 14 | * Focusing on what is best for the community 15 | * Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | * The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | * Trolling, insulting/derogatory comments, and personal or political attacks 21 | * Public or private harassment 22 | * Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | * Other conduct which could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Our Responsibilities 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. 30 | 31 | ## Scope 32 | 33 | This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. 34 | 35 | ## Enforcement 36 | 37 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at razonjoe@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. 38 | 39 | Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. 40 | 41 | ## Attribution 42 | 43 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version] 44 | 45 | [homepage]: http://contributor-covenant.org 46 | [version]: http://contributor-covenant.org/version/1/4/ 47 | --------------------------------------------------------------------------------