<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>NamForum.com - OpenOffice</title>
    <link>http://www.namforum.com/blog/</link>
    <description>A forum for Namibians</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.0-beta2 - http://www.s9y.org/</generator>
    <pubDate>Mon, 10 Jul 2006 06:58:57 GMT</pubDate>

    <image>
        <url>http://www.namforum.com/blog/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: NamForum.com - OpenOffice - A forum for Namibians</title>
        <link>http://www.namforum.com/blog/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>Use OpenOffice as a plugin in Eclipse</title>
    <link>http://www.namforum.com/blog/index.php?/archives/49-Use-OpenOffice-as-a-plugin-in-Eclipse.html</link>
            <category>OpenOffice</category>
    
    <comments>http://www.namforum.com/blog/index.php?/archives/49-Use-OpenOffice-as-a-plugin-in-Eclipse.html#comments</comments>
    <wfw:comment>http://www.namforum.com/blog/wfwcomment.php?cid=49</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.namforum.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=49</wfw:commentRss>
    

    <author>nospam@example.com (Gerard Jensen)</author>
    <content:encoded>
    One of the usual pains when creating your own software is to keep up with the documentation of it. It becomes such a major hassle, because virtually no office suite offers an integrated interface with the development platform you are using, so you eventually end up using your IDE for program development and your usual wordprocessor for the documentation, keeping files at different locations and sooner or later loosing out on synchronicity between your documentation and the actual progress of your development.&lt;br /&gt;
&lt;br /&gt;
If your IDE is &lt;a href=&quot;http://www.eclipse.org/&quot; target=&quot;_blank&quot; title=&quot;Link opens in new window&quot;&gt;Eclipse&lt;/a&gt; though, you can now utilise the &lt;a href=&quot;http://ubion.ion.ag/solutions/003officeintegrationeditor?set_language=en&quot; target=&quot;_blank&quot; title=&quot;Link opens in new window&quot;&gt;Office Integration Editor Plugin&lt;/a&gt;, and as from that day onward use the functionality of a full blown wordprocessor (&quot;Write&quot; from &lt;a href=&quot;http://www.openoffice.org/&quot; target=&quot;_blank&quot; title=&quot;Link opens in new window&quot;&gt;OpenOffice&lt;/a&gt;) to keep your documentation up to date. &lt;br /&gt;
&lt;br /&gt;
Since you now keep your documentation within the development tree of your application, updating your CVS or Subversion repository with new versions of your documentation becomes a breeze - and that in turn allows you as well as your entire development staff to ensure the highest level of quality regarding your documentation too. 
    </content:encoded>

    <pubDate>Mon, 10 Jul 2006 08:46:23 +0200</pubDate>
    <guid isPermaLink="false">http://www.namforum.com/blog/index.php?/archives/49-guid.html</guid>
    
</item>
<item>
    <title>Integrate with OpenOffice instead of MS-Office</title>
    <link>http://www.namforum.com/blog/index.php?/archives/48-Integrate-with-OpenOffice-instead-of-MS-Office.html</link>
            <category>OpenOffice</category>
    
    <comments>http://www.namforum.com/blog/index.php?/archives/48-Integrate-with-OpenOffice-instead-of-MS-Office.html#comments</comments>
    <wfw:comment>http://www.namforum.com/blog/wfwcomment.php?cid=48</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://www.namforum.com/blog/rss.php?version=2.0&amp;type=comments&amp;cid=48</wfw:commentRss>
    

    <author>nospam@example.com (Gerard Jensen)</author>
    <content:encoded>
    Many business applications these days invariably integrate their reporting functions solely with MS-Office. That in turn usually binds people using these kinds of applications to that specific office package too - despite the fact that there&#039;s actually nothing that would keep the developers from also providing a link to OpenOffice too, but they simply haven&#039;t catched on yet.&lt;br /&gt;
&lt;br /&gt;
So what do you do, if you want to wipe MS-Office from your disk and still be able to use the &quot;Office integration&quot; functions of your (usually: closed source) business applications? Well, meet &lt;a href=&quot;http://www.apriorit.com/automateit.html&quot; target=&quot;_blank&quot; title=&quot;Link opens in new window&quot;&gt;AutomateIT!&lt;/a&gt;, a tool that essentially replaces the OLE/COM objects found in MS-Office installations with similar working OpenOffice equivalents. &lt;br /&gt;
&lt;br /&gt;
In essence that now allows you to click the &quot;Export to Excel&quot; buttons in your financial software - and instead of Mirosoft Excel popping up with the export result, you now have OpenOffice Calc pop up with the same data - one could only wish that the world would always be that simple.&lt;br /&gt;
&lt;br /&gt;
Built by &lt;a href=&quot;http://www.apriorit.com/&quot; target=&quot;_blank&quot; title=&quot;Link opens in new window&quot;&gt;ApriorIT&lt;/a&gt;, a Ukranian company, this tool is still so new, it&#039;s only considered to be &quot;alpha software&quot;, yet it already provides a good example of how you can indeed replace yet another Microsoft product with an open source equivalent without having to switch operating systems just yet - and thus allowing you to have a &quot;smoother&quot; transition from Windows to Linux one of these day. 
    </content:encoded>

    <pubDate>Mon, 10 Jul 2006 08:28:18 +0200</pubDate>
    <guid isPermaLink="false">http://www.namforum.com/blog/index.php?/archives/48-guid.html</guid>
    
</item>

</channel>
</rss>