[gst-devel] Module list

[Benoît de Boursetty]

Ah yes, thanks.

If I summarize the email thread:

 - There is a need for this functionality
 - It might be opportune to have different pages for different target
audiences (developers vs. users), or a page with ability to "drill
down" into details so as not to confuse the basic user
 - Some info can already be pulled from the plug-ins, some has to be
provided anew

Here is a list of information to gather, from the original post
amended to reflect further posts in the thread. Information preceded
by a # can be automatically generated from the plug-ins.

#* Element/plug-in name.
#* Short, one-line description.
* Longer, more meaningful description.
#* Pads:
 	#- Listing of all pads.
 	#- Capabilities.
 	- Description.
* External library dependencies:
 	- Name of library.
 	- Link to "home page", not just where the source tarball can
 	   be downloaded.
 	- Version numbers that are compatible (where known).
#* Platform availability (all platforms, Mac OS X only, anything but
 Windows, etc.)
#* CVS module/branch/revision number (or whatever) that indicates the
 version of the plug-in that is being referred to.

I would like to my own suggestions: adding author (comprising name,
email, homepage, etc.) and commercial status.

I also suggest establishing a hierarchy of "packages" vs. "plug-ins",
because some references (e.g. revision number, author, platform
availability, or some library dependencies) are probably going to be
at the "package" level, i.e. identical for each plug-in. Then the
plug-ins would be able to override package defaults for these
properties.

Does anyone have time to try out something like this?

Benoît.

On 5/13/05, Darren Blaser <darrenb at extendedsystems.com> wrote:
> This request goes hand in hand with the "Revive the element status
> tables" item on the gstreamer todo list. See
> http://gstreamer.freedesktop.org/tasks/gstreamer.html#elementlist
> 
> This was recently discussed on the mailing list and Jeff was planning to
> take a crack at it... Does anyone have any kind of status update for
> this task?
> 
> You can see the previous discussion in the mailing list archive from Feb
> 11-16 of this year under the topic:
> What I want out of a "Status Table"
> http://sourceforge.net/mailarchive/message.php?msg_id=10837999
> 
>