[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On April 9, 2010, Matthew Leverton wrote:
> On Fri, Apr 9, 2010 at 12:19 AM, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>
wrote:
> > On April 8, 2010, Matthew Leverton wrote:
> >> On Thu, Apr 8, 2010 at 3:34 PM, Peter Hull <peterhull90@xxxxxxxxxx>
wrote:
> >> > Just wondering, does Allegro 5 count as a 'compatibility layer'?
> >> >
> >> > http://daringfireball.net/2010/04/iphone_agreement_bans_flash_compi
> >> > ler
> >>
> >> Even the previous wording: "3.3.1 — Applications ... must not use or
> >> call any private APIs" makes Allegro illegal.
> >
> > I'm pretty sure that meant private iPhone apis.
>
> That's quite likely, but it ultimately really doesn't matter. I've
> known people who have had apps rejected already per the old 3.3.1,
> without ever being told exactly what was meant. You're always going to
> be at the mercy of Apple on whether or not you are worthy enough to
> publish something on the store.
>
> It will be interesting to see Apple's official response to this. My
> guess is they will remain as secretive as ever, hoping to simply scare
> people away from using any of the big cross platform tools and
> building only for the iPhone. Obviously they will claim this is all
> about "user experience," but if that were true they would simply
> prohibit junk from being posted to the store regardless if it were
> written only in Objective C only for the iPhone.
>
> But I cannot fathom them categorically preventing people from using a
> third party library written directly in C/C++. It's such a fuzzy line
> to draw.
I'm willing to bet they will use it as an excuse to reject crappy (as per
their own definition, whatever that is) apps, while still allowing well
written, and useful apps even if they do use a compatibility layer.
But as you say, apple has been finicky in the past, not exactly being clear
on what is and isn't allowed.
> --
> Matthew Leverton
>
> -------------------------------------------------------------------------
> ----- Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
--
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx