| CODENOTIFIER | HelpYou are not signed inSign in |
Project: Ruport
Revision: 1301
Author: sandal
Date: 14 Apr 2008 10:53:06
Changes:Diff:| ...... | @@ -15,17 +15,17 @@ | |
| 15 | 15 | # of reports. |
| 16 | 16 | # |
| 17 | 17 | # Ruport provides tools for using a number of data sources, including CSV files, |
| 18 | # ActiveRecord models, and raw SQL connections via RubyDBI. | |
| 18 | # ActiveRecord models, and raw SQL connections via RubyDBI (through ruport-util). | |
| 19 | 19 | # |
| 20 | 20 | # Data manipulation is easy as there are standard structures that support |
| 21 | 21 | # record, table, and grouping operations. These all can be extended to |
| 22 | 22 | # implement custom behavior as needed. |
| 23 | 23 | # |
| 24 | 24 | # For common tasks, Ruport provides formatters for CSV, HTML, PDF, and text- |
| 25 | # based reports. However, the real power lies in building custom renderers and | |
| 26 | # formatters. The base formatting libraries provide a number of helper | |
| 27 | # functions that will let you build complex reports while maintaining a DRY and | |
| 28 | # consistent interface. | |
| 25 | # based reports. However, the real power lies in building custom report | |
| 26 | # controllers and formatters. The base formatting libraries provide a number | |
| 27 | # of helper functions that will let you build complex reports while maintaining | |
| 28 | # a DRY and consistent interface. | |
| 29 | 29 | # |
| 30 | 30 | # To get a quick feel for what you can accomplish with Ruport, take a look at |
| 31 | 31 | # a few simple examples provided on our web site. |
| ...... | @@ -40,15 +40,15 @@ | |
| 40 | 40 | # |
| 41 | 41 | # = Installation |
| 42 | 42 | # |
| 43 | # To install ruport via rubygems with all it's dependencies (except DBI): | |
| 43 | # To install ruport via rubygems: | |
| 44 | 44 | # |
| 45 | # sudo gem install ruport -y | |
| 45 | # sudo gem install ruport | |
| 46 | 46 | # |
| 47 | 47 | # Check to see if it installed properly: |
| 48 | 48 | # |
| 49 | 49 | # ruby -rubygems -e "require 'ruport'; puts Ruport::VERSION" |
| 50 | 50 | # |
| 51 | # If you get an error, please consult the mailing list. | |
| 51 | # If you get an error, please let us know on our mailing list. | |
| 52 | 52 | # |
| 53 | 53 | # Dependencies Details: |
| 54 | 54 | # |
| ...... | @@ -61,19 +61,29 @@ | |
| 61 | 61 | # |
| 62 | 62 | # If you wish to use Ruport to report against a rails project, |
| 63 | 63 | # a camping project, or do standalone acts_as_reportable reports, you'll need |
| 64 | # ActiveRecord. | |
| 64 | # ActiveRecord and the acts_as_reportable gem. | |
| 65 | 65 | # |
| 66 | 66 | # If you want to use Ruport::Query for raw SQL support, you'll need to |
| 67 | # install RubyDBI and whatever database drivers you might need. | |
| 67 | # install ruport-util, RubyDBI and whatever database drivers you might need. | |
| 68 | 68 | # |
| 69 | # = Resources | |
| 69 | # = Resources | |
| 70 | 70 | # |
| 71 | # The best way to get help and make suggestions is the Ruport mailing list. | |
| 71 | # Our developers have published a free-content book about all things | |
| 72 | # Ruport, including complete coverage of acts_as_reportable and some of | |
| 73 | # ruport-util's features. This book serves as the definitive guide to | |
| 74 | # Ruport, so all users should become acquainted with it: | |
| 75 | # | |
| 76 | # http://ruportbook.com | |
| 77 | # | |
| 78 | # The next best way to get help and make suggestions is the Ruport mailing list. | |
| 72 | 79 | # This software is on the move, so the list is the most reliable way of getting |
| 73 | 80 | # up to date information. |
| 74 | 81 | # |
| 75 | 82 | # - You can sign up and/or view the archives here: |
| 76 | # http://groups.google.com/group/ruby-reports | |
| 83 | # http://groups.google.com/group/ruby-reports | |
| 84 | # | |
| 85 | # If you are looking to dig a little deeper, there are a couple more resources | |
| 86 | # that may be helpful to you. | |
| 77 | 87 | # |
| 78 | 88 | # - The latest stable API documentation is available at: |
| 79 | 89 | # http://api.rubyreports.org |
| ...... | @@ -83,6 +93,22 @@ | |
| 83 | 93 | # |
| 84 | 94 | # = Hacking |
| 85 | 95 | # |
| 86 | # If you'd like to work on Ruport, please post on the list and let us know what | |
| 87 | # you're interested in doing, or contact Gregory Brown or Michael Milner if you | |
| 88 | # have questions. | |
| 96 | # If you'd like to contribute code to Ruport, please join our development | |
| 97 | # mailing list, and let us know what you'd like to do! | |
| 98 | # | |
| 99 | # http://groups.google.com/group/ruport-dev | |
| 100 | # | |
| 101 | # It also may be worthwhile to join this list if you plan on running edge | |
| 102 | # versions of Ruport, as this is where we make announcements about major | |
| 103 | # breakage in trunk. | |
| 104 | # | |
| 105 | # We are very responsive to contributors, and review every patch we receive | |
| 106 | # fairly quickly. Most contributors who successfully get a patch or two applied | |
| 107 | # are given write access to the repositories and invited to join Ruport's | |
| 108 | # development team. Since we view every user as potential contributor, this | |
| 109 | # approach works well for us. | |
| 110 | # | |
| 111 | # So if you want to help out with Ruport, we'll happy accept your efforts! | |
| 112 | ||
| 113 | ||
| 114 |
| ...... | @@ -15,17 +15,17 @@ | |
| 15 | 15 | # of reports. |
| 16 | 16 | # |
| 17 | 17 | # Ruport provides tools for using a number of data sources, including CSV files, |
| 18 | # ActiveRecord models, and raw SQL connections via RubyDBI. | |
| 18 | # ActiveRecord models, and raw SQL connections via RubyDBI (through ruport-util). | |
| 19 | 19 | # |
| 20 | 20 | # Data manipulation is easy as there are standard structures that support |
| 21 | 21 | # record, table, and grouping operations. These all can be extended to |
| 22 | 22 | # implement custom behavior as needed. |
| 23 | 23 | # |
| 24 | 24 | # For common tasks, Ruport provides formatters for CSV, HTML, PDF, and text- |
| 25 | # based reports. However, the real power lies in building custom renderers and | |
| 26 | # formatters. The base formatting libraries provide a number of helper | |
| 27 | # functions that will let you build complex reports while maintaining a DRY and | |
| 28 | # consistent interface. | |
| 25 | # based reports. However, the real power lies in building custom report | |
| 26 | # controllers and formatters. The base formatting libraries provide a number | |
| 27 | # of helper functions that will let you build complex reports while maintaining | |
| 28 | # a DRY and consistent interface. | |
| 29 | 29 | # |
| 30 | 30 | # To get a quick feel for what you can accomplish with Ruport, take a look at |
| 31 | 31 | # a few simple examples provided on our web site. |
| ...... | @@ -40,15 +40,15 @@ | |
| 40 | 40 | # |
| 41 | 41 | # = Installation |
| 42 | 42 | # |
| 43 | # To install ruport via rubygems with all it's dependencies (except DBI): | |
| 43 | # To install ruport via rubygems: | |
| 44 | 44 | # |
| 45 | # sudo gem install ruport -y | |
| 45 | # sudo gem install ruport | |
| 46 | 46 | # |
| 47 | 47 | # Check to see if it installed properly: |
| 48 | 48 | # |
| 49 | 49 | # ruby -rubygems -e "require 'ruport'; puts Ruport::VERSION" |
| 50 | 50 | # |
| 51 | # If you get an error, please consult the mailing list. | |
| 51 | # If you get an error, please let us know on our mailing list. | |
| 52 | 52 | # |
| 53 | 53 | # Dependencies Details: |
| 54 | 54 | # |
| ...... | @@ -61,19 +61,29 @@ | |
| 61 | 61 | # |
| 62 | 62 | # If you wish to use Ruport to report against a rails project, |
| 63 | 63 | # a camping project, or do standalone acts_as_reportable reports, you'll need |
| 64 | # ActiveRecord. | |
| 64 | # ActiveRecord and the acts_as_reportable gem. | |
| 65 | 65 | # |
| 66 | 66 | # If you want to use Ruport::Query for raw SQL support, you'll need to |
| 67 | # install RubyDBI and whatever database drivers you might need. | |
| 67 | # install ruport-util, RubyDBI and whatever database drivers you might need. | |
| 68 | 68 | # |
| 69 | # = Resources | |
| 69 | # = Resources | |
| 70 | 70 | # |
| 71 | # The best way to get help and make suggestions is the Ruport mailing list. | |
| 71 | # Our developers have published a free-content book about all things | |
| 72 | # Ruport, including complete coverage of acts_as_reportable and some of | |
| 73 | # ruport-util's features. This book serves as the definitive guide to | |
| 74 | # Ruport, so all users should become acquainted with it: | |
| 75 | # | |
| 76 | # http://ruportbook.com | |
| 77 | # | |
| 78 | # The next best way to get help and make suggestions is the Ruport mailing list. | |
| 72 | 79 | # This software is on the move, so the list is the most reliable way of getting |
| 73 | 80 | # up to date information. |
| 74 | 81 | # |
| 75 | 82 | # - You can sign up and/or view the archives here: |
| 76 | # http://groups.google.com/group/ruby-reports | |
| 83 | # http://groups.google.com/group/ruby-reports | |
| 84 | # | |
| 85 | # If you are looking to dig a little deeper, there are a couple more resources | |
| 86 | # that may be helpful to you. | |
| 77 | 87 | # |
| 78 | 88 | # - The latest stable API documentation is available at: |
| 79 | 89 | # http://api.rubyreports.org |
| ...... | @@ -83,6 +93,22 @@ | |
| 83 | 93 | # |
| 84 | 94 | # = Hacking |
| 85 | 95 | # |
| 86 | # If you'd like to work on Ruport, please post on the list and let us know what | |
| 87 | # you're interested in doing, or contact Gregory Brown or Michael Milner if you | |
| 88 | # have questions. | |
| 96 | # If you'd like to contribute code to Ruport, please join our development | |
| 97 | # mailing list, and let us know what you'd like to do! | |
| 98 | # | |
| 99 | # http://groups.google.com/group/ruport-dev | |
| 100 | # | |
| 101 | # It also may be worthwhile to join this list if you plan on running edge | |
| 102 | # versions of Ruport, as this is where we make announcements about major | |
| 103 | # breakage in trunk. | |
| 104 | # | |
| 105 | # We are very responsive to contributors, and review every patch we receive | |
| 106 | # fairly quickly. Most contributors who successfully get a patch or two applied | |
| 107 | # are given write access to the repositories and invited to join Ruport's | |
| 108 | # development team. Since we view every user as potential contributor, this | |
| 109 | # approach works well for us. | |
| 110 | # | |
| 111 | # So if you want to help out with Ruport, we'll happy accept your efforts! | |
| 112 | ||
| 113 | ||
| 114 |