[Gstreamer-bugs] [Bug 133541] Changed - int2float and int2floatnew conflict should be resolved

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=133541

Changed by in7y118 at public.uni-hamburg.de.

--- shadow/133541	Sat Feb  7 06:25:51 2004
+++ shadow/133541.tmp.22877	Tue Feb 10 09:47:22 2004
@@ -32,6 +32,26 @@
 widgets change between releases.
 
 It's not because the element concept is more vague as an interface,
 that it's not part of that interface :) I honestly don't see what
 applications could currently do to figure out what name it should try
 to factory_make on if we change names on plugins between releases.
+
+------- Additional Comments From in7y118 at public.uni-hamburg.de  2004-02-10 09:47 -------
+The general idea is that you look for an element in the list that 
+does your job and then select the one that best suits what you want 
+to do.
+
+Hardcoding element names totally stomps extensibility and to me is 
+only a crude hack to get what you want.
+
+If for example one day oilcolorspace is the best colorspace element, 
+gst-player won't use that and insist on using ffmpeg. Same for 
+volume (an element that implements the volume interface), 
+colorbalance (... colorbalance interface), audioconvert (a converter 
+that takes/outputs audio/x-raw-int) or filesrc/gnomevfssrc (... URI 
+interface). The gconf keys already do this, too.
+
+There is really no need to use element names. It's just simpler most 
+of the time.
+
+