Bug 9 - CoreImage's APIs are still NSDictionary based
Summary: CoreImage's APIs are still NSDictionary based
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 1.0
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-07-16 22:54 UTC by Miguel de Icaza [MSFT]
Modified: 2015-04-13 13:30 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Miguel de Icaza [MSFT] 2011-07-16 22:54:28 UTC
Many of the APIs in CoreImage could use a strongly typed set of configuration parameters instead of the NSDictionary setup that they have now.  From the notes:

+	Missing "properties" dictionary on CIImage
+	on IOS they have a CIFIlter outputImage property, this is a pain on OSX (valueForKey:kCIOOutputImageKey)
+	For OSX, we should wrap that shit into a decent property
+		For that matter, we should do properties for all of this crap dictionary APIs
+	Missing: filterWithName:keysAndValues: ...