Closed delebedev closed 10 years ago
The reason because CDEKit does not share any code with the OS X project is the following:
Core Data Editor for OS X has been developed first without CDEKit in mind. When I finished Core Data Editor I began to experiment with extracting functionality from the Core Data Editor OS X application into CDEKit by copy & paste (and removing OS X specific code). This is what became CDEKit. I have never distributed nor sold CDEKit because I had no time to finish it.
The intention was to extract all the non-GUI functionality from the OS X app into CDEKit and then let the OS X app use CDEKit and then make an iOS static library based on CDEKit. :)
So code SHOULD be shared among CDEKit and the OS X app as time goes on in my opinion.
So I would prefer if CDEKit could do more things and have the OS X app depend on CDEKit.
What do you think?
That makes sense for me. I've seen some of files are already duplicated. Also 'CDE' core might be easier to test since it will become basically a (lot) of categories :)
I would like to have possibility to embed
CDEKit
in my iOS app for debugging via Cocoapods. Of course it's possible to write podspec and place it in this repo, but it would be painful to clone all the git repo with mac app and assets just to have it's iOS part. Note thatCDEKit
does not share any code withOS X
project and can be safely extracted. It also will allow to setup Travis for iOS in particular.@ChristianKienle what do you think?