3 ms·
Just a note: from Mac user perspective cross-platform often means second-rate. Portable toolkits just copy superficial look of Cocoa controls, but don't mimic
by pornel 16y ago
Just a note: from Mac user perspective cross-platform often means second-rate.
Portable toolkits just copy superficial look of Cocoa controls, but don't mimic "feel" part correctly. Not all mouse interactions and keyboard shortcuts work "right".
And even if your toolkit uses real Cocoa controls, there's still problem of window layout and UI design patterns, which aren't portable to Mac OS X (e.g. non-destructive preferences don't have OK/Apply buttons, drag'n'drop is expected almost everywhere, OK/Cancel are in reverse order than on Windows, etc.)
e.g. do you know OS X has separate clipboard for search fields? Cmd+E/Cmd+G. I like it and use it, but it doesn't work in "fake" Mac apps.
If you want to make good portable app that supports Mac well, then separate UI from the rest of the application and on Mac add Cocoa GUI (you don't need ObjC, you can use PyObjC or MacRuby).
- cjg 16y agoThe OP didn't say he wanted to make a cross-platform app or a portable one.
- VBprogrammer 16y agoHe also didn't specify which platform he was targeting. A lot of the points pornel mention apply equally to GUI toolkits running on Windows or Linux. You sacrifice some control in order to get cross-platform compatibility (as you have to do with certain CSS / Javascript elements). Java is probably the worst of all worlds in terms of the look and feel of its de-facto standard GUI library.
- umenline 16y agowell cross platform is a dream , but i do know its so hard when you working with desktop app. my toolkit is Qt. i guess first i will go with windows.