On 14/06/2013, at 6:15 PM, Daniele Margutti <m...@danielemargutti.com> wrote:
> No offence guy, but seriusly I can’t. We have a compatible UIKit layer which > can run on OS X. In order to mantain compatibility I need to handle > UIApplication and UIScreen singleton; morehower I need to manage > UIAppearance. This thing can’t work on with multiple projects at the same > time so in order to work with it I need to isolate each project/UIKit > instance/process from the other. That's exactly the sort of thing I'm referring to - for whatever reason your design is incorrect, so you're now trying to "fix" that by adding more incorrectness. The split between your controller and view layer is in the wrong place. By refactoring you can replace your view layer by a native OSX one and not attempt to add a layer ON TOP of your view layer to make Mac OSX look like UIKit. While I haven't had much experience on iOS yet, I have made a few simple apps that work across iOS and Mac OS and by and large these share 70% or more of the controller and model code. Most of the view stuff comes from xibs and so in reality there isn't that much code that differs. I would accept that your app is a lot more complicated than mine, but nevertheless the right approach should make cross-platform deployment reasonably straightforward. It's much easier than, say, Windows/Mac cross-platform, at least the whole thing can be in Cocoa. --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
