Thank you Peter. I understand all of that... :-) Le 9 mai 2010 à 16:13, Peter Alcibiades a écrit : > > Things are 'originally written' in, for > instance, French, when this was the first version of the novel that was > written. Translations into English are not originally written in English. > It may seem hard to define exactly, but its clear to most people what does > and does not count as originally written.
In literrature there is case of a writer who write in a language et rewrite (himself) in another language (Nabokov by example) > > In short, do not write originally in anything but the approved languages, > and if you do, do not compile and link against the APIs. > > -- It finally says that "Applications that link to Documented APIs through > an intermediary translation or compatibility layer or tool are prohibited". > Now, this is a for example, so it is not exhaustive. But what it is telling > you is that you cannot use an intermediary translation tool. You cannot do > what you are trying to do. > > What's the bottom line? You can write your C or C++ using whatever you > want. Eclipse or notepad, they do not care. But you will write C or C++ in > the editor or IDE of your choice. You will not write revtalk or anything > else, and have that translate into C. > Have you red my last posts (with the explanation of "my method" ;-) ? > > > There is really no doubt about what this means. As to whether its > enforceable, the answer is, in the short to medium term, undoubtedly. > Because there is an enforcement mechanism, they don't have to let your app > into the App store, and they don't have to give a reason for refusal. So > mere suspicion that you have done it in the wrong language and translated > it, will get your app barred. And they are not interested, they simply do > not care, if they ban some apps incorrectly. There is nothing you can do > about it. They do not even have to tell you what their reason was. > > The only people who will change this will be the courts and the competition > regulators in the US. By the time they get around to it, and by the time a > settlement is worked out, if they overturn it, and by the time the > boundaries of that settlement are fixed, it will be too late for you as an > iPhone developer. Yes I think also > > You have to understand that finding some way around the wording does not > help at all. Even if you were to find one, which you won't, you will just > get banned anyway for finding a way around and using it. > > You want to develop for iPhone OS as a business, you now have two and only > two practical choices. One, get busy on C or iPhone Java. Two, develop > webapps as in Rodeo. The safest is probably flavors of C. The quickest is > probably Rodeo. Save time, and accept it. > It's seems to be wise, indeed, I am interested in Rodeo but is seems complicated (!?) Thank you again Bon souvenir de Paris René _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution