Re: iphone

> We'd need an effort from the iSCKit team as well, or someone(s) committed
> to work on it with their blessing, and presumably starting with that
> effort.  They should update their repo to the current version of SC with
> a common sense effort to draw clear lines of distinction between platform
> specific code and shared code.

I agree. Until this is done I don't see much of a path for integration. But
3.4 is quite old.

> Re: Significance of SuperCollider on mobile.  Making SC available as an
> option for sound generation on mobile seems to have a natural and
> undeniable upside.  SC could influence industry standards.  Not to
> mention the technology push and legitimacy SC will get from the gaming
> community.

I'm sorry, maybe I'm just dense but I don't see how these things are
related at all.

> Big question is... if someone magically delivered a pull request tomorrow
> with a full integration that sustained iSCKit without significant
> side-effects to the current version of SC... would this PR be accepted
> by sd-dev community?  That is the first step.

I don't know. My feeling is, yes, but *only if* that PR is made with some
sort of understand that the original contributor will take part in its
maintenance. Realistically speaking there are only so many things we as a
project can work on. If it's a one-time contribution that is abandoned or
unsupported by the original author, my fear is that it's very likely it
will languish and become a burden to active development in other areas. For
example, while reworking one of my older PRs I spent a good 5 hours or so
making sure old SC_IPHONE code was preserved.

So, I guess the best first step is to reach out to the author of iSCKit and
see how they feel about this. I'd be happy to do that.

Regards,

Brian