I agree on these names, they sound sensible and also clear (notice for all
not too familiar with gst: the GStreamer project itself refers to the main
gstreamer package/library as "core", so "corelibs" and "coreplugins" seem to
make sense).

2008/3/21, José Alburquerque <[EMAIL PROTECTED]>:
>
> Hi.  I'm noticing that there are some things in gstreamer which
> we haven't contemplated wrapping in gstreamermm yet and I was wondering
> how we might go about this:
>
> 1) In the gstreamer source directory, besides the gst directory (which
> we've mostly wrapped), there is a libs/gst directory with other
> directories such as base, check, controller, etc. which are not wrapped
> (the docs for these are at:
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-libs/html/
> ).
>
> 2) In the gstreamer source directory there's also a plugin directory
> with other directories (namely elements and indexers) which are also not
> wrapped (the docs for these are at:
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-plugins/html/
> ).
>
> 3) The gstreamer gst-plugins-base module has a directory named
> gst-libs/gst with items (including a few interfaces which I mentioned in
> post:
> http://mail.gnome.org/archives/gtkmm-list/2008-February/msg00201.html)
> that may also be beneficial to wrap (the docs for these are found at:
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-libs/html/
> ).
>
> Finally,
>
> 4) The gst-plugins-base module also has directories named gst and ext
> which contain gstreamer base plugins (the docs for these are at:
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/
> ).
>
> (I'm not sure that these should be wrapped, but I thought I should
> include them in this list for completeness.)
>
> What I'm trying to figure out is: would it be necessary to make
> subdirectories in gstreamermm/gstreamer or in gstreamermm (the main
> directory)?  I know that if the directories are created under the main
> gstreamermm directory these would probably represent namespaces and I'm
> not sure if I have to be precise in choosing good names and what these
> names should be.  I thought that names could be as follows: for 1)
> corelibs, for 2) coreplugins, for 3) baselibs and for 4) baseplugins.
> Are these names ok?  I'm thinking of adding these directories so that
> what's necessary can also be wrapped.  Thanks.
>
> --
> José Alburquerque
> [EMAIL PROTECTED]
>
>
> _______________________________________________
> gtkmm-list mailing list
> [email protected]
> http://mail.gnome.org/mailman/listinfo/gtkmm-list
>
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list

Reply via email to