3 ms·
That's what is suggested by this blog: http://blog.backblaze.com/2008/12/15/10-rules-for-how-to-write-cross-platform-code/ http://blog.backblaze.com/2008/12/15
by bluedino 13y ago
That's what is suggested by this blog:
http://blog.backblaze.com/2008/12/15/10-rules-for-how-to-write-cross-platform-code/ http://blog.backblaze.com/2008/12/15/10-rules-for-how-to-wri...
Rule #2: Factor out the GUI into non-reusable code – then develop a cross-platform library for the underlying logic
I'd like to hear others experiences and views with doing that as opposed to using something like QT or GTK.
- bcoates 13y agoThat link has some solid advice. I had to learn a lot of that the hard way.
- ballard 13y agoThis makes sense, since vying for cross-platform tends to result in awkward experiences like the windows Treo. Using MVC, it's more straightforward what components are specialized per OS and which ones are common. Not only that, having native apps would make the app UX "feel" better too.
- erichocean 13y agoThat's exactly how the iOS app I'm building right now is factored, specifically so that all of the networking/model layer/sync code is identical between iOS and Android. I'm using libuv, SQLite, CurveCP/NaCl and MessagePack for the cross-platform stuff, and the rest of the code is straight C (which I prefer to C++). So far, it's working well, although it did require more effort to set up initially, primarily due to multi-threading.