<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Build map mashups with the Map Rails Kit</title>
	<atom:link href="http://blog.railskits.com/2008/09/build-map-mashups-with-the-map-rails-kit/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.railskits.com/2008/09/build-map-mashups-with-the-map-rails-kit/</link>
	<description>Get Code. Get Moving.</description>
	<lastBuildDate>Mon, 22 Sep 2008 18:56:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ray Neville</title>
		<link>http://blog.railskits.com/2008/09/build-map-mashups-with-the-map-rails-kit/comment-page-1/#comment-215</link>
		<dc:creator>Ray Neville</dc:creator>
		<pubDate>Mon, 22 Sep 2008 18:56:52 +0000</pubDate>
		<guid isPermaLink="false">http://railskits.com/?p=82#comment-215</guid>
		<description>Rails Reporting – A Showstopper - An Appeal!

Ben, You might consider this for a Kit. 

Gregory Browne is working on an update of Ruport called Prawn.

We are converting 3 of our existing successful PC based software apps to Rails for SaaS.

The Showstopper is Rails Reporting!

We have tried unsuccessfully to generate supplier statements from our dev app using Ruport.

We purchased the Ruport book but still no joy after 6 weeks!

Unless Rails gets a good, easy to use Reporting system/plugin then I’m afraid I don’t hold out much hope for its commercial use – fine for social networks etc.

Having used reporting from other frameworks in the past the basic requirements are:-

1. Generate the data required to populate each part of the report – not difficult in Rails

2. Provide the following report segments into which the data can be placed for pdf formatting.

.header                        – document header - optional

.group header1            – first group header for first grouped data - optional

.group header2            – second group header for second grouped data - optional

.items                           – to list items - optional

.group trailer2              – to place summary of .items including calculated attributes &amp; other related table attributes e.g Tax Rate etc

.page                           - to generate a new page for each group2 - optional

.group trailer1              - to place any summary data for group header1 - optional 

.page                           - to generate a new page for each group1 - optional

.end                             – to place document grand totals –optional

automatic pagination with repeat of group header on next page where overflow occurs of .items to second or subsequent page

FOR THE SAKE OF RAILS – A BRILLIANT FRAMEWORK!!! 

Regards
Ray Neville
Neville SaaS 
(DataEase Expert)</description>
		<content:encoded><![CDATA[<p>Rails Reporting – A Showstopper &#8211; An Appeal!</p>
<p>Ben, You might consider this for a Kit. </p>
<p>Gregory Browne is working on an update of Ruport called Prawn.</p>
<p>We are converting 3 of our existing successful PC based software apps to Rails for SaaS.</p>
<p>The Showstopper is Rails Reporting!</p>
<p>We have tried unsuccessfully to generate supplier statements from our dev app using Ruport.</p>
<p>We purchased the Ruport book but still no joy after 6 weeks!</p>
<p>Unless Rails gets a good, easy to use Reporting system/plugin then I’m afraid I don’t hold out much hope for its commercial use – fine for social networks etc.</p>
<p>Having used reporting from other frameworks in the past the basic requirements are:-</p>
<p>1. Generate the data required to populate each part of the report – not difficult in Rails</p>
<p>2. Provide the following report segments into which the data can be placed for pdf formatting.</p>
<p>.header                        – document header &#8211; optional</p>
<p>.group header1            – first group header for first grouped data &#8211; optional</p>
<p>.group header2            – second group header for second grouped data &#8211; optional</p>
<p>.items                           – to list items &#8211; optional</p>
<p>.group trailer2              – to place summary of .items including calculated attributes &amp; other related table attributes e.g Tax Rate etc</p>
<p>.page                           &#8211; to generate a new page for each group2 &#8211; optional</p>
<p>.group trailer1              &#8211; to place any summary data for group header1 &#8211; optional </p>
<p>.page                           &#8211; to generate a new page for each group1 &#8211; optional</p>
<p>.end                             – to place document grand totals –optional</p>
<p>automatic pagination with repeat of group header on next page where overflow occurs of .items to second or subsequent page</p>
<p>FOR THE SAKE OF RAILS – A BRILLIANT FRAMEWORK!!! </p>
<p>Regards<br />
Ray Neville<br />
Neville SaaS<br />
(DataEase Expert)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
