[gst-devel] Notes on the 0.9 API

[Stefan Kost]

Hi Torsten,

  Torsten Schoenfeld wrote:
> On Mon, 2005-11-21 at 08:58 +0100, Stefan Kost wrote:
> 
> 
>>>* gstchildproxy.h doesn't get included by default.
> 
> 
> What about this issue?
Fixed, will commit in minute.
> 
> 
>>>* gst_child_proxy_[sg]et is badly named.  Since GstChildProxy is an
>>>interface, these methods map to $thing->[sg]et in OO-ish language
>>>bindings -- thus colliding with g_object_[sg]et.  Something like that is
>>>okay if the interface provides the basic functionality of the object
>>>implementing it.  Example: gtk_tree_model_get also maps to $thing->get,
>>>but if you call the "get" method on a tree model, it's pretty likely
>>>that you actually want gtk_tree_model_get instead of g_object_get.
>>>Fetching data is more common than fetching object properties.
>>
>>As I see it, properties *are* the data an object manages. For C we decided to 
>>not overly extend the parameter names.
> 
> 
> Well, but would you expect to get gst_child_proxy_get if you called the
> "get" method on a GstBin or a GstPipeline?  That's what happens if
> language bindings wrap the interface as-is.
I wouldn't mind.
gst_child_proxy_get(object,"name",&name,NULL);
would do the same as
g_object_get(object,"name",&name,NULL);
The difference is that
gst_child_proxy_get(object,"child0:name",&name,NULL);
would get the name of the child named "child0".

<snip>

Stefan