From m.fellinger at gmail.com Sat Jun 16 23:29:20 2007 From: m.fellinger at gmail.com (Michael Fellinger) Date: Sun, 17 Jun 2007 12:29:20 +0900 Subject: [Rg 35] [ANN] Ramaze Version 0.1.2 Message-ID: <9c00d3e00706162029s3eb54db2s1fa1e30df5bab377@mail.gmail.com> This time we are proud to announce Version 0.1.2 of the Ramaze framework, an open source web framework with the aim to be light and modular. Since the 0.1.0 release we have made a lot of progress and the overall API has mostly settled down. An extensive set of tests is covering almost every detail of the implementation and usage. It is developed by by several people and already in production-use at some companies. Homepage: http://ramaze.rubyforge.org IRC: #ramaze on irc.freenode.net New Features in Version 0.1.2: - Restructuring of Ramaze internals, featuring a cleaner overall layout. - Add Ramaze::Record to easily record requests fitting particular patterns. - Support for the Remarkably templating engine. - Adapted for Rack 0.2 - Easier caching. - replacing autoreload with a general SourceReload class. - Reviewed and largely improved tutorial and tested examples. - Even less patches to the Ruby core, mostly for compatibility with the upcoming Ruby 1.9 and tested with older versions down to 1.8.2. - Largely improved Spec-framework for any kind of web-application. - Through some benchmarking and refactoring the overall speed has improved around the factor 2-3. A complete Changelog is available at http://manveru.mine.nu/ramaze/doc/CHANGELOG Features: - Builds on top of the recently released Rack library, which provides easy use of adapters like Mongrel, WEBrick, CGI or FCGI. - Supports a wide range of templating-engines like: Amrita2, Erubis, HAML, Liquid, Markaby, Remarkably and its own engine called Ezamar. - Highly modular structure, you can just use the parts you like. This also means that it's very simple to add your own customizations. - A variety of helpers is already available, giving you things like advanced caching, OpenID-authentication or aspect-oriented programming for your controllers. - It is possible to use the ORM you like, be it ActiveRecord, Og, Kansas or something more simplistic like a wrapper around YAML::Store. - Good documentation: although we don't have 100% documentation right now, just about every part of Ramaze is covered with basic and advanced docs. There are a variety of examples and a tutorial available. - Friendly community: lastly, but still quite important, there are people from all over the world using Ramaze, so you can get almost instant help and info. For more information please come to http://ramaze.rubyforge.org or ask directly on IRC (irc://irc.freenode.net/#ramaze) Thank you, Michael 'manveru' Fellinger and the Ramaze community From lasso at lassoweb.se Mon Jun 18 16:19:10 2007 From: lasso at lassoweb.se (Lars Olsson) Date: Mon, 18 Jun 2007 22:19:10 +0200 Subject: [Rg 36] Re: [ANN] Ramaze Version 0.1.2 In-Reply-To: <9c00d3e00706162029s3eb54db2s1fa1e30df5bab377@mail.gmail.com> References: <9c00d3e00706162029s3eb54db2s1fa1e30df5bab377@mail.gmail.com> Message-ID: <4676E8BE.6070903@lassoweb.se> Great! Congratulations on a solid release. I'm very happy the upgrade didn't break my "old" apps as 0.1.1 did. I also got my webspace provider (OCS Solutions) to install Ramaze. They now provide Rails, Nitro and Ramaze and a ton of other ruby stuff. :) Kindly /lasso Michael Fellinger skrev: > This time we are proud to announce Version 0.1.2 of the Ramaze framework, an > open source web framework with the aim to be light and modular. > > Since the 0.1.0 release we have made a lot of progress and the overall API has > mostly settled down. An extensive set of tests is covering almost every detail > of the implementation and usage. > > It is developed by by several people and already in production-use at some > companies. > > > Homepage: http://ramaze.rubyforge.org > IRC: #ramaze on irc.freenode.net > > > New Features in Version 0.1.2: > > - Restructuring of Ramaze internals, featuring a cleaner overall layout. > > - Add Ramaze::Record to easily record requests fitting particular patterns. > > - Support for the Remarkably templating engine. > > - Adapted for Rack 0.2 > > - Easier caching. > > - replacing autoreload with a general SourceReload class. > > - Reviewed and largely improved tutorial and tested examples. > > - Even less patches to the Ruby core, mostly for compatibility with the > upcoming Ruby 1.9 and tested with older versions down to 1.8.2. > > - Largely improved Spec-framework for any kind of web-application. > > - Through some benchmarking and refactoring the overall speed has improved > around the factor 2-3. > > A complete Changelog is available at http://manveru.mine.nu/ramaze/doc/CHANGELOG > > > Features: > - Builds on top of the recently released Rack library, which provides easy use > of adapters like Mongrel, WEBrick, CGI or FCGI. > > - Supports a wide range of templating-engines like: > Amrita2, Erubis, HAML, Liquid, Markaby, Remarkably and its own engine > called Ezamar. > > - Highly modular structure, you can just use the parts you like. This also > means that it's very simple to add your own customizations. > > - A variety of helpers is already available, giving you things like advanced > caching, OpenID-authentication or aspect-oriented programming for your > controllers. > > - It is possible to use the ORM you like, be it ActiveRecord, Og, Kansas or > something more simplistic like a wrapper around YAML::Store. > > - Good documentation: although we don't have 100% documentation right now, > just about every part of Ramaze is covered with basic and advanced docs. > There are a variety of examples and a tutorial available. > > - Friendly community: lastly, but still quite important, there are people from > all over the world using Ramaze, so you can get almost instant help and > info. > > > For more information please come to http://ramaze.rubyforge.org or ask directly > on IRC (irc://irc.freenode.net/#ramaze) > > Thank you, > Michael 'manveru' Fellinger and the Ramaze community > _______________________________________________ > Ramaze-general mailing list > Ramaze-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/ramaze-general From john at oxyliquit.de Tue Jun 19 01:18:54 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Tue, 19 Jun 2007 08:18:54 +0300 Subject: [Rg 37] Re: [ANN] Ramaze Version 0.1.2 In-Reply-To: <4676E8BE.6070903@lassoweb.se> References: <9c00d3e00706162029s3eb54db2s1fa1e30df5bab377@mail.gmail.com> <4676E8BE.6070903@lassoweb.se> Message-ID: Hi, > Great! I agree. :P > Congratulations on a solid release. I'm very happy the upgrade didn't > break my "old" apps as 0.1.1 did. Glad to see this was an easy migration (for me it wasn't quite, but that that's because I use too many internal features ;)) for you. :) > I also got my webspace provider (OCS Solutions) to install Ramaze. They > now provide Rails, Nitro and Ramaze and a ton of other ruby stuff. :) Hey, nice, that's also "spreading the word", so thanks! ^_^ Jo -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From lasso at lassoweb.se Wed Jun 20 12:58:18 2007 From: lasso at lassoweb.se (Lars Olsson) Date: Wed, 20 Jun 2007 18:58:18 +0200 Subject: [Rg 38] Informer tags Message-ID: <46795CAA.9090704@lassoweb.se> Hi! I'm planning to write a small patch for the Informer class to allow filtering (based on tag content). The Ramaze::Informer.inform method takas a tag as an argument and I've seen :info and :debug used so far. I'm wondering about what tags I might expect from Ramaze itself. (Looking at the Informing module I guess :debug, :error, :info and :warn are possible). Are there any more tags that I should be aware of? Sincerely /laso -- ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ From m.fellinger at gmail.com Wed Jun 20 13:52:40 2007 From: m.fellinger at gmail.com (Michael Fellinger) Date: Thu, 21 Jun 2007 02:52:40 +0900 Subject: [Rg 39] Re: Informer tags In-Reply-To: <46795CAA.9090704@lassoweb.se> References: <46795CAA.9090704@lassoweb.se> Message-ID: <9c00d3e00706201052h1b0f074en75e53aa47a0e190d@mail.gmail.com> On 6/21/07, Lars Olsson wrote: > Hi! > > I'm planning to write a small patch for the Informer class to allow > filtering (based on tag content). The Ramaze::Informer.inform method > takas a tag as an argument and I've seen :info and :debug used so far. :warn and :error are used... :warn very seldom but :error relatively often (on errors ;) > I'm wondering about what tags I might expect from Ramaze itself. > (Looking at the Informing module I guess :debug, :error, :info and :warn > are possible). Are there any more tags that I should be aware of? Ramaze only uses these 4, it is the only fragment that is left from our old tag-based logging-system and i don't have problems locking them down as long as there are benefits from it. Also have a look into LogHub, which allows pre-filtering for all loggers already, maybe you could improve and/or replace it, i currently don't use it at all and for example Analogger has its own handling. I basically tried to find the lowest common denominator in the beginning, but it turned out that people hardly ever customize the output of logging but love to switch logging-systems themselves. Anyway, i'm open for anything you may come up with :) ^ manveru > Sincerely > > /laso From lasso at lassoweb.se Tue Jun 26 15:00:05 2007 From: lasso at lassoweb.se (Lars Olsson) Date: Tue, 26 Jun 2007 21:00:05 +0200 Subject: [Rg 40] Small Informer patch Message-ID: <46816235.4020404@lassoweb.se> Hi! I've created a small patch to allow the Informer class to only catch specific tags (any combination of :debug, :error, :info and :warn messages). This allows for better log separation. For instance, you could log all errors to a file while just showing debug info on the screen. Like this: Inform.loggers.clear Inform.loggers << Informer.new(File.new('logs/errors.log', 'w'), [:error]) Inform.loggers << Informer.new($stdout, [:debug]) Anyway, I'll hope you find this patch useful. Adapt it at your pleasure (or just nuke it if you don't like it). Kindly /lasso ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: informer_log_levels Url: http://rubyforge.org/pipermail/ramaze-general/attachments/20070626/672b6112/attachment.pl From m.fellinger at gmail.com Tue Jun 26 21:26:25 2007 From: m.fellinger at gmail.com (Michael Fellinger) Date: Wed, 27 Jun 2007 10:26:25 +0900 Subject: [Rg 41] Re: Small Informer patch In-Reply-To: <46816235.4020404@lassoweb.se> References: <46816235.4020404@lassoweb.se> Message-ID: <9c00d3e00706261826p749d5257p7031caaaf0e1efa6@mail.gmail.com> On 6/27/07, Lars Olsson wrote: > Hi! > > I've created a small patch to allow the Informer class to only catch > specific tags (any combination of :debug, :error, :info and :warn > messages). This allows for better log separation. For instance, you > could log all errors to a file while just showing debug info on the > screen. Like this: > > Inform.loggers.clear > Inform.loggers << Informer.new(File.new('logs/errors.log', 'w'), [:error]) > Inform.loggers << Informer.new($stdout, [:debug]) > > Anyway, I'll hope you find this patch useful. Adapt it at your pleasure > (or just nuke it if you don't like it). I think it's a good patch, but could you please paste (p.caboo.se or the like) them somewhere else or make them an attachment, maybe it's just gmail that is messing it up, but i can't get darcs to apply it when i just copy&paste. Thanks in advance, it's no big patch (though a quite useful one) but i'd like to attribute the patch to you directly :) ^ manveru From lasso at lassoweb.se Wed Jun 27 16:34:54 2007 From: lasso at lassoweb.se (Lars Olsson) Date: Wed, 27 Jun 2007 22:34:54 +0200 Subject: [Rg 42] Re: Small Informer patch In-Reply-To: <9c00d3e00706261826p749d5257p7031caaaf0e1efa6@mail.gmail.com> References: <46816235.4020404@lassoweb.se> <9c00d3e00706261826p749d5257p7031caaaf0e1efa6@mail.gmail.com> Message-ID: <4682C9EE.7000907@lassoweb.se> Hi! Using Caboo is a bit boring, don't you think? ;) We got all this new and shine stuff...like Ramaze and Og. Why not make use of it? I just wrote a small controller for managing pasties...doesn't look to fancy at the moment, but it works! =) The controller lives at http://www.lassoweb.se/snippets and the patch is the first link. Enjoy! Kindly /lasso Michael Fellinger skrev: > I think it's a good patch, but could you please paste (p.caboo.se or > the like) them somewhere else or make them an attachment, maybe it's > just gmail that is messing it up, but i can't get darcs to apply it > when i just copy&paste. -- ________________________________________ Lars Olsson lasso at lassoweb.se http://www.lassoweb.se/ From m.fellinger at gmail.com Wed Jun 27 21:51:17 2007 From: m.fellinger at gmail.com (Michael Fellinger) Date: Thu, 28 Jun 2007 10:51:17 +0900 Subject: [Rg 43] Re: Small Informer patch In-Reply-To: <4682C9EE.7000907@lassoweb.se> References: <46816235.4020404@lassoweb.se> <9c00d3e00706261826p749d5257p7031caaaf0e1efa6@mail.gmail.com> <4682C9EE.7000907@lassoweb.se> Message-ID: <9c00d3e00706271851jbb3ed7yd2a76a50575a443a@mail.gmail.com> On 6/28/07, Lars Olsson wrote: > Hi! > > Using Caboo is a bit boring, don't you think? ;) We got all this new and > shine stuff...like Ramaze and Og. Why not make use of it? > > I just wrote a small controller for managing pasties...doesn't look to > fancy at the moment, but it works! =) > > The controller lives at http://www.lassoweb.se/snippets and the patch is > the first link. Enjoy! yay :D please check out http://code.google.com/p/syntaxhighlighter/wiki/Overview - maybe you could add that to the snippets... :) applied your patch right away. > > I think it's a good patch, but could you please paste (p.caboo.se or > > the like) them somewhere else or make them an attachment, maybe it's > > just gmail that is messing it up, but i can't get darcs to apply it > > when i just copy&paste. From lasso at lassoweb.se Sat Jun 30 13:06:12 2007 From: lasso at lassoweb.se (Lars Olsson) Date: Sat, 30 Jun 2007 19:06:12 +0200 Subject: [Rg 44] Defining custom error action? Message-ID: <46868D84.2070202@lassoweb.se> Hi! (I know this isn't Nitro general, but that's where I'm porting my app from...) In Nitro I can customize the error handling in a controller p? creating my own 'error' method. If I try to do the same in Ramaze I get "undefined method `each' for nil:NilClass" with the following stack trace: [2007-06-30 18:50:05] ERROR # [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/controller/resolve.rb:148:in `raise_no_action' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/controller/resolve.rb:41:in `resolve' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/controller.rb:140:in `handle' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher/action.rb:20:in `process' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:85:in `filter' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:84:in `each' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:84:in `filter' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:44:in `dispatch' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:43:in `catch' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:43:in `dispatch' [2007-06-30 18:50:05] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:42:in `catch' [2007-06-30 18:50:05] DEBUG The Action: # [2007-06-30 18:50:06] ERROR # [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/proto/public/error.zmr:19:in `binding' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/action.rb:101:in `binding' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/action.rb:101:in `instance_eval' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/action.rb:101:in `binding' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/template/ezamar.rb:23:in `transform' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/action/render.rb:39:in `uncached_render' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/action/render.rb:21:in `render' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/controller.rb:141:in `handle' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher/action.rb:20:in `process' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:85:in `filter' [2007-06-30 18:50:06] ERROR /usr/local/lib/ruby/gems/1.8/gems/ramaze-0.1.2/lib/ramaze/dispatcher.rb:84:in `each' # The code that is causing the error class MainController < Ramaze::Controller def error # It doesn't matter what I put here, I always get the same error Thread.current[:exception].inspect end end Is it possible to use a custom error handler in Ramaze? Sincerely /lasso ________________________________________ Lars Olsson lasso at lassoweb.nu http://www.lassoweb.nu/ From john at oxyliquit.de Sat Jun 30 13:30:39 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Sat, 30 Jun 2007 20:30:39 +0300 Subject: [Rg 45] Re: Defining custom error action? In-Reply-To: <46868D84.2070202@lassoweb.se> References: <46868D84.2070202@lassoweb.se> Message-ID: Hi, > (I know this isn't Nitro general, but that's where I'm porting my app > from...) no worries, everything's fine. :) > In Nitro I can customize the error handling in a controller p? creating > my own 'error' method. If I try to do the same in Ramaze I get > "undefined method `each' for nil:NilClass" with the following stack > trace: > # The code that is causing the error > class MainController < Ramaze::Controller > > def error > # It doesn't matter what I put here, I always get the same error > Thread.current[:exception].inspect Sidenote: If you use the newest ramaze repo, you can use Ramaze::Dispatcher::Error.current instead of the thread var. > Is it possible to use a custom error handler in Ramaze? I guess the standard error-template is still getting loaded, that'd be my guess anyway. Did you try creating an (empty?) error.xhtml in the template folder? The error-handling in Ramaze is quite flexible, enabling you to create different error handlers for different errors (I for example catch Og errors nicely that way). error.rb for more info. Hope that helps, Jo -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From john at oxyliquit.de Sat Jun 30 17:34:19 2007 From: john at oxyliquit.de (Jonathan Buch) Date: Sun, 01 Jul 2007 00:34:19 +0300 Subject: [Rg 46] Re: Defining custom error action? In-Reply-To: <46868D84.2070202@lassoweb.se> References: <46868D84.2070202@lassoweb.se> Message-ID: Hi, a note, I discussed the matter of the default error template with manveru and we both came to the conclusion that it might be better if it was not included by default. So, the very newest repo has a patch for that. Now, if you want to use the standard error template, you either have to copy it yourself or use `ramaze --create` to get a new project set up with it. Reason for that is that we avoid problems like yours, it removes some complexity from the template resolver and everyone who sets up his own ramaze projects instead of using the proto knows what he's doing and so doesn't need advice (yeah right :P). So, basically by pulling newest repo your problems should all go away, isn't that cool. :P Jo -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/