<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Reporting Tales - openoffice.org tag</title>
  <link>http://www.sherito.org/tags/openoffice.org/</link>
  <description>.. if it is not printed, it can&#039;t be real</description>
  <language>en</language>
  <copyright>Thomas Morgner</copyright>
  <lastBuildDate>Tue, 26 Aug 2008 11:33:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Sunny days for the Flow-Engine</title>
    <link>http://www.sherito.org/2007/04/19/1176976020000.html</link>
    
      
        <description>
          &lt;p align=&#034;justify&#034;&gt; Its finally gone public: &lt;a href=&#034;http://www.openoffice.org/&#034;&gt;OpenOffice&lt;/a&gt; uses the new &lt;a href=&#034;http://reporting.pentaho.org/&#034;&gt;Pentaho Reporting Flow Engine&lt;/a&gt; as backend for their new &lt;a href=&#034;http://blogs.sun.com/GullFOSS/entry/report_designer_will_extend_the&#034;&gt;Report Designer&lt;/a&gt;. &lt;/p&gt;
&lt;div align=&#034;justify&#034;&gt; &lt;/div&gt;
&lt;p align=&#034;justify&#034;&gt; I strongly believe that this is a big win for both communities. OpenOffice was in bad need for a sane reporting system, that is fully integrated into the office suite. Sure, with OpenOffice 2.0, they already introduced one - but this one was more or less a extended mail-merge system. And honestly, I was never able to design a report from scratch with that thing.  &lt;/p&gt;
&lt;div align=&#034;justify&#034;&gt; &lt;/div&gt;
&lt;p align=&#034;justify&#034;&gt; Ocke Jansen created a modern (and beautiful) UI to design banded reports now. Adding elements to the report is now a lot easier - just grab the mouse and drag&#039;n&#039;drop them where you want them to appear. Simple and easy to use - that&#039;s how reporting should be. &lt;/p&gt;
&lt;p align=&#034;justify&#034;&gt; &lt;/p&gt;
&lt;p align=&#034;justify&#034;&gt; And once you&#039;ve finished the design, you heat up the engine and tell it whether you want a Text-Document or a Spreasheet-Document. And just in the twinkling of an eye later you get the results. &lt;/p&gt;
&lt;div align=&#034;justify&#034;&gt; &lt;/div&gt;
&lt;p align=&#034;justify&#034;&gt; But the interesting part lies hidden deep inside the engine: The Flow-Engine works natively on the OpenOffice document structures. The engine does not waste time converting the OpenOffice-tables, paragraphs and everything else into an internal proprietary representation -  simple take what we get and process it immediatly.  &lt;/p&gt;
&lt;p align=&#034;justify&#034;&gt; And we do it fast. Displaying the results in the OpenOffice-Writer takes more time than the report generation itself.  &lt;/p&gt;
&lt;p align=&#034;justify&#034;&gt; And we do it conservatively, with as little memory as possible while preserving all incoming report structures. So no matter what valid OpenDocument content you want to process - the engine will happily accept it from you and produces all the report you always wanted to produce. &lt;/p&gt;
        </description>
      
      
    
    
    
    <comments>http://www.sherito.org/2007/04/19/1176976020000.html#comments</comments>
    <guid isPermaLink="true">http://www.sherito.org/2007/04/19/1176976020000.html</guid>
    <pubDate>Thu, 19 Apr 2007 09:47:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>
