>> Then I wonder how to deal with the MIT licence if I have to deploy a >>commercial app.
The MIT license tells you - you have to provide a copy of the copyright notice and permission statement (essentially a copy of the license file) with all copies of the software, although I'm sure Monte isn't planning to sue anyone who doesn't. There is nothing that says you have to make a copy of the license highly visible or easy to access, so you could just add it to the app bundle as an external file. However, generally accepted practice is to either include the license in an about box in your app if you have one, or add it to the end of your EULA on the App Store if you don't. >> Then, to sumarize, at the present time, what is the best practice to create >>a little commercial app for the iOS devices ? There isn't really an ideal solution at the moment, so it depends on your current and expected future requirements. How long is the app likely to be maintained? Might you ever want to build it for Android? >> - build an app with several different layouts taylored according the >> "iphoneUseDeviceResolution" This works for iOS only but as an approach doesn't scale to Android where there are so many more resolutions to deal with. The native iOS development community have been strongly encouraged towards auto-layout recently which suggests there may be some additional resolutions on the way for iOS too. >> - installingMobGui plugin and let this software to manage the resolution >> issues I believe the future of this plugin will remain uncertain until RunRev have released (or at least revealed much more detail on) their resolution independence and native platform themes functionality. It would work for now but you *might* need to switch away from it in the future. >> - using mApp framework This appears to be a viable long term solution across all platforms but as you say it doesn't really have any documentation yet, so there will be a greater learning curve. >> - wait for the "resolution independence" be integrated in LiveCode If you have no time pressure then this is the easiest option but I wouldn't count on having something complete and stable in the next few months. It's also not yet clear that this will be sufficient for most apps or if you'll still need something like mApp to manage layouts dynamically - from what I've read about the feature so far it looks like the latter may be the case. Hope that helps, Mark _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
