User: jpmcc Date: 2010-07-02 17:01:06+0000 Modified: marketing/www/planet/atom.xml marketing/www/planet/index.html marketing/www/planet/opml.xml marketing/www/planet/rss10.xml marketing/www/planet/rss20.xml
Log: Planet run at Fri Jul 2 19:00:14 CEST 2010 File Changes: Directory: /marketing/www/planet/ ================================= File [changed]: atom.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/atom.xml?r1=1.3472&r2=1.3473 Delta lines: +25 -6 -------------------- --- atom.xml 2010-07-02 11:00:28+0000 1.3472 +++ atom.xml 2010-07-02 17:01:02+0000 1.3473 @@ -5,10 +5,29 @@ <link rel="self" href="http://marketing.openoffice.org/planet/atom.xml"/> <link href="http://marketing.openoffice.org/planet/"/> <id>http://marketing.openoffice.org/planet/atom.xml</id> - <updated>2010-07-02T11:00:27+00:00</updated> + <updated>2010-07-02T17:01:00+00:00</updated> <generator uri="http://www.planetplanet.org/";>Planet/2.0 +http://www.planetplanet.org</generator> <entry> + <title type="html">Better multimedia support for OpenOffice.org on Unix systems</title> + <link href="http://blogs.sun.com/GullFOSS/entry/better_multimedia_support_for_openoffice1"/> + <id>tag:google.com,2005:reader/item/22e710f239d9aab9</id> + <updated>2010-07-01T14:53:16+00:00</updated> + <content type="html"><p>Playing back audio and video content on Unix system was and is still a matter of choices. <br /><br />On the one hand, this is a good thing for the user. It offers a wide range of frameworks that best suit his/her needs. But on the other hand, this also brings a developer of a multi platform, general purpose Office productivity suite like OpenOffice.org (OOo) into the situation to make a choice. The choice needs to be made just to ensure that we don't have to provide a different backend for all multimedia frameworks that already exist. This just doesn't work for resource reasons. So, a framework needs to be chosen that meets the needs of a group of users as large as possible.<br /><br />A few years ago, we created a flexible multimedia solution for OOo that offers the chance to extend the set of supported external frameworks in an easy way and with only little development effort.<br /><br />Our first choice for a backend was the support for Sun's 'Java Media Framework' (JMF) at that time. A framework that is platform independent in general and that offers a good performance. Especially when using the - then platform dependent - performance extension, performance is on par with other frameworks.<br /><br />Time has shown that JMF seems to be a bit outdated today and that support for appropriate decoders is still not as good as expected. Enabling the support for JMF within OOo was also a not so easy task for the user, since the appropriate jmf.jar archive had to be added by hand by the user to the OOo classpath.<br /><br />So, we took a closer look at other frameworks and decided to create a completely new backend from scratch. This backend is based on the popular GStreamer framework. This is supported out of the box by many current Unix distributions, giving Ubuntu Linux and its derivatives as one of the most successful examples among available distributions.<br /><br />With the release 0.10 of GStreamer, this framework reached a very mature state and offers a great and 'complete' set of supported codecs. If âalready installed on the system, no more user interaction is needed within OOo to enable the new OOo GStreamer backend. It should just work, supporting all GStreamer decoders that have been installed on the system!<br /><br />From a technical point of view, the new GStreamer backend will be enabled by default on Unix systems, but can be disabled via configure with the --disable-gstreamer switch. In this case or in cases where no appropriate library can be found during runtime, a fallback to the old JMF implementation will happen.<br /><br />In order to build the GStreamer backend with the default configure values, care needs to be taken to adjust the build baseline to at least gstreamer-0.10.17 or newer (tested, previous micro releases &lt; 0.10.17 may also work), pkg-config requires the following build dependencies to gstreamer-0.10 and gstreamer-interfaces-0.10 resolved:<br /><br />pkg-config --cflags --libs gstreamer-0.10 gstreamer-interfaces-0.10<br /><br />-pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0<br />-I/usr/lib/glib-2.0/include -I/usr/include/libxml2Â -pthread<br />-lgstinterfaces-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -lxml2<br />-lgthread-2.0 -lrt -lglib-2.0<br /><br />If you are the maintainer of an OOo Tinderbox, please take care to update your Unix build machine to the new baseline.<br /><br />By choosing GStreamer as our favorite framework for an up to date multimedia backend, we hope to serve as much Linux and Solaris OpenOffice.org customers as best as possible. Creating this backend is also our answer to a lot of feedback we received from SOHO as well as enterprise customers in the past. Please have fun using this new multimedia solution and don't hesitate to give us feedback.</p> + <p> </p></content> + <author> + <name>kaiahrens</name> + <uri></uri> + </author> + <source> + <title type="html">jpmcc's shared items in Google Reader</title> + <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> + <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> + <updated>2010-07-02T17:00:36+00:00</updated> + </source> + </entry> + + <entry> <title type="html">New: OOo-DEV 3.x Developer Snapshot (build DEV300m84) available</title> <link href="http://blogs.sun.com/GullFOSS/entry/new_ooo_dev_3_x36"/> <id>tag:google.com,2005:reader/item/2e041e3b3b505fd1</id> @@ -27,7 +46,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2010-07-02T11:00:17+00:00</updated> + <updated>2010-07-02T17:00:36+00:00</updated> </source> </entry> @@ -193,7 +212,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2010-07-02T11:00:17+00:00</updated> + <updated>2010-07-02T17:00:36+00:00</updated> </source> </entry> @@ -335,7 +354,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2010-07-02T11:00:17+00:00</updated> + <updated>2010-07-02T17:00:36+00:00</updated> </source> </entry> @@ -437,7 +456,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2010-07-02T11:00:17+00:00</updated> + <updated>2010-07-02T17:00:36+00:00</updated> </source> </entry> @@ -459,7 +478,7 @@ <title type="html">jpmcc's shared items in Google Reader</title> <link rel="self" href="http://www.google.co.uk/reader/public/atom/user/06203502505240591501/state/com.google/broadcast"/> <id>tag:google.com,2005:reader/user/06203502505240591501/state/com.google/broadcast</id> - <updated>2010-07-02T11:00:17+00:00</updated> + <updated>2010-07-02T17:00:36+00:00</updated> </source> </entry> File [changed]: index.html Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/index.html?r1=1.3479&r2=1.3480 Delta lines: +16 -1 -------------------- --- index.html 2010-07-02 11:00:29+0000 1.3479 +++ index.html 2010-07-02 17:01:02+0000 1.3480 @@ -37,12 +37,27 @@ <a href="rss20.xml"><img src="rss2.gif" alt="Link to RSS 2 feed" /></a> </div> -<p><em>Bloggings on marketing topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: July 02, 2010 11:00 AM CET</em></p> +<p><em>Bloggings on marketing topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: July 02, 2010 05:01 PM CET</em></p> <h2>July 01, 2010</h2> <h3> <a href="" title="jpmcc's shared items in Google Reader"> GullFOSS</a> : +<a href="http://blogs.sun.com/GullFOSS/entry/better_multimedia_support_for_openoffice1";> +Better multimedia support for OpenOffice.org on Unix systems</a> +</h3> +<p> +<p>Playing back audio and video content on Unix system was and is still a matter of choices. <br /><br />On the one hand, this is a good thing for the user. It offers a wide range of frameworks that best suit his/her needs. But on the other hand, this also brings a developer of a multi platform, general purpose Office productivity suite like OpenOffice.org (OOo) into the situation to make a choice. The choice needs to be made just to ensure that we don't have to provide a different backend for all multimedia frameworks that already exist. This just doesn't work for resource reasons. So, a framework needs to be chosen that meets the needs of a group of users as large as possible.<br /><br />A few years ago, we created a flexible multimedia solution for OOo that offers the chance to extend the set of supported external frameworks in an easy way and with only little development effort.<br /><br />Our first choice for a backend was the support for Sun's 'Java Media Framework' (JMF) at that time. A framework that is platform independent in general and that offers a good performance. Especially when using the - then platform dependent - performance extension, performance is on par with other frameworks.<br /><br />Time has shown that JMF seems to be a bit outdated today and that support for appropriate decoders is still not as good as expected. Enabling the support for JMF within OOo was also a not so easy task for the user, since the appropriate jmf.jar archive had to be added by hand by the user to the OOo classpath.<br /><br />So, we took a closer look at other frameworks and decided to create a completely new backend from scratch. This backend is based on the popular GStreamer framework. This is supported out of the box by many current Unix distributions, giving Ubuntu Linux and its derivatives as one of the most successful examples among available distributions.<br /><br />With the release 0.10 of GStreamer, this framework reached a very mature state and offers a great and 'complete' set of supported codecs. If âalready installed on the system, no more user interaction is needed within OOo to enable the new OOo GStreamer backend. It should just work, supporting all GStreamer decoders that have been installed on the system!<br /><br />From a technical point of view, the new GStreamer backend will be enabled by default on Unix systems, but can be disabled via configure with the --disable-gstreamer switch. In this case or in cases where no appropriate library can be found during runtime, a fallback to the old JMF implementation will happen.<br /><br />In order to build the GStreamer backend with the default configure values, care needs to be taken to adjust the build baseline to at least gstreamer-0.10.17 or newer (tested, previous micro releases < 0.10.17 may also work), pkg-config requires the following build dependencies to gstreamer-0.10 and gstreamer-interfaces-0.10 resolved:<br /><br />pkg-config --cflags --libs gstreamer-0.10 gstreamer-interfaces-0.10<br /><br />-pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0<br />-I/usr/lib/glib-2.0/include -I/usr/include/libxml2Â -pthread<br />-lgstinterfaces-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -lxml2<br />-lgthread-2.0 -lrt -lglib-2.0<br /><br />If you are the maintainer of an OOo Tinderbox, please take care to update your Unix build machine to the new baseline.<br /><br />By choosing GStreamer as our favorite framework for an up to date multimedia backend, we hope to serve as much Linux and Solaris OpenOffice.org customers as best as possible. Creating this backend is also our answer to a lot of feedback we received from SOHO as well as enterprise customers in the past. Please have fun using this new multimedia solution and don't hesitate to give us feedback.</p> + <p> </p></p> +<p> +<em><a href="http://blogs.sun.com/GullFOSS/entry/better_multimedia_support_for_openoffice1";>by kaiahrens at July 01, 2010 02:53 PM CET</a></em> +</p> +<br /> +<hr /> +<br /> +<h3> +<a href="" title="jpmcc's shared items in Google Reader"> +GullFOSS</a> : <a href="http://blogs.sun.com/GullFOSS/entry/new_ooo_dev_3_x36";> New: OOo-DEV 3.x Developer Snapshot (build DEV300m84) available</a> </h3> File [changed]: opml.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/opml.xml?r1=1.3472&r2=1.3473 Delta lines: +1 -1 ------------------- --- opml.xml 2010-07-02 11:00:29+0000 1.3472 +++ opml.xml 2010-07-02 17:01:02+0000 1.3473 @@ -2,7 +2,7 @@ <opml version="1.1"> <head> <title>Marketing Planet</title> - <dateModified>Fri, 02 Jul 2010 11:00:27 +0000</dateModified> + <dateModified>Fri, 02 Jul 2010 17:01:00 +0000</dateModified> <ownerName>Marketing Project</ownerName> <ownerEmail>[email protected]</ownerEmail> </head> File [changed]: rss10.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/rss10.xml?r1=1.1015&r2=1.1016 Delta lines: +9 -0 ------------------- --- rss10.xml 2010-07-01 17:00:24+0000 1.1015 +++ rss10.xml 2010-07-02 17:01:02+0000 1.1016 @@ -13,6 +13,7 @@ <items> <rdf:Seq> + <rdf:li rdf:resource="tag:google.com,2005:reader/item/22e710f239d9aab9" /> <rdf:li rdf:resource="tag:google.com,2005:reader/item/2e041e3b3b505fd1" /> <rdf:li rdf:resource="tag:www.instapaper.com://6131c978b18ba8c0ccc92e654b9dbdf4" /> <rdf:li rdf:resource="tag:www.instapaper.com://9c58e6f248922d929cfb71a9e5959289" /> @@ -36,6 +37,14 @@ </items> </channel> +<item rdf:about="tag:google.com,2005:reader/item/22e710f239d9aab9"> + <title>GullFOSS: Better multimedia support for OpenOffice.org on Unix systems</title> + <link>http://blogs.sun.com/GullFOSS/entry/better_multimedia_support_for_openoffice1</link> + <content:encoded><p>Playing back audio and video content on Unix system was and is still a matter of choices. <br /><br />On the one hand, this is a good thing for the user. It offers a wide range of frameworks that best suit his/her needs. But on the other hand, this also brings a developer of a multi platform, general purpose Office productivity suite like OpenOffice.org (OOo) into the situation to make a choice. The choice needs to be made just to ensure that we don't have to provide a different backend for all multimedia frameworks that already exist. This just doesn't work for resource reasons. So, a framework needs to be chosen that meets the needs of a group of users as large as possible.<br /><br />A few years ago, we created a flexible multimedia solution for OOo that offers the chance to extend the set of supported external frameworks in an easy way and with only little development effort.<br /><br />Our first choice for a backend was the support for Sun's 'Java Media Framework' (JMF) at that time. A framework that is platform independent in general and that offers a good performance. Especially when using the - then platform dependent - performance extension, performance is on par with other frameworks.<br /><br />Time has shown that JMF seems to be a bit outdated today and that support for appropriate decoders is still not as good as expected. Enabling the support for JMF within OOo was also a not so easy task for the user, since the appropriate jmf.jar archive had to be added by hand by the user to the OOo classpath.<br /><br />So, we took a closer look at other frameworks and decided to create a completely new backend from scratch. This backend is based on the popular GStreamer framework. This is supported out of the box by many current Unix distributions, giving Ubuntu Linux and its derivatives as one of the most successful examples among available distributions.<br /><br />With the release 0.10 of GStreamer, this framework reached a very mature state and offers a great and 'complete' set of supported codecs. If âalready installed on the system, no more user interaction is needed within OOo to enable the new OOo GStreamer backend. It should just work, supporting all GStreamer decoders that have been installed on the system!<br /><br />From a technical point of view, the new GStreamer backend will be enabled by default on Unix systems, but can be disabled via configure with the --disable-gstreamer switch. In this case or in cases where no appropriate library can be found during runtime, a fallback to the old JMF implementation will happen.<br /><br />In order to build the GStreamer backend with the default configure values, care needs to be taken to adjust the build baseline to at least gstreamer-0.10.17 or newer (tested, previous micro releases &lt; 0.10.17 may also work), pkg-config requires the following build dependencies to gstreamer-0.10 and gstreamer-interfaces-0.10 resolved:<br /><br />pkg-config --cflags --libs gstreamer-0.10 gstreamer-interfaces-0.10<br /><br />-pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0<br />-I/usr/lib/glib-2.0/include -I/usr/include/libxml2Â -pthread<br />-lgstinterfaces-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -lxml2<br />-lgthread-2.0 -lrt -lglib-2.0<br /><br />If you are the maintainer of an OOo Tinderbox, please take care to update your Unix build machine to the new baseline.<br /><br />By choosing GStreamer as our favorite framework for an up to date multimedia backend, we hope to serve as much Linux and Solaris OpenOffice.org customers as best as possible. Creating this backend is also our answer to a lot of feedback we received from SOHO as well as enterprise customers in the past. Please have fun using this new multimedia solution and don't hesitate to give us feedback.</p> + <p> </p></content:encoded> + <dc:date>2010-07-01T14:53:16+00:00</dc:date> + <dc:creator>kaiahrens</dc:creator> +</item> <item rdf:about="tag:google.com,2005:reader/item/2e041e3b3b505fd1"> <title>GullFOSS: New: OOo-DEV 3.x Developer Snapshot (build DEV300m84) available</title> <link>http://blogs.sun.com/GullFOSS/entry/new_ooo_dev_3_x36</link> File [changed]: rss20.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/rss20.xml?r1=1.1015&r2=1.1016 Delta lines: +8 -0 ------------------- --- rss20.xml 2010-07-01 17:00:24+0000 1.1015 +++ rss20.xml 2010-07-02 17:01:03+0000 1.1016 @@ -8,6 +8,14 @@ <description>Marketing Planet - http://marketing.openoffice.org/planet/</description> <item> + <title>GullFOSS: Better multimedia support for OpenOffice.org on Unix systems</title> + <guid>tag:google.com,2005:reader/item/22e710f239d9aab9</guid> + <link>http://blogs.sun.com/GullFOSS/entry/better_multimedia_support_for_openoffice1</link> + <description><p>Playing back audio and video content on Unix system was and is still a matter of choices. <br /><br />On the one hand, this is a good thing for the user. It offers a wide range of frameworks that best suit his/her needs. But on the other hand, this also brings a developer of a multi platform, general purpose Office productivity suite like OpenOffice.org (OOo) into the situation to make a choice. The choice needs to be made just to ensure that we don't have to provide a different backend for all multimedia frameworks that already exist. This just doesn't work for resource reasons. So, a framework needs to be chosen that meets the needs of a group of users as large as possible.<br /><br />A few years ago, we created a flexible multimedia solution for OOo that offers the chance to extend the set of supported external frameworks in an easy way and with only little development effort.<br /><br />Our first choice for a backend was the support for Sun's 'Java Media Framework' (JMF) at that time. A framework that is platform independent in general and that offers a good performance. Especially when using the - then platform dependent - performance extension, performance is on par with other frameworks.<br /><br />Time has shown that JMF seems to be a bit outdated today and that support for appropriate decoders is still not as good as expected. Enabling the support for JMF within OOo was also a not so easy task for the user, since the appropriate jmf.jar archive had to be added by hand by the user to the OOo classpath.<br /><br />So, we took a closer look at other frameworks and decided to create a completely new backend from scratch. This backend is based on the popular GStreamer framework. This is supported out of the box by many current Unix distributions, giving Ubuntu Linux and its derivatives as one of the most successful examples among available distributions.<br /><br />With the release 0.10 of GStreamer, this framework reached a very mature state and offers a great and 'complete' set of supported codecs. If âalready installed on the system, no more user interaction is needed within OOo to enable the new OOo GStreamer backend. It should just work, supporting all GStreamer decoders that have been installed on the system!<br /><br />From a technical point of view, the new GStreamer backend will be enabled by default on Unix systems, but can be disabled via configure with the --disable-gstreamer switch. In this case or in cases where no appropriate library can be found during runtime, a fallback to the old JMF implementation will happen.<br /><br />In order to build the GStreamer backend with the default configure values, care needs to be taken to adjust the build baseline to at least gstreamer-0.10.17 or newer (tested, previous micro releases &lt; 0.10.17 may also work), pkg-config requires the following build dependencies to gstreamer-0.10 and gstreamer-interfaces-0.10 resolved:<br /><br />pkg-config --cflags --libs gstreamer-0.10 gstreamer-interfaces-0.10<br /><br />-pthread -I/usr/include/gstreamer-0.10 -I/usr/include/glib-2.0<br />-I/usr/lib/glib-2.0/include -I/usr/include/libxml2Â -pthread<br />-lgstinterfaces-0.10 -lgstreamer-0.10 -lgobject-2.0 -lgmodule-2.0 -lxml2<br />-lgthread-2.0 -lrt -lglib-2.0<br /><br />If you are the maintainer of an OOo Tinderbox, please take care to update your Unix build machine to the new baseline.<br /><br />By choosing GStreamer as our favorite framework for an up to date multimedia backend, we hope to serve as much Linux and Solaris OpenOffice.org customers as best as possible. Creating this backend is also our answer to a lot of feedback we received from SOHO as well as enterprise customers in the past. Please have fun using this new multimedia solution and don't hesitate to give us feedback.</p> + <p> </p></description> + <pubDate>Thu, 01 Jul 2010 14:53:16 +0000</pubDate> +</item> +<item> <title>GullFOSS: New: OOo-DEV 3.x Developer Snapshot (build DEV300m84) available</title> <guid>tag:google.com,2005:reader/item/2e041e3b3b505fd1</guid> <link>http://blogs.sun.com/GullFOSS/entry/new_ooo_dev_3_x36</link> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
