User: jpmcc Date: 2008-06-27 11:59:39+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 Jun 27 13:00:14 BST 2008 File Changes: Directory: /marketing/www/planet/ ================================= File [changed]: atom.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/atom.xml?r1=1.618&r2=1.619 Delta lines: +28 -28 --------------------- --- atom.xml 2008-06-27 05:59:34+0000 1.618 +++ atom.xml 2008-06-27 11:59:36+0000 1.619 @@ -5,10 +5,35 @@ <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>2008-06-27T06:00:22+00:00</updated> + <updated>2008-06-27T12:00:26+00:00</updated> <generator uri="http://www.planetplanet.org/";>Planet/2.0 +http://www.planetplanet.org</generator> <entry> + <title type="html">[EMAIL PROTECTED] (An ODF Wiki)</title> + <link href="http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki"/> + <id>tag:google.com,2005:reader/item/936fdc33b75b6d60</id> + <updated>2008-06-27T11:28:50+00:00</updated> + <content type="html"><p> Using <a href="http://www.openoffice.org" title="OpenOffice.org">OOo</a> in my daily work as well as the <a title="OpenOffice.org Wiki" href="http://wiki.services.openoffice.org/wiki/Main_Page">OOo Wiki</a>, I noticed an obvious disconnect between these two, especially taking into consideration, that we like to promote <a href="http://en.wikipedia.org/wiki/OpenDocument" title="Open Document Format">ODF</a> with OOo.<br /><br />OOo is used to create and to modify rich documents, which are mostly stored as data files on the local hard disk. Typical scenarios include attaching these documents/files to mails or uploading them somewhere. OOos strength is it's <a title="What You See Is What You Get" href="http://en.wikipedia.org/wiki/WYSIWYG">WYSIWYG</a> approach for changing rich documents, which includes spreadsheets, drawings, presentations and certainly texts. Though nowadays this does not seem to be sufficient anymore, &quot;sharing&quot; as by publication to a few or many individuals needs to be addressed as well. Not supporting this is OOos weakness ...<br /><br /><a title="Wiki Wiki" href="http://en.wikipedia.org/wiki/Wiki">Wikis</a>, as opposed to rich documents, are more lightweight and allow the direct editing of pages of a particular website by clicking an unspectacular &quot;edit&quot; link. Unfortunately one has to learn a dedicated &quot;programming language&quot;, which is not suitable for creating expressive tables or graphics but mostly for simple text only. The document handling is a Wikis strength, but the document editing and simpleness are it's weaknesses ...<br /><br />Thinking about that, I understood that these two approaches may be married to become an &quot;ODF Wiki&quot;, combing their strength - simple editing and simple publishing - while eliminating their weaknesses. </p> + <p>No sooner said than done, I installed an apache webserver, enabled WebDAV, did some (hacky) bash scripting, and got the following:</p> + <p>(YouTubes resolution is not the best, you can download the video as 1280x720 from <a title="ODF-AT-WWW--An-ODF-Wiki.mpg" href="http://mediacast.sun.com/users/Kay.Ramme/media/ODF-WWW-An-ODF-Wiki/details">mediacast</a>. It is showing OpenOffice.org used as a WYSIWYG editor for documents stored on +a webserver. Demoing Wiki like capabilities of adding, retrieving, +manipulating and publishing documents.)</p> + <p> +One may notice, that the &quot;full&quot; experience with an &quot;ODF Wiki&quot; may be achieved by donating a browse-mode to OOo. Nothingness the &quot;ODF Wiki&quot; does certainly support HTML access as well. The demoed scenario is only one of many use cases natively supporting ODF on the server and using OOo as a client. The Wiki approach may be applied to blogging as well, though this is only the tip of the iceberg. Just imagine what you could do, if you make the parts (such as paragraphs, styles etc.) or the content of the stored documents accessible, e.g. from the &quot;gallery&quot; (the thing I copied the image from), you could easily recombine it (either by inserting copies or references) to create other documents.<br /></p> + <p>If you like, or even if you don't like, what you see, please comment. I believe this approach has huge potential and would love to hear your thoughts, impressions etc. and would certainly like to see YOU helping with bringing this forward :-) <br /><br />Setting up the &quot;ODF Wiki&quot; with the scripts etc. is very simple. I am going to give the details in one of my next blogs :-)<br /><br />To be continued ...<br /><br /><br />Regards<br /><br />     Kay<br /><br /></p></content> + <author> + <name>KayRamme</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>2008-06-27T12:00:18+00:00</updated> + </source> + </entry> + + <entry> <title type="html">OpenOffice.org Newsletter in Danish</title> <link href="http://lodahl.blogspot.com/2008/06/openofficeorg-newsletter-in-danish.html"/> <id>tag:blogger.com,1999:blog-5198340507565233169.post-2243317390909120212</id> @@ -245,32 +270,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>2008-06-27T06:00:18+00:00</updated> - </source> - </entry> - - <entry> - <title type="html">[EMAIL PROTECTED] (An ODF Wiki)</title> - <link href="http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki"/> - <id>tag:google.com,2005:reader/item/936fdc33b75b6d60</id> - <updated>2008-06-19T15:34:38+00:00</updated> - <content type="html"><p> Using <a title="OpenOffice.org" href="http://www.openoffice.org">OOo</a> in my daily work as well as the <a href="http://wiki.services.openoffice.org/wiki/Main_Page" title="OpenOffice.org Wiki">OOo Wiki</a>, I noticed an obvious disconnect between these two, especially taking into consideration, that we like to promote <a title="Open Document Format" href="http://en.wikipedia.org/wiki/OpenDocument">ODF</a> with OOo.<br /><br />OOo is used to create and to modify rich documents, which are mostly stored as data files on the local hard disk. Typical scenarios include attaching these documents/files to mails or uploading them somewhere. OOos strength is it's <a href="http://en.wikipedia.org/wiki/WYSIWYG" title="What You See Is What You Get">WYSIWYG</a> approach for changing rich documents, which includes spreadsheets, drawings, presentations and certainly texts. Though nowadays this does not seem to be sufficient anymore, &quot;sharing&quot; as by publication to a few or many individuals needs to be addressed as well. Not supporting this is OOos weakness ...<br /><br /><a href="http://en.wikipedia.org/wiki/Wiki" title="Wiki Wiki">Wikis</a>, as opposed to rich documents, are more lightweight and allow the direct editing of pages of a particular website by clicking an unspectacular &quot;edit&quot; link. Unfortunately one has to learn a dedicated &quot;programming language&quot;, which is not suitable for creating expressive tables or graphics but mostly for simple text only. The document handling is a Wikis strength, but the document editing and simpleness are it's weaknesses ...<br /><br />Thinking about that, I understood that these two approaches may be married to become an &quot;ODF Wiki&quot;, combing their strength - simple editing and simple publishing - while eliminating their weaknesses. </p> - <p>No sooner said than done, I installed an apache webserver, enabled WebDAV, did some (hacky) bash scripting, and got the following:</p> - <p>(YouTubes resolution is not the best, you can download the video as 1280x720 from <a href="http://mediacast.sun.com/users/Kay.Ramme/media/ODF-WWW-An-ODF-Wiki/details" title="ODF-AT-WWW--An-ODF-Wiki.mpg">mediacast</a>. It is showing OpenOffice.org used as a WYSIWYG editor for documents stored on -a webserver. Demoing Wiki like capabilities of adding, retrieving, -manipulating and publishing documents.)</p> - <p> -One may notice, that the &quot;full&quot; experience with an &quot;ODF Wiki&quot; may be achieved by donating a browse-mode to OOo. Nothingness the &quot;ODF Wiki&quot; does certainly support HTML access as well. The demoed scenario is only one of many use cases natively supporting ODF on the server and using OOo as a client. The Wiki approach may be applied to blogging as well, though this is only the tip of the iceberg. Just imagine what you could do, if you make the parts (such as paragraphs, styles etc.) or the content of the stored documents accessible, e.g. from the &quot;gallery&quot; (the thing I copied the image from), you could easily recombine it (either by inserting copies or references) to create other documents.<br /></p> - <p>If you like, or even if you don't like, what you see, please comment. I believe this approach has huge potential and would love to hear your thoughts, impressions etc. and would certainly like to see YOU helping with bringing this forward :-) <br /><br />Setting up the &quot;ODF Wiki&quot; with the scripts etc. is very simple. I am going to give the details in one of my next blogs :-)<br /><br />To be continued ...<br /><br /><br />Regards<br /><br />     Kay<br /><br /></p></content> - <author> - <name>KayRamme</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>2008-06-27T06:00:18+00:00</updated> + <updated>2008-06-27T12:00:18+00:00</updated> </source> </entry> @@ -502,7 +502,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>2008-06-27T06:00:18+00:00</updated> + <updated>2008-06-27T12:00:18+00:00</updated> </source> </entry> File [changed]: index.html Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/index.html?r1=1.618&r2=1.619 Delta lines: +23 -22 --------------------- --- index.html 2008-06-27 05:59:34+0000 1.618 +++ index.html 2008-06-27 11:59:36+0000 1.619 @@ -34,8 +34,30 @@ <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: June 27, 2008 06:00 AM GMT</em></p> +<p><em>Bloggings on marketing topics by project members - see <a href="#disclaimer">disclaimer</a>.<br />Last updated: June 27, 2008 12:00 PM GMT</em></p> +<h2>June 27, 2008</h2> +<h3> +<a href="" title="jpmcc's shared items in Google Reader"> +GullFOSS</a> : +<a href="http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki";> [EMAIL PROTECTED] (An ODF Wiki)</a> +</h3> +<p> +<p> Using <a href="http://www.openoffice.org"; title="OpenOffice.org">OOo</a> in my daily work as well as the <a title="OpenOffice.org Wiki" href="http://wiki.services.openoffice.org/wiki/Main_Page";>OOo Wiki</a>, I noticed an obvious disconnect between these two, especially taking into consideration, that we like to promote <a href="http://en.wikipedia.org/wiki/OpenDocument"; title="Open Document Format">ODF</a> with OOo.<br /><br />OOo is used to create and to modify rich documents, which are mostly stored as data files on the local hard disk. Typical scenarios include attaching these documents/files to mails or uploading them somewhere. OOos strength is it's <a title="What You See Is What You Get" href="http://en.wikipedia.org/wiki/WYSIWYG";>WYSIWYG</a> approach for changing rich documents, which includes spreadsheets, drawings, presentations and certainly texts. Though nowadays this does not seem to be sufficient anymore, "sharing" as by publication to a few or many individuals needs to be addressed as well. Not supporting this is OOos weakness ...<br /><br /><a title="Wiki Wiki" href="http://en.wikipedia.org/wiki/Wiki";>Wikis</a>, as opposed to rich documents, are more lightweight and allow the direct editing of pages of a particular website by clicking an unspectacular "edit" link. Unfortunately one has to learn a dedicated "programming language", which is not suitable for creating expressive tables or graphics but mostly for simple text only. The document handling is a Wikis strength, but the document editing and simpleness are it's weaknesses ...<br /><br />Thinking about that, I understood that these two approaches may be married to become an "ODF Wiki", combing their strength - simple editing and simple publishing - while eliminating their weaknesses. </p> + <p>No sooner said than done, I installed an apache webserver, enabled WebDAV, did some (hacky) bash scripting, and got the following:</p> + <p>(YouTubes resolution is not the best, you can download the video as 1280x720 from <a title="ODF-AT-WWW--An-ODF-Wiki.mpg" href="http://mediacast.sun.com/users/Kay.Ramme/media/ODF-WWW-An-ODF-Wiki/details";>mediacast</a>. It is showing OpenOffice.org used as a WYSIWYG editor for documents stored on +a webserver. Demoing Wiki like capabilities of adding, retrieving, +manipulating and publishing documents.)</p> + <p> +One may notice, that the "full" experience with an "ODF Wiki" may be achieved by donating a browse-mode to OOo. Nothingness the "ODF Wiki" does certainly support HTML access as well. The demoed scenario is only one of many use cases natively supporting ODF on the server and using OOo as a client. The Wiki approach may be applied to blogging as well, though this is only the tip of the iceberg. Just imagine what you could do, if you make the parts (such as paragraphs, styles etc.) or the content of the stored documents accessible, e.g. from the "gallery" (the thing I copied the image from), you could easily recombine it (either by inserting copies or references) to create other documents.<br /></p> + <p>If you like, or even if you don't like, what you see, please comment. I believe this approach has huge potential and would love to hear your thoughts, impressions etc. and would certainly like to see YOU helping with bringing this forward :-) <br /><br />Setting up the "ODF Wiki" with the scripts etc. is very simple. I am going to give the details in one of my next blogs :-)<br /><br />To be continued ...<br /><br /><br />Regards<br /><br />     Kay<br /><br /></p></p> +<p> +<em><a href="http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki";>by KayRamme at June 27, 2008 11:28 AM GMT</a></em> +</p> +<br /> +<hr /> +<br /> <h2>June 26, 2008</h2> <h3> <a href="http://lodahl.blogspot.com/search/label/OpenOffice.org"; title="Lodahl's blog"> @@ -234,27 +256,6 @@ <br /> <h2>June 19, 2008</h2> <h3> -<a href="" title="jpmcc's shared items in Google Reader"> -GullFOSS</a> : -<a href="http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki";> [EMAIL PROTECTED] (An ODF Wiki)</a> -</h3> -<p> -<p> Using <a title="OpenOffice.org" href="http://www.openoffice.org";>OOo</a> in my daily work as well as the <a href="http://wiki.services.openoffice.org/wiki/Main_Page"; title="OpenOffice.org Wiki">OOo Wiki</a>, I noticed an obvious disconnect between these two, especially taking into consideration, that we like to promote <a title="Open Document Format" href="http://en.wikipedia.org/wiki/OpenDocument";>ODF</a> with OOo.<br /><br />OOo is used to create and to modify rich documents, which are mostly stored as data files on the local hard disk. Typical scenarios include attaching these documents/files to mails or uploading them somewhere. OOos strength is it's <a href="http://en.wikipedia.org/wiki/WYSIWYG"; title="What You See Is What You Get">WYSIWYG</a> approach for changing rich documents, which includes spreadsheets, drawings, presentations and certainly texts. Though nowadays this does not seem to be sufficient anymore, "sharing" as by publication to a few or many individuals needs to be addressed as well. Not supporting this is OOos weakness ...<br /><br /><a href="http://en.wikipedia.org/wiki/Wiki"; title="Wiki Wiki">Wikis</a>, as opposed to rich documents, are more lightweight and allow the direct editing of pages of a particular website by clicking an unspectacular "edit" link. Unfortunately one has to learn a dedicated "programming language", which is not suitable for creating expressive tables or graphics but mostly for simple text only. The document handling is a Wikis strength, but the document editing and simpleness are it's weaknesses ...<br /><br />Thinking about that, I understood that these two approaches may be married to become an "ODF Wiki", combing their strength - simple editing and simple publishing - while eliminating their weaknesses. </p> - <p>No sooner said than done, I installed an apache webserver, enabled WebDAV, did some (hacky) bash scripting, and got the following:</p> - <p>(YouTubes resolution is not the best, you can download the video as 1280x720 from <a href="http://mediacast.sun.com/users/Kay.Ramme/media/ODF-WWW-An-ODF-Wiki/details"; title="ODF-AT-WWW--An-ODF-Wiki.mpg">mediacast</a>. It is showing OpenOffice.org used as a WYSIWYG editor for documents stored on -a webserver. Demoing Wiki like capabilities of adding, retrieving, -manipulating and publishing documents.)</p> - <p> -One may notice, that the "full" experience with an "ODF Wiki" may be achieved by donating a browse-mode to OOo. Nothingness the "ODF Wiki" does certainly support HTML access as well. The demoed scenario is only one of many use cases natively supporting ODF on the server and using OOo as a client. The Wiki approach may be applied to blogging as well, though this is only the tip of the iceberg. Just imagine what you could do, if you make the parts (such as paragraphs, styles etc.) or the content of the stored documents accessible, e.g. from the "gallery" (the thing I copied the image from), you could easily recombine it (either by inserting copies or references) to create other documents.<br /></p> - <p>If you like, or even if you don't like, what you see, please comment. I believe this approach has huge potential and would love to hear your thoughts, impressions etc. and would certainly like to see YOU helping with bringing this forward :-) <br /><br />Setting up the "ODF Wiki" with the scripts etc. is very simple. I am going to give the details in one of my next blogs :-)<br /><br />To be continued ...<br /><br /><br />Regards<br /><br />     Kay<br /><br /></p></p> -<p> -<em><a href="http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki";>by KayRamme at June 19, 2008 03:34 PM GMT</a></em> -</p> -<br /> -<hr /> -<br /> -<h3> <a href="http://www.solidoffice.com"; title="SolidOffice » OpenOffice.org"> Benjamin Horst</a> : <a href="http://www.solidoffice.com/archives/825";> File [changed]: opml.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/opml.xml?r1=1.618&r2=1.619 Delta lines: +1 -1 ------------------- --- opml.xml 2008-06-27 05:59:35+0000 1.618 +++ opml.xml 2008-06-27 11:59:37+0000 1.619 @@ -2,7 +2,7 @@ <opml version="1.1"> <head> <title>Marketing Planet</title> - <dateModified>Fri, 27 Jun 2008 06:00:22 +0000</dateModified> + <dateModified>Fri, 27 Jun 2008 12:00:26 +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.328&r2=1.329 Delta lines: +15 -15 --------------------- --- rss10.xml 2008-06-26 23:59:37+0000 1.328 +++ rss10.xml 2008-06-27 11:59:37+0000 1.329 @@ -13,6 +13,7 @@ <items> <rdf:Seq> + <rdf:li rdf:resource="tag:google.com,2005:reader/item/936fdc33b75b6d60" /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-5198340507565233169.post-2243317390909120212" /> <rdf:li rdf:resource="http://www.solidoffice.com/?p=830"; /> <rdf:li rdf:resource="http://www.italovignoli.org/?p=468"; /> @@ -23,7 +24,6 @@ <rdf:li rdf:resource="http://blogs.sun.com/dancer/entry/microsoft_invites_to_odf_workshop"; /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-4887643299605448632.post-7496439869107002415" /> <rdf:li rdf:resource="tag:google.com,2005:reader/item/585931f06a08d325" /> - <rdf:li rdf:resource="tag:google.com,2005:reader/item/936fdc33b75b6d60" /> <rdf:li rdf:resource="http://www.solidoffice.com/?p=825"; /> <rdf:li rdf:resource="http://blogs.sun.com/dancer/entry/leaving_sun_and_going_to"; /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-5198340507565233169.post-97612882622239692" /> @@ -37,6 +37,20 @@ </items> </channel> +<item rdf:about="tag:google.com,2005:reader/item/936fdc33b75b6d60"> + <title>GullFOSS: [EMAIL PROTECTED] (An ODF Wiki)</title> + <link>http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki</link> + <content:encoded><p> Using <a href="http://www.openoffice.org" title="OpenOffice.org">OOo</a> in my daily work as well as the <a title="OpenOffice.org Wiki" href="http://wiki.services.openoffice.org/wiki/Main_Page">OOo Wiki</a>, I noticed an obvious disconnect between these two, especially taking into consideration, that we like to promote <a href="http://en.wikipedia.org/wiki/OpenDocument" title="Open Document Format">ODF</a> with OOo.<br /><br />OOo is used to create and to modify rich documents, which are mostly stored as data files on the local hard disk. Typical scenarios include attaching these documents/files to mails or uploading them somewhere. OOos strength is it's <a title="What You See Is What You Get" href="http://en.wikipedia.org/wiki/WYSIWYG">WYSIWYG</a> approach for changing rich documents, which includes spreadsheets, drawings, presentations and certainly texts. Though nowadays this does not seem to be sufficient anymore, &quot;sharing&quot; as by publication to a few or many individuals needs to be addressed as well. Not supporting this is OOos weakness ...<br /><br /><a title="Wiki Wiki" href="http://en.wikipedia.org/wiki/Wiki">Wikis</a>, as opposed to rich documents, are more lightweight and allow the direct editing of pages of a particular website by clicking an unspectacular &quot;edit&quot; link. Unfortunately one has to learn a dedicated &quot;programming language&quot;, which is not suitable for creating expressive tables or graphics but mostly for simple text only. The document handling is a Wikis strength, but the document editing and simpleness are it's weaknesses ...<br /><br />Thinking about that, I understood that these two approaches may be married to become an &quot;ODF Wiki&quot;, combing their strength - simple editing and simple publishing - while eliminating their weaknesses. </p> + <p>No sooner said than done, I installed an apache webserver, enabled WebDAV, did some (hacky) bash scripting, and got the following:</p> + <p>(YouTubes resolution is not the best, you can download the video as 1280x720 from <a title="ODF-AT-WWW--An-ODF-Wiki.mpg" href="http://mediacast.sun.com/users/Kay.Ramme/media/ODF-WWW-An-ODF-Wiki/details">mediacast</a>. It is showing OpenOffice.org used as a WYSIWYG editor for documents stored on +a webserver. Demoing Wiki like capabilities of adding, retrieving, +manipulating and publishing documents.)</p> + <p> +One may notice, that the &quot;full&quot; experience with an &quot;ODF Wiki&quot; may be achieved by donating a browse-mode to OOo. Nothingness the &quot;ODF Wiki&quot; does certainly support HTML access as well. The demoed scenario is only one of many use cases natively supporting ODF on the server and using OOo as a client. The Wiki approach may be applied to blogging as well, though this is only the tip of the iceberg. Just imagine what you could do, if you make the parts (such as paragraphs, styles etc.) or the content of the stored documents accessible, e.g. from the &quot;gallery&quot; (the thing I copied the image from), you could easily recombine it (either by inserting copies or references) to create other documents.<br /></p> + <p>If you like, or even if you don't like, what you see, please comment. I believe this approach has huge potential and would love to hear your thoughts, impressions etc. and would certainly like to see YOU helping with bringing this forward :-) <br /><br />Setting up the &quot;ODF Wiki&quot; with the scripts etc. is very simple. I am going to give the details in one of my next blogs :-)<br /><br />To be continued ...<br /><br /><br />Regards<br /><br />     Kay<br /><br /></p></content:encoded> + <dc:date>2008-06-27T11:28:50+00:00</dc:date> + <dc:creator>KayRamme</dc:creator> +</item> <item rdf:about="tag:blogger.com,1999:blog-5198340507565233169.post-2243317390909120212"> <title>Leif Lodahl: OpenOffice.org Newsletter in Danish</title> <link>http://lodahl.blogspot.com/2008/06/openofficeorg-newsletter-in-danish.html</link> @@ -152,20 +166,6 @@ <dc:date>2008-06-20T15:16:19+00:00</dc:date> <dc:creator>Joost Andrae</dc:creator> </item> -<item rdf:about="tag:google.com,2005:reader/item/936fdc33b75b6d60"> - <title>GullFOSS: [EMAIL PROTECTED] (An ODF Wiki)</title> - <link>http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki</link> - <content:encoded><p> Using <a title="OpenOffice.org" href="http://www.openoffice.org">OOo</a> in my daily work as well as the <a href="http://wiki.services.openoffice.org/wiki/Main_Page" title="OpenOffice.org Wiki">OOo Wiki</a>, I noticed an obvious disconnect between these two, especially taking into consideration, that we like to promote <a title="Open Document Format" href="http://en.wikipedia.org/wiki/OpenDocument">ODF</a> with OOo.<br /><br />OOo is used to create and to modify rich documents, which are mostly stored as data files on the local hard disk. Typical scenarios include attaching these documents/files to mails or uploading them somewhere. OOos strength is it's <a href="http://en.wikipedia.org/wiki/WYSIWYG" title="What You See Is What You Get">WYSIWYG</a> approach for changing rich documents, which includes spreadsheets, drawings, presentations and certainly texts. Though nowadays this does not seem to be sufficient anymore, &quot;sharing&quot; as by publication to a few or many individuals needs to be addressed as well. Not supporting this is OOos weakness ...<br /><br /><a href="http://en.wikipedia.org/wiki/Wiki" title="Wiki Wiki">Wikis</a>, as opposed to rich documents, are more lightweight and allow the direct editing of pages of a particular website by clicking an unspectacular &quot;edit&quot; link. Unfortunately one has to learn a dedicated &quot;programming language&quot;, which is not suitable for creating expressive tables or graphics but mostly for simple text only. The document handling is a Wikis strength, but the document editing and simpleness are it's weaknesses ...<br /><br />Thinking about that, I understood that these two approaches may be married to become an &quot;ODF Wiki&quot;, combing their strength - simple editing and simple publishing - while eliminating their weaknesses. </p> - <p>No sooner said than done, I installed an apache webserver, enabled WebDAV, did some (hacky) bash scripting, and got the following:</p> - <p>(YouTubes resolution is not the best, you can download the video as 1280x720 from <a href="http://mediacast.sun.com/users/Kay.Ramme/media/ODF-WWW-An-ODF-Wiki/details" title="ODF-AT-WWW--An-ODF-Wiki.mpg">mediacast</a>. It is showing OpenOffice.org used as a WYSIWYG editor for documents stored on -a webserver. Demoing Wiki like capabilities of adding, retrieving, -manipulating and publishing documents.)</p> - <p> -One may notice, that the &quot;full&quot; experience with an &quot;ODF Wiki&quot; may be achieved by donating a browse-mode to OOo. Nothingness the &quot;ODF Wiki&quot; does certainly support HTML access as well. The demoed scenario is only one of many use cases natively supporting ODF on the server and using OOo as a client. The Wiki approach may be applied to blogging as well, though this is only the tip of the iceberg. Just imagine what you could do, if you make the parts (such as paragraphs, styles etc.) or the content of the stored documents accessible, e.g. from the &quot;gallery&quot; (the thing I copied the image from), you could easily recombine it (either by inserting copies or references) to create other documents.<br /></p> - <p>If you like, or even if you don't like, what you see, please comment. I believe this approach has huge potential and would love to hear your thoughts, impressions etc. and would certainly like to see YOU helping with bringing this forward :-) <br /><br />Setting up the &quot;ODF Wiki&quot; with the scripts etc. is very simple. I am going to give the details in one of my next blogs :-)<br /><br />To be continued ...<br /><br /><br />Regards<br /><br />     Kay<br /><br /></p></content:encoded> - <dc:date>2008-06-19T15:34:38+00:00</dc:date> - <dc:creator>KayRamme</dc:creator> -</item> <item rdf:about="http://www.solidoffice.com/?p=825";> <title>Benjamin Horst: Mail Merge in OpenOffice.org</title> <link>http://www.solidoffice.com/archives/825</link> File [changed]: rss20.xml Url: http://marketing.openoffice.org/source/browse/marketing/www/planet/rss20.xml?r1=1.328&r2=1.329 Delta lines: +14 -14 --------------------- --- rss20.xml 2008-06-26 23:59:37+0000 1.328 +++ rss20.xml 2008-06-27 11:59:37+0000 1.329 @@ -8,6 +8,20 @@ <description>Marketing Planet - http://marketing.openoffice.org/planet/</description> <item> + <title>GullFOSS: [EMAIL PROTECTED] (An ODF Wiki)</title> + <guid>tag:google.com,2005:reader/item/936fdc33b75b6d60</guid> + <link>http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki</link> + <description><p> Using <a href="http://www.openoffice.org" title="OpenOffice.org">OOo</a> in my daily work as well as the <a title="OpenOffice.org Wiki" href="http://wiki.services.openoffice.org/wiki/Main_Page">OOo Wiki</a>, I noticed an obvious disconnect between these two, especially taking into consideration, that we like to promote <a href="http://en.wikipedia.org/wiki/OpenDocument" title="Open Document Format">ODF</a> with OOo.<br /><br />OOo is used to create and to modify rich documents, which are mostly stored as data files on the local hard disk. Typical scenarios include attaching these documents/files to mails or uploading them somewhere. OOos strength is it's <a title="What You See Is What You Get" href="http://en.wikipedia.org/wiki/WYSIWYG">WYSIWYG</a> approach for changing rich documents, which includes spreadsheets, drawings, presentations and certainly texts. Though nowadays this does not seem to be sufficient anymore, &quot;sharing&quot; as by publication to a few or many individuals needs to be addressed as well. Not supporting this is OOos weakness ...<br /><br /><a title="Wiki Wiki" href="http://en.wikipedia.org/wiki/Wiki">Wikis</a>, as opposed to rich documents, are more lightweight and allow the direct editing of pages of a particular website by clicking an unspectacular &quot;edit&quot; link. Unfortunately one has to learn a dedicated &quot;programming language&quot;, which is not suitable for creating expressive tables or graphics but mostly for simple text only. The document handling is a Wikis strength, but the document editing and simpleness are it's weaknesses ...<br /><br />Thinking about that, I understood that these two approaches may be married to become an &quot;ODF Wiki&quot;, combing their strength - simple editing and simple publishing - while eliminating their weaknesses. </p> + <p>No sooner said than done, I installed an apache webserver, enabled WebDAV, did some (hacky) bash scripting, and got the following:</p> + <p>(YouTubes resolution is not the best, you can download the video as 1280x720 from <a title="ODF-AT-WWW--An-ODF-Wiki.mpg" href="http://mediacast.sun.com/users/Kay.Ramme/media/ODF-WWW-An-ODF-Wiki/details">mediacast</a>. It is showing OpenOffice.org used as a WYSIWYG editor for documents stored on +a webserver. Demoing Wiki like capabilities of adding, retrieving, +manipulating and publishing documents.)</p> + <p> +One may notice, that the &quot;full&quot; experience with an &quot;ODF Wiki&quot; may be achieved by donating a browse-mode to OOo. Nothingness the &quot;ODF Wiki&quot; does certainly support HTML access as well. The demoed scenario is only one of many use cases natively supporting ODF on the server and using OOo as a client. The Wiki approach may be applied to blogging as well, though this is only the tip of the iceberg. Just imagine what you could do, if you make the parts (such as paragraphs, styles etc.) or the content of the stored documents accessible, e.g. from the &quot;gallery&quot; (the thing I copied the image from), you could easily recombine it (either by inserting copies or references) to create other documents.<br /></p> + <p>If you like, or even if you don't like, what you see, please comment. I believe this approach has huge potential and would love to hear your thoughts, impressions etc. and would certainly like to see YOU helping with bringing this forward :-) <br /><br />Setting up the &quot;ODF Wiki&quot; with the scripts etc. is very simple. I am going to give the details in one of my next blogs :-)<br /><br />To be continued ...<br /><br /><br />Regards<br /><br />     Kay<br /><br /></p></description> + <pubDate>Fri, 27 Jun 2008 11:28:50 +0000</pubDate> +</item> +<item> <title>Leif Lodahl: OpenOffice.org Newsletter in Danish</title> <guid>tag:blogger.com,1999:blog-5198340507565233169.post-2243317390909120212</guid> <link>http://lodahl.blogspot.com/2008/06/openofficeorg-newsletter-in-danish.html</link> @@ -132,20 +146,6 @@ <pubDate>Fri, 20 Jun 2008 15:16:19 +0000</pubDate> </item> <item> - <title>GullFOSS: [EMAIL PROTECTED] (An ODF Wiki)</title> - <guid>tag:google.com,2005:reader/item/936fdc33b75b6d60</guid> - <link>http://blogs.sun.com/GullFOSS/entry/odf_www_an_odf_wiki</link> - <description><p> Using <a title="OpenOffice.org" href="http://www.openoffice.org">OOo</a> in my daily work as well as the <a href="http://wiki.services.openoffice.org/wiki/Main_Page" title="OpenOffice.org Wiki">OOo Wiki</a>, I noticed an obvious disconnect between these two, especially taking into consideration, that we like to promote <a title="Open Document Format" href="http://en.wikipedia.org/wiki/OpenDocument">ODF</a> with OOo.<br /><br />OOo is used to create and to modify rich documents, which are mostly stored as data files on the local hard disk. Typical scenarios include attaching these documents/files to mails or uploading them somewhere. OOos strength is it's <a href="http://en.wikipedia.org/wiki/WYSIWYG" title="What You See Is What You Get">WYSIWYG</a> approach for changing rich documents, which includes spreadsheets, drawings, presentations and certainly texts. Though nowadays this does not seem to be sufficient anymore, &quot;sharing&quot; as by publication to a few or many individuals needs to be addressed as well. Not supporting this is OOos weakness ...<br /><br /><a href="http://en.wikipedia.org/wiki/Wiki" title="Wiki Wiki">Wikis</a>, as opposed to rich documents, are more lightweight and allow the direct editing of pages of a particular website by clicking an unspectacular &quot;edit&quot; link. Unfortunately one has to learn a dedicated &quot;programming language&quot;, which is not suitable for creating expressive tables or graphics but mostly for simple text only. The document handling is a Wikis strength, but the document editing and simpleness are it's weaknesses ...<br /><br />Thinking about that, I understood that these two approaches may be married to become an &quot;ODF Wiki&quot;, combing their strength - simple editing and simple publishing - while eliminating their weaknesses. </p> - <p>No sooner said than done, I installed an apache webserver, enabled WebDAV, did some (hacky) bash scripting, and got the following:</p> - <p>(YouTubes resolution is not the best, you can download the video as 1280x720 from <a href="http://mediacast.sun.com/users/Kay.Ramme/media/ODF-WWW-An-ODF-Wiki/details" title="ODF-AT-WWW--An-ODF-Wiki.mpg">mediacast</a>. It is showing OpenOffice.org used as a WYSIWYG editor for documents stored on -a webserver. Demoing Wiki like capabilities of adding, retrieving, -manipulating and publishing documents.)</p> - <p> -One may notice, that the &quot;full&quot; experience with an &quot;ODF Wiki&quot; may be achieved by donating a browse-mode to OOo. Nothingness the &quot;ODF Wiki&quot; does certainly support HTML access as well. The demoed scenario is only one of many use cases natively supporting ODF on the server and using OOo as a client. The Wiki approach may be applied to blogging as well, though this is only the tip of the iceberg. Just imagine what you could do, if you make the parts (such as paragraphs, styles etc.) or the content of the stored documents accessible, e.g. from the &quot;gallery&quot; (the thing I copied the image from), you could easily recombine it (either by inserting copies or references) to create other documents.<br /></p> - <p>If you like, or even if you don't like, what you see, please comment. I believe this approach has huge potential and would love to hear your thoughts, impressions etc. and would certainly like to see YOU helping with bringing this forward :-) <br /><br />Setting up the &quot;ODF Wiki&quot; with the scripts etc. is very simple. I am going to give the details in one of my next blogs :-)<br /><br />To be continued ...<br /><br /><br />Regards<br /><br />     Kay<br /><br /></p></description> - <pubDate>Thu, 19 Jun 2008 15:34:38 +0000</pubDate> -</item> -<item> <title>Benjamin Horst: Mail Merge in OpenOffice.org</title> <guid>http://www.solidoffice.com/?p=825</guid> <link>http://www.solidoffice.com/archives/825</link> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
