[gstreamer-bugs] [Bug 171735] add an interface to gst-core that allows multi child elements

[bugzilla-daemon at bugzilla.gnome.org]

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=171735
 GStreamer | gstreamer (core) | Ver: HEAD CVS





------- Additional Comments From Ronald Bultje  2005-04-11 04:08 -------
I want it documented at the place where it is committed. Pointers to URLs that
may not exist at a later date are not good enough. They may disappear. I want it
all in one place.

gst-launch is not a good reason to put it in core. gst-launch is a *test toy*,
nothing more. Anything serious will need test apps anyway. Same for gst-inspect.
gst-inspect doesn't link to gstinterfaces either, same reason. Is there a
*technical* reason why *core*, so libgstreamer-0.8.so, would need to link this
in? You can put a copy of gst-launch or gst-inspect in the package where we
commit this if you really need it, other interfaces have local test apps for
that as well. If gst-launch is the only reason, then I automatically conclude
that this does not necessarily need to go in core.
Again, just to be clear:
* gst-launch is not an all-featured demo tool for gstreamer.
* gst-launch is not for end users.
* gst-launch can not be a reason to put stuff in core.
* gst-launch merely has some basic features to make testing certain features for
certain developers easier that is all.
* we should never think that gst-launch is important in any way; it is not.
* s/gst-launch/gst{-inspect,etc}/: same.

As for layout: // etc. are not done by gst-indent, and it also does not take
care of newlines. I didn't commit on other layout stuff *because* gst-indent
does take care of the other concerns I had there. :).

-

I'm not against this patch, I'm trying to make it look better and make it fit in
with the basic requirements that I have for all patches. Other people (Wim,
Benjamin) will do the same. I do that to keep code quality high in gstreamer. My
requirements are not bad or outrageous at all, and have a really obvious goal.

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.