Tricertops
Roadmap
Current iteration: 0.2.0
Note: Features, where only test are missing, should work as expected. They are just not formally tested.
Producers
- [x] Command + Tests
- [x] Hub + Tests
- [x] Property + Tests
- [x] Notificator + Tests
- [x] Timer + Tests
- [x] Invoker + Tests
- [x] Action Target (missing Tests)
- [ ] Task ?? Does it make sense to abstract a task as a Producer of values? Maybe.
Mediators
- [x] Bridge + Tests
- [x] Context + Tests
- [x] UIKit Contexts (missing Tests)
- [x] Filter + Tests
- [ ] Gateway
- [x] Throttle + Tests
- [x] Interpolator + Tests
- [ ] Delayer ?
- [ ] Reproducer ?
Consumers
- [x] Subscriber + Tests
- [x] Property + Tests
- [x] Switch + Tests
- [ ] UIButton setters (missing Tests)
Transformers
- [x] Basic + Tests
- [x] Collections (NSArray, NSDictionary, …) + Tests
- [x] Math + Tests
- [x] NSString and related (missing Tests)
- [x] NSDate and related (missing Tests)
- [x] NSData (missing Tests)
- [x] CGPoint (missing Tests)
- [x] CGSize (missing Tests)
- [x] CGRect (missing Tests)
- [x] CGAffineTransform (missing Tests)
- [x] UIEdgeInsets (missing Tests)
- [x] CATransform3D (missing Tests)
- [x] UIColor
- [x] UIImage
Predicates
- [x] Basic (missing Tests)
- [x] Geometry
Utilities
- [x] Decomposer + Tests
- [x] Queue + Tests
- [x] Key-Path Accessor + Tests
- [x] Structure Accessor + Tests
- [x] Invocation Catcher + Tests
Hi! Why don't you publish it as a Cocoapod? At least you may creadte Podspec for the repo and allow to use it as private pod (with direct link to the repo). I can do it for you and make a pull request, what do you think?
Hi, I don't use CocoaPods. If you need a config file, create a Pull Request and I will include it :)
The problem is, you would be able to use only tagged versions of the repo, right? This is work in progress, so I don't have strict versioning. Should I mark every important commit on master as x.x.1 increment?
No, you do not need to do anything special. There is a way to use just the most recent version of source code from default branch on a repo, you just need to point explicitly exact repo URL in the Podfile.
Here is an example: pod 'CocoaTouchHelpers', :git => 'https://github.com/maximkhatskevich/CocoaTouchHelpers.git'
If you specify a pod in Podfile this way - it ignores settings from Podspec file and just fetches latest commit from default branch. You even do not need to publish your Pod on Cocoapods at all. The target repo just need to have correct Podspec in repo root.
So I'll add Podspec and will start pull request, all you need to do is just approve it.
I don’t have strict versions in this project, the latest commit of master is the most usable revision. Does the CocoaPods allow you to use repos this way?
Yes, there are two ways:
Option 1:
You can publish a 0.1 version into the CocoaPods master repo and state that the project is under active development, but ready to try. Users can then install as follows:
pod 'Obejctive-Chain', :head
The advantage of publishing to the master repo is that:
- Let's people search and find the project
- Users can read CocoaPods generated API documentation.
(Alternatively at www.typhoonframework.org, we have our API docs regenerated after each push and committed to gh-pages. They're available at http://www.typhoonframework.org/docs/latest/api/ )
Option 2:
Place the *.podspec file in the root folder of this repository. Users can then install with:
pod 'Objective-Chain', :git => '[email protected]:iMartinKiss/Objective-Chain.git'
In either of the above cases CocoaPods users will be able to do continuous integration (ie install latest changes) by calling pod update
Sorry, didn’t have time for GitHub for past few weeks.
It would be great if any of you could submit a Pull Request with the podspec (as @maximkhatskevich promised). Looks like you, guys, have more experience with pods than me. I think you can do it directly from GitHub website.
Thanks.