GNOME.org
 

Gtkmm-forge Digest, Vol 31, Issue 13

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-owner lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 565454] Problematic packaging of 0.9.8
      (gnomemm (bugzilla.gnome.org))
   2. [Bug 565487] Glib::spawn_async* functions don't	work with
      exceptions disabled (glibmm (bugzilla.gnome.org))
   3. [Bug 565487] Glib::spawn_async* functions don't	work with
      exceptions disabled (glibmm (bugzilla.gnome.org))
   4. [Bug 565454] Problematic packaging of 0.9.8
      (gnomemm (bugzilla.gnome.org))
   5. [Bug 565454] Problematic packaging of 0.9.8
      (gnomemm (bugzilla.gnome.org))
   6. [Bug 565454] Problematic packaging of 0.9.8
      (gnomemm (bugzilla.gnome.org))


----------------------------------------------------------------------

Message: 1
Date: Wed, 24 Dec 2008 21:20:52 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 565454] Problematic packaging of 0.9.8
To: gtkmm-forge lists sourceforge net
Message-ID: <20081224212052 EFED923F51A label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=565454

  gnomemm | gstreamermm | Ver: unspecified




------- Comment #7 from Jos? Alburquerque  2008-12-24 21:20 UTC -------
For a reference of what I'm describing, look at the Gst::FakeSink generated .hg
and .ccg files.  You'll see the generated structures and _get_type() functions
in the .ccg file.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=565454.



------------------------------

Message: 2
Date: Wed, 24 Dec 2008 22:11:25 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 565487] Glib::spawn_async* functions
	don't	work with exceptions disabled
To: gtkmm-forge lists sourceforge net
Message-ID: <20081224221125 AEF8623F51B label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=565487

  glibmm | general | Ver: unspecified




------- Comment #1 from Murray Cumming  2008-12-24 22:11 UTC -------
Created an attachment (id=125284)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=125284&action=view)
spawn_no_exceptions.patch

Yes. I committed this patch to fix it. It's what we do for other
functions/methods that throw exceptions.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=565487.



------------------------------

Message: 3
Date: Wed, 24 Dec 2008 22:11:43 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 565487] Glib::spawn_async* functions
	don't	work with exceptions disabled
To: gtkmm-forge lists sourceforge net
Message-ID: <20081224221143 3F3F923F519 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=565487

  glibmm | general | Ver: unspecified

Murray Cumming changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murrayc murrayc com
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=565487.



------------------------------

Message: 4
Date: Thu, 25 Dec 2008 16:34:58 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 565454] Problematic packaging of 0.9.8
To: gtkmm-forge lists sourceforge net
Message-ID: <20081225163458 8DBD923EEF9 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=565454

  gnomemm | gstreamermm | Ver: unspecified




------- Comment #8 from Jos? Alburquerque  2008-12-25 16:34 UTC -------
I've been thinking and there may be a couple of solutions:

1) Have the generated files part of the tarball as is done in other *mm
projects like gtkmm but then generate the wrap_init() functions based on which
plug-ins are present on the build system (This still would require perl
processing, I think).

2) Same as above, but not include the plug-ins in the wrap_init()s.  After all,
the underlying C type of the plug-ins are never available because they're not
public so wrapping a C object using Glib::wrap() would be impossible except for
the fact that because of the "typedef strct _GstCPluginType GstCPluginType" in
the .h file generated by gmmproc, it is available in C++ (see the
test-plugin-gen test in tests/).  In the C API plug-ins are designed to be
referenced only by name with functions such as the ones mentioned before in the
footnotes of the previous comments and others in GstPlugin[1] and
GstRegistry[2].  If plug-ins are not included in the wrap_inits this would fix
this bug altogether.

[1]
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/GstPlugin.html
[2]
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/GstRegistry.html

There's just one observation with 2) above:  The user in C++ may want to, for
some odd reason, create an element of a plug-in type using the C API and then
wrap it with Glib::wrap() in C++ as in the following:

GstElement* gst_element = gst_element_factory_make("pluginName", NULL);
Glib::RefPtr<Gst::PluginName> element = Glib::wrap( (GstPluginName*) element);

But I think this would not be possible with 2).  Also, with the above
statements, notice the relation between "pluginName" and the C++ type (without
the namespace) "PluginName".  It's designed to always be so in gstreamermm as
it also generally is with the C type though some strange things may occur with
the C type such as it changing altogether between releases (see relevant
comment[3] in bug #562810).

[3] http://bugzilla.gnome.org/show_bug.cgi?id=562810#c5


On a final note, I thought about the comment that gstreamer is very varying,
and I understand.  Here are my thoughts:  I'm completely open to anything such
as: 1) Discontinuing development, 2) Passing on development if you all think
that someone may better handle the task, 3) Including others that may help to
advance development, 4) Having me develop on my own as long as I can and it is
useful to others or even 5) passing development over to GStreamer or something
like that (though I don't know whether they would want that).

I want to make it clear that I don't mind that these choices are made (even if
I'm not included) so that it is not difficult to make them.  I really have no
misgivings about things like this, so they can be decided however best it is
convenient.  In this way, I wont complicate a decision to include someone else
in development or change things around, for example.

The reason I began developing gstreamermm is that I thought I would need it for
a project that I started, and I think it is nearly at a point where it may be
used successfully in this project so this is why I'm open to these decisions;
because it is nearly usable.  Also, who knows if another API may be used just
as well.  Again, I'm open.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=565454.



------------------------------

Message: 5
Date: Sat, 27 Dec 2008 06:49:22 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 565454] Problematic packaging of 0.9.8
To: gtkmm-forge lists sourceforge net
Message-ID: <20081227064922 0858A23F51C label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=565454

  gnomemm | gstreamermm | Ver: unspecified




------- Comment #9 from Deng Xiyue  2008-12-27 06:49 UTC -------
Sorry for the late response. I have no strong opinion for the packaging, and
absolutely no intent to question the development of gstreamermm. As the current
approach of source generation, I guess just put m4 and XML::Parser to the build
requirement should be enough. (And XML::Parser is required when generating ccg
-> cc or hg -> h as it seems.)


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=565454.



------------------------------

Message: 6
Date: Sat, 27 Dec 2008 11:38:34 +0000 (UTC)
From: "gnomemm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 565454] Problematic packaging of 0.9.8
To: gtkmm-forge lists sourceforge net
Message-ID: <20081227113834 B69BB23F51B label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=565454

  gnomemm | gstreamermm | Ver: unspecified




------- Comment #10 from Murray Cumming  2008-12-27 11:38 UTC -------
> 1) Have the generated files part of the tarball as is done in other *mm
> projects like gtkmm but then generate the wrap_init() functions based on which
> plug-ins are present on the build system (This still would require perl
> processing, I think).

There should be ifdefs in the wrap_init.cc just as there are for deprecated or
optional API in gtkmm. That would require some changes to the wrap_init.pl
script, or a local copy of it, I guess.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=565454.



------------------------------

------------------------------------------------------------------------------


------------------------------

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest, Vol 31, Issue 13
*******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]