search for: instancetags

What is the best way to override some of the FormHelper default options? Right now I''m adding this to the beginning of my environment.rb: ActionView::Helpers::InstanceTag::DEFAULT_TEXT_AREA_OPTIONS = { "cols" => 80, "rows" => 5 } Is that the way it''s supposed to be done? --~--~---------~--~----~------------~-------~--~----~ You received this message

As I asked in StackOverflow<http://stackoverflow.com/questions/15127658/hoe-to-get-tag-id-from-a-record-in-form-for/15129741> I think it would be helpful since we can dynamically create javascript code to control each input tag in form helper, what do you think? Or there has already been a solution? -- You received this message because you are subscribed to the Google Groups "Ruby

In Ruby you can add and modify existing classes at will simply by reopening it. The 4 files you mention add functionalities to the InstanceTag class. This is not a redefinition. The best part is that you can do the same ! An easy way to overwrite an existing method or to add new ones is to create a file under you rails application lib directory and put in it the replacement you want to make:

Hi there, I''m trying to override the defaults for form_helper. I can see in action_view/helpers/form_helper.rb: class InstanceTag #:nodoc: include Helpers::TagHelper attr_reader :method_name, :object_name DEFAULT_FIELD_OPTIONS = { "size" => 30 }.freeze unless const_defined?(:DEFAULT_FIELD_OPTIONS) DEFAULT_RADIO_OPTIONS = { }.freeze

Hi, I''ve been prying my way around form helpers and I need to do something very similar to date_select. I was thinking I might be able tailor it to suit my purposes and then came upon InstanceTag.new with a call to_date_select_tag at the end. I can''t find any mention of these anywhere else - can anyone give me any pointers as to what these two things do? thanks dorian -- I do

In Rails 1.2, the interface to InstanceTag#value and #value_before_type_cast changed, and looking through the svn and Trac history, I can''t see why. It appears that every call to #value now passes the same argument (the result of the #object method), which just duplicates what the function did before it took an argument. The reason I bring this up is that the change breaks some of our

I''m trying to read through the code, hoping to find a way to custom style select boxes for a date_select and can''t figure out this code. Any help appreciated: <code> def to_date_tag() defaults = DEFAULT_DATE_OPTIONS.dup date = value(object) || Date.today options = Proc.new { |position| defaults.merge(:prefix =>

Guys, I''ve been chasing a problem with country_select for the past few hours now. My intention was pretty simple...use the following line in a form: <p><label for="country_region">Country</label> <%= f.country_select :country_region, "United States" %></p> However, for the life of me, I couldn''t get it to work. I kept getting

...roc for my fields but the above version of the proc for my form - the above version would change the behaviour of all following fields. Another version would be to redefine InstanceTag.error_wrapping to be empty with the same method (not nice, eighter - same Argument). Is there a nice way to have InstanceTags ignore errors (like :ignore_errors => true) so that i can implement them myself (a trivial problem inside a FormBuilder). I searched the code, but I find no convinient way. Any hints would be much appreciated. Thanks in advance Florian P.S.: Optional question: Is there a plugin that handles fo...

Hi, I''m having some trouble overriding/defining the default_field_options constant without raising a warning. I''ve tried adding the code to do it in an initializer but that produces a warning (because the constant is already frozen), after some googling I found a recommendation to put it in the environment.rb file but that then that throws uninitialized constant ActionView

I want to override the ''tag'' method in ActionView::Helpers::TagHelper to do some generalized error handling similar to the way scaffolding puts a red border around fields that fail validation. I''ve created a file lib/rails_patches/tag_helper.rb which contains the following. module ActionView module Helpers module TagHelper alias_method :orig_tag, :tag

I would like to have a date control on a page and I would like a behavior similar to what you get using date_select with the :include_blank => true option where the first value in the dropdown is "- Month -", "- Day -", or "- Year -" rather than a blank value for the respective month, day, and year select fields. I took a look at the ruby source for

I''m attempting to use the example given in the Rails Recipes book chapter 2, to create a select drop-down using the InPlaceEditor function (modified to be InPlaceSelectEditor. The example given works (a country list drop-down), but I''m attempting to use it to display a list of items generated from an object in another table that is linked to the table that I''m editing.

Why select_date and select_date? I dont understand why having both (backward compat?). I also look that their source are different, one use the InstanceTag and others calls 3 select_(year, month, day) functions.

Hi all, I would like to write some custom helpers like the ones available as form helpers text_field, text_area and the like. My first try was this: custom_helper(obj, meth) ''some_string'' + obj.send(meth) + ''some_other_string'' end Object and method are being passed as symbols like this: custom_helper(:person, :name) and Ruby rightfully complains that

Can someone please help me with this. I have an Images table :- create table images ( id integer unsigned not null auto_increment primary key, image varchar(200) not null default '''' )ENGINE=InnoDB default CHARSET=latin1; And a car table :- create table cars ( id integer unsigned not null auto_increment primary key, user_id integer unsigned not null, title varchar(100) not

Hi everybody, I needed change field error rendering for some forms created with Rail''s form builder. I found solution by changing ActionView::Base::field_error_ proc to own before form and changing it back after form rendered. I don''t like this solution :) It''s not thread-safe (but it''s not so important, nobody really wants it :), but I don''t like

Hi, I''m trying to write a helper for Scriptaculous'' InPlaceCollectionEditor component. I''ve already submitted a patch (http://dev.rubyonrails.org/ticket/4302). This was a drunk patch; it needs a bit of work (Don''t drink & code!). So far I''ve gotten it to work correctly with normal collections, but I want to use it for belongs_to relations as

I have in my view the following: <% 0.upto(@num_performances) do |idx| -%> <%= text_field ''performance'', ''city'', :index => idx, %> <%= text_field ''performance'', ''venue'', :index => idx, %> <% end -%> and in my controller I have: @performance = [Performance.new("city" =>

Hi, I am currently reading the Rails Recipes book and like the chapter on providing your own in_place_editor for enumerations / selects. I understood so far, or I believe that I understood ;-), how to do that for a field that uses values only, like choosing from "red", "black", "green". What I fail to understand is how to chose from associated objects?!