News for hackers. Stuff that matters.
Re:Chameleon - UIKit for Mac development by shaggyfrog on Tuesday March 22, 2011 @02:38PM (#2355763)
I really don't get the point of this at all. When I've ported iPhone apps to iPad (i.e. make them Universal) there was always little-to-no work to do on the underlying model classes, but always a lot of work to do designing new views since the UI model is so much different (mainly from the bigger screen). Same deal with Mac OS X, except the UI changes are even more extreme. If I want my iOS app to work on a Mac's screen, I'll have to spend the time to redesign the UI. Which is fine, so how is this thing going to save me any time at all, really?
Re:Chameleon - UIKit for Mac development by joshaber on Tuesday March 22, 2011 @03:27PM (#2356011)
But AppKit is pretty awful. I'm much more interested in Chameleon as a Core Animation-based replacement for AppKit than as an easy way to port iOS apps.
Re:Chameleon - UIKit for Mac development by glhaynes on Tuesday March 22, 2011 @02:50PM (#2355810)
It could be useful for lots of folks that know UIKit inside and out but haven't dealt with AppKit before.
Re:Chameleon - UIKit for Mac development by shaggyfrog on Tuesday March 22, 2011 @03:06PM (#2355893)
But a Mac's interface is not an iOS interface. There are different constraints and different best practices, and sometimes completely different widgets. To make a decent UI, you have to understand the native platform.
Re:Chameleon - UIKit for Mac development by silkodyssey on Tuesday March 22, 2011 @08:56PM (#2357380)
I think the same argument can be made with regard to iPhone apps running on iPad. iPhone apps on the iPad are not very pleasant but if you absolutely must have that iPhone app on your iPad then you can put up with a suboptimal experience just to have the functionality.

I think the same thing occurs on the desktop. Many times I use iPad applications and wish they were available on the desktop. iPad applications especially I think can work very well on the desktop due to the large display.

But don't take my work for it. Have a look at the streamtome app on the mac app store. The interface mimics that of the iPad. I am not sure if it uses chameleon but there's a good chance I would guess.

http://itunes.apple.com/app/streamtome/id405892506?mt=12

Re:Chameleon - UIKit for Mac development by gte910h on Tuesday March 22, 2011 @03:13PM (#2355938)
Sometimes perfect is the enemy of the good.

The ability of a stopgap measure such as this is a good way to let established iOS players test the Mac waters without a huge investment.

Re:Chameleon - UIKit for Mac development by glhaynes on Tuesday March 22, 2011 @04:31PM (#2356330)
Definitely agree. And no doubt this is why Apple hasn't announced UIKit on Mac (yet).
Re:Chameleon - UIKit for Mac development by scrod on Tuesday March 22, 2011 @04:03PM (#2356188)
>It could be useful for lots of folks that know UIKit inside and out ...

Then they'll have a very easy time picking up AppKit — certainly much easier than someone coming from any other platform would have, mobile or desktop. The lineage from AppKit is supposed to be one of the advantages of UIKit. These frameworks are very similar.

Re:Chameleon - UIKit for Mac development by joshaber on Tuesday March 22, 2011 @04:07PM (#2356211)
AppKit and UIKit aren't at all similar. And they aren't related. UIKit was written from the ground up for iOS and is based on Core Animation. AppKit was written by NeXSTEP and is based on software rendering with dirty rects.
Re:Chameleon - UIKit for Mac development by kenferry on Tuesday March 22, 2011 @05:32PM (#2356616)
This argument seems strange to me.

UIKit was written, from the ground up, by people who either worked on AppKit or worked with AppKit, with full access to the AppKit source base. They share almost all design patterns, and some source code. UIKit is clearly based on AppKit.

Pervasive use of layers is indeed a difference. That's hardly the only thing interesting about either framework, though.

Re:Chameleon - UIKit for Mac development by joshaber on Tuesday March 22, 2011 @05:43PM (#2356655)
Compare NSView vs. UIView. Or NSViewController vs. UIViewController. Or NSTableView vs. UITableView. NSButton vs. UIButton. Same names but very different design patterns and APIs.

I've worked on many iOS and Mac apps. I'm honestly not sure how anyone can claim AppKit and UIKit are essentially the same.

Re:Chameleon - UIKit for Mac development by kenferry on Tuesday March 22, 2011 @06:06PM (#2356745)
What would you consider the essential Cocoa design patterns? I would point at the items listed at http://developer.apple.com/library/ios/#documentation/Cocoa/... . Delegation, notification, target action, the responder chain - these are all shared.

The frameworks are not identical, but to say they're not related… they only look wildly different if you're focusing in incredibly closely. If you consider .Net, or Java, or Rails, or GTK, or almost anything else, the differences between AppKit and UIKit are miniscule.

Re:Chameleon - UIKit for Mac development by ajg1977 on Tuesday March 22, 2011 @07:17PM (#2357026)
Nobody is saying that that they're not related. They clearly are (although the presence of other UI libraries does not affect any comparison of that relationship at all.

Your examples of delegates, responders, targets etc are concepts - and indeed UIKit and AppKit are both built around the same concepts.

The implementations of both is quite different however, to the point that porting something of complexity from UIKit to AppKit involves a lot of tedious changes - or worse: creation of abstraction layers if the codebase is to be maintained for both apps.

Re:Chameleon - UIKit for Mac development by scrod on Tuesday March 22, 2011 @06:01PM (#2356725)
> AppKit and UIKit aren't at all similar. And they aren't related.

Actually, they're incredibly similar in terms of class hierarchy, design patterns (e.g., delegates, data sources, target/action for the most part), graphics principles (points vs pixels), use of various Foundation and CoreGraphics data structures, etc.

And yes, Core Animation works quite well with layer-backed views in AppKit, which is where it started.

It's easy to point out specific differences between these frameworks, but I think any developer who's already learned one would object to the underestimation of his/her intelligence that would be implied by comparing the subsequent difficulty in moving to the other with that of any other non-Apple platform SDK.

Perhaps you'd like to point out another SDK that is more similar to AppKit than UIKit?