From: Sascha H. <sa...@xm...> - 2010-06-23 09:37:17
|
I agree. Seems like this shouldn't be a big deal, if the API hasn't changed much. Of course there is a lot of new API, but the old one is probably mostly untouched, right? On Wed, Jun 23, 2010 at 11:30 AM, Arno Puder <ar...@pu...> wrote: > > correct me if I'm wrong, but it sounds like we can do a command line > option for now and deal with this difference. Those developers who still > want to target 3.* (and therefore should not update to the iOS4 SDK) can > still use XMLVM. > > Arno > > > On 6/23/10 11:21 AM, Panayotis Katsaloulis wrote: > > > > On Jun 23, 2010, at 11:15 AM, Arno Puder wrote: > > > >> does this mean you have to change the way Xcode projects are generated > >> by XMLVM for iOS4 and that change would not be backward compatible with > >> iOS 3.1 and 3.2? > > > > Yes, unfortunately. > > > > > > On Jun 23, 2010, at 11:16 AM, Sascha Haeberling wrote: > > > >> what are the things that need to change right now to write apps with > XMLVM for iOS? Did the existing APIs change dramatically? I guess the XCode > project creator need to be adapted? If it's just the latter, I would propose > to introduce a legacy argument that uses the current XCode code creation and > have the current one create new XCode projects. > > > > The API has changed, but not so drastically. > > What is actually happened is that the current version of the SDK has > support ONLY for the 4.0 version of iOS, while the old (and vanished) > versions of the SDK have of course support ONLY for version prior of 4.0 :) > > Clever, eh? > > > > The Xproject creator of course needs to be updated. > > > > If a project is created for iOS4, then the project (not the java code) > could not be compatible with the older versions. > > With older SDK's of course it is not able to be loaded. > > > > If a project is created for version 3.1 (the latest fully supported > version), then this project is not compatible with current iOS SDK (but it > *is* binary compatible with older versions). > > With the current SDK, the user should make a couple of not obvious > changes to the project in order to able to compile& publish it. > > > > > > > > > ------------------------------------------------------------------------------ > > ThinkGeek and WIRED's GeekDad team up for the Ultimate > > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > > lucky parental unit. See the prize list and enter to win: > > http://p.sf.net/sfu/thinkgeek-promo > > _______________________________________________ > > xmlvm-users mailing list > > xml...@li... > > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users > |