3 ms·
I mean, the better (for users, maybe not for developers) alternative is to buck up and build a native client for each platform. Share as much code as you can po
by ryandrake 4y ago
I mean, the better (for users, maybe not for developers) alternative is to buck up and build a native client for each platform. Share as much code as you can portably, but you'll have a small platform-specific shim around the edges to call into the shared business logic and implement the platform-specific window management and bling.
- karencarits 4y agoYes, this is very reasonable for some kinds of software. For other kinds of software, the users may consist of a small team - say the teachers at a school or a specific research group or a family - where some are using Mac and others are using Windows Sometimes, developing a simple tools should be simple (without all the overhead of shared business logic, etc.), but in my experience, there is too many obstacles to make simple GUI tools that just works. It's a shame, I believe that many teams would have increased their efficiency if there were easier ways for individuals to make simple tools adapted to their specific needs. Now, they are typically stuck with Excel...
- krapp 4y ago>but you'll have a small platform-specific shim around the edges to call into the shared business logic and implement the platform-specific window management and bling No you won't. We've had cross-platform libraries like SDL to do that for ages.