On May 23, 2011, at 4:23 AM, Matt Gough wrote:

> There is some discussion that our cross-platform app should switch to using 
> WebKit for its UI (using embedded HTML/CSS/JavaScript), instead of the 
> current divergent code paths of Cocoa on Mac and native Windows stuff on PC. 
> Our app doesn't have much UI. Just a few configuration panels and error 
> message handling. Is is not a document-based app.
> 
> I am currently looking for opinions on the pros and cons of such a move. 
> 
> My main concerns are:
> 
> Can the Mac the version comply with HI guidelines and hence get approved for 
> the App Store solely using WebViews? This is my main concern, if we would 
> fail App Store automatically for going this route, then it is a non-starter.
> 
> Is debugging the UI going to be a nightmare?
> 
> What expected/standard UI behaviours are going to go AWOL (or become much 
> harder to implement without going through hoops)
> 
> We could still really end up with divergent code anyway, just in the html/css.
> 
> Thanks in advance for any input
> 
> Matt_______________________________________________
> 
It really depends on how much  UI you need reinvent every time. From what you 
describe, it doesn't sound like there is all that much benefit to this move.
Both platforms would still have significant differences in wiring things up to 
a WebKit UI.
Often, there is just a certain amount of work that must be done. 
It is much the same as doing localization.
As long as the differences between the two are clear and well-defined, it will 
just be wiring it up.
Apps that try to be somehow universal without trying to behave naturally on a 
given OS usually suffer for it. 

_______________________________________________

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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to