> Since image processing is largely CPU intensive (and normally done using > SIMD - which, sadly, MonoTouch does not support (maybe a feature for a > future version?)), this might be a task best suited for a native library or > something. Then again, maybe Apple's CoreImage does what you need, in which > case MonoTouch's binding should already have what you need as well (and > there should be no significant overhead).
this is the big thing. If you are calling into native iOS CocoaTouch functions, there might be a very minor overhead calling the method, but after that, it's 1:1 with objc, 'cos it's the _same code_ which is being run. Now, if you are writing your own image manipulation lib's, then..... dont. Unless you really need to. And even then: dont. :) CocoaTouch is SO SO SO rich - and even more so with the Mono framework there too - chances are you can do pretty much everything with what you have there already, with no perf hit _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
