I guess I should clarify my comment earlier that apple doesn't have to go through the app store approval process - I meant that apple doesn't have to obey the app store rules for their own software. They're free to add QC, java, flash, or anything else, regardless of whether it's interpreting code or not - they just choose not to. It's just the rest of us that aren't allowed. (I think that's pretty reasonable actually - if apple write something insecure, they have a good QA team to hopefully catch it before it leaves the building, and will patch it if not. If I write something insecure, apple can't do much about it other than shout at me and maybe stop sales of the app.)
Dick: XML isn't so bad really.. there's times when human readable really helps, it's actually a binary plist which isn't so inefficient, and it's only parsed/written when you open/save files, not all the time. The expense should be pretty negligible compared to running the composition for even a second... I'd really like to see QC on the iphone though. I'd write mini-games during lunch break again :D (I bet somebody at apple will see this and cancel the QC iphone project ;) But considering the technical hurdles, I think it's more reasonable to expect it on desktops only for now.. the original iphone/ipod touches won't support anything like CI for example, so there's already a big compatibility issue. An ipad version could be easier. But really I'm hoping for UIKit and it's friends to work their way onto the desktop, so we can have the awesomeness of multitouch with the power of a desktop. Oh, and you mentioned using the ipad as a multitouch device - check out the OSC app. It does that on the iiphone/ipod. An ipod version isn't hard to imagine, and could be an incredible controller! Chris On 1 Feb 2010, at 18:26, Dick Applebaum wrote: > > Here are some thoughts on QC & interpreted code... since I made the original > statement: > > "...and since it is interpreted, likely, there never will be!" > > > Apple SDK guidelines prohibit interpreted code. > > Apple has allowed interpreted code in some specific cases. > > Apple could allow QC, but I doubt it, > > Apple does not allow Java, one of the most efficient interpreted constructs-- > Java source is [pre or JIT] compiled to Java Byte code, an efficient pseudo > code, that is interpreted. > > AFAIK, Safari processes JavaScript in a similar fashion to mitigate the cost > of interpretation. > > QC, and many other apps, use quite a lot of XML constructs. These, by > definition, are verbose and inefficient to transmit, store, parse, > encode/decode. In most cases there is no need for human-readability and this > makes XML the wrong solution, IMO, and a very expensive one. What's the cost > of unnecessarily parsing and manipulating data, just so we can store it as > XML? > > As others have mentioned, QC has support for many hardware and OS > capabilities that are not available on the iPad. Would an iPad QC Subset be > viable? > > Apple could break all its own rules and allow whatever QC constructs that the > iPad and OS supports -- but does it make sense? > > Apple could provide a means of compiling QC for inclusion in an iPad app. > Some would argue that compilation would negate the QC advantages of > interaction and customization... but this could be addresses in several ways. > > Personally, I would like to see the iPad support QC. > > One possibility, is that a Mac supports QC as it presently does. And the > Mac, and QC use an attached (USB WiFi) iPad as an interactive MultiTouch I/O > device. > > Maybe future versions of iPads could have minimal bezels-- they could be > stacked to form a video wall (vertically) or a big-assed light table > (horizontally). QC Visualizer already supports this type of composite output. > > > Dick > > > On Feb 1, 2010, at 8:02 AM, George Toledo wrote: > >> I'm thinking Core Image is the biggie... >> >> -George Toledo >> >> On Mon, Feb 1, 2010 at 10:42 AM, Alex Drinkwater <[email protected]> >> wrote: >> >> Still, there's not a lot of power in an iphone or ipad, and QC is >> pretty demanding. I suspect it would be a lot of work to port, and >> might not be totally compatible with the desktop framework. The >> rewards of porting it might not be worthwhile for apple - that seems a >> more likely reason for it not happening to me. >> >> That seems to make sense to me. The thing you have to remember about QC is >> that it's not a standalone application, in the sense that it's built on top >> of a whole suite of technologies that are part of the MacOS, but aren't >> necessarily available on the iPhone, because of hardware limitations, >> mainly. So porting QC would involve also porting a load of other stuff, that >> might not be possible to make run on the iPhone with any reasonable level of >> performance. >> >> a|x >> >> >> >> Chris >> >> >> On 1 February 2010 15:00, Oscar Font <[email protected]> wrote: >> >> >> >> .... and since it is interpreted, likely, there will never be! >> >> Is that a straight affirmation? No chances to see QC in any apple devices in >> a future? Shame! >> There is a reflexion that we all made already. The future is all computers >> will be more and more handly portable, as iPad, iPhone. Right now there are, >> OS X, OS Chrome, Linux, iPhone OS X and Android. as an OS willing to be on >> any device. (forget windows). >> I honestly think that all should mix to one OS (opensource) for the best >> of/for all.... but this is decided on the market, not on what is good for >> the people. >> >> Some thoughts.. >> >> Oscar. >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Quartzcomposer-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/quartzcomposer-dev/psonice%40gmail.com >> >> This email sent to [email protected] >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Quartzcomposer-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/quartzcomposer-dev/the_voder%40yahoo.co.uk >> >> This email sent to [email protected] >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Quartzcomposer-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com >> >> This email sent to [email protected] >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Quartzcomposer-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/quartzcomposer-dev/dicklacara%40mac.com >> >> This email sent to [email protected] > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Quartzcomposer-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/quartzcomposer-dev/psonice%40gmail.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
