search for: sichanugrist

...epos add the rest of the maintainers. Second I will add a note on each rails/plugin mentioning this repos updates. So from now on, if someone else is interested in helping/contributing please send a message to the appropriate repo owner. verification (https://github.com/sikachu/verification) Prem Sichanugrist Rishav Rastogi country_select (https://github.com/chrislerum/country_select) Mark Turner Chris Lerum Devdatta dynamic_form (https://github.com/joelmoss/dynamic_form) Prem Sichanugrist Joel Moss Devdatta exception_notification (https://github.com/smartinez87/exception_notification) Sebastián Mart...

Hi Guys, I just realize that on the API documentation the code snippet is overflowing off the screen. Is this an intended behavior? Or who should I contact to get this one fixed. You can see the screenshot here: http://skitch.com/sikachu/dw82n/screen-shot-2553-08-30-at-16.24.26 Thanks :) Prem Sichanugrist -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For more options...

...stones page (https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/milestones) and found out that Rails 2.3.6 was due Jan 15, 2010. Does it mean all tickets in that milestone should be cleared first? If so, then I would pay attention to clear tickets in that bucket first. Thank you, Prem Sichanugrist (sikachu) -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com. For mo...

Hello, I have a suggestion to improve the Rails Lighthouse overview page. At present the description is very large. You need to scroll to find the tickets and more importantly the list of pages. I think a shorter description along the lines of http://i48.tinypic.com/2z6a7lt.png would be much better. All the information at present in the description can be moved into pages, and they can be linked

(I posted this as a bug in GitHub (https://github.com/rails/rails/issues/7018), but then someone there told me I should post it here, so here it is.) If you set attr_accessible on some properties in an ActiveRecord-descended class, and then attr_protected on others - the class becomes ''default-open'' - if any properties are missed or added later, they will be accessible by

Forms without explicit enctype are submitted as application/x-www-form- urlencoded. This is the default behaviour in Rails. However, this enctype does not allow transmission of binary data (files). Would it not make sense to specify the enctype multipart/form-data by default instead? i.e. all the form_for helpers would add this enctype to the form tag, unless overriden by the developer. This

Is there any reason why db:setup and db:reset don''t show any more on "rake -T db"? I guess any rake task that is defined only as a group of other tasks (without any ruby blocks attached) presents this problem. Also let me write this as a remember note to myself for when I have some time: the Rails Guides on Migrations should be updated to include instructions about db:load

Hello all, I''m working on a Rails app and I have resources nested three deep - let''s call them user, project, and issues. The route helpers now look like user_project_issue_path(@user, @project, @issue). Would it make sense for Rails to guess the @user <https://github.com/user> and @project<https://github.com/project> relations from @issue

In Rails 3 routing, it seems we''re using the match() method to hook up arbitrary url patterns to rack endpoints (which I think is a great new routing feature). I''d like to suggest that we name it "connect", instead of "match": 1. It maintains continuity with previous versions of rails 2. It''s more descriptive of the intention of a route: to connect

Yes, I know that Rails *2.3.x* is no longer fully supported (this is why I''m posting it to rails/issues). Still, I would like to post the topic so that everyone who experience the same problem could quickly google for it (no, afaik no solution for this yet). I''m trying to migrate a 1.5 years *2.3.x* app from Ruby version *1.8.7* to * 1.9.3-p0*. The strange problem I

I found out today that Range#include? behaves differently on 1.9 than on 1.8 ( http://rhnh.net/2009/08/03/range-include-in-ruby-1-9 ) In order to deal with various edge cases, instead of just checking whether range.first <= value <= range.last, in ruby 1.9 include? steps through all the values in the range, checking for equality. This is of course a lot slower - in my case, checking a date

In Rails 3, is it possible to have a plugin inside an engine? Adding the lib dir of the plugin to autoload_paths doesn''t seem to work. I can manage to load it by adding that path to $: and requiring the init.rb file, but I''m not sure that''s the correct approach. Thanks! -- You received this message because you are subscribed to the Google Groups "Ruby on Rails:

Hi, it would be nice to have the touch option in has_many associations also. I have a scenario like this: An user has some credit (money) and some advertises. Each advertise can be enabled or disabled depending on some rules. One of the rules is that the user should have money. Each time the money of the user change, the advertises are touched, enabled/disabled and then cached, as they are much