search for: rorti

When a validates_asssociated fails... I get something like Address is invalid is there a way, preferably on a per-association basis to have the error messaage include the actual error like Zipcode is too long (max is 10 characters) _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org

Quick question - how come the function.prototype.bind doesn''t allow for return values? Am I missing some basic understanding of how this works? I searched and couldn''t find an answer. Specifically, I''m binding an object method to an existing form''s onSubmit, but it still actually submits the form, refreshing the page - which is not what I want. If change

Thomas, currently the script.aculo.us scripts have some workarounds for Safari that should be extended to more generally cover all khtml-based browsers, Konqueror in particular. In prototype.js, there is a workaround for an addEventListener bug that affects Konqueror as well as Safari, controls.js has a similar workaround, and the special case in dragdrop.js doesn''t hurt anyway. In

Recently, I''ve started to write unit tests for some of my scripts. In general,it''s no worse in JavaScript than in Ruby or Java. I didn''t have the courage to try Selenium, but had a look at JsUnit. Unfortunately, in Konqueror it produces unfathomable errors and in Firefox it is slow beyond imagination. Anyway, writing tests for functions that are computational or

Currently, pages generated by Rails tend to be sprinkled with JavaScript. This happens, because the various helper methods work only locally and simply append to the output. In order to hide the JavaScript away, rendering would probably have to be changed. A way I can think of is that a page-specific script is included in the head of the document and JavaScript code is not written to the

I have several tables for enumerations. They all have the same content: id, name, position. I''d like to avoid the tedious work of defining a class for each one explicitly. Not least, in order to avoid clutter in the model directory. Here''s what I''ve come up with: class EnumRecord < ActiveRecord::Base def self.define_enums(*enums) enums.each do |spec|

Ah - thanks Michael. Event.stop is precisely what I was looking for. I can just grab the event object inside the handler that I registered previously and pass it to an Event.stop call, and get exactly what I want. Thanks, Rahul Date: Tue, 2 Aug 2005 16:08:20 +0200 From: Markus Joschko <markus.joschko@gmail.com> Subject: Re: [Rails-spinoffs] Re: function.prototype.bind

It''s awfully quiet in here... So here''s another bunch of scripts that are heavily inspired by Prototype.js and useful in conjunction with Rails http://www.schuerig.de/michael/javascript/ Please have a look... at the code. There''s nothing visual about the scripts, I happily leave that to Thomas. Michael -- Michael Schuerig Airtight arguments have

My application is built on Rails and MySQL. It will only be accepting US formatted dates as input, however both Rails and MySQL are oriented around ISO the format. I know I can convert a good portion of the entries using ParseDate::parsedate but it does not appear this is how the conversion is taking place when data is being transferred from the params hash into model members. Say I have a field

I''ve noticed that using several TimedObservers (prototype.js) on a page to watch for changes to text fields (haven''t tried forms) can have a non-negligible effect on the CPU cycles used by the browser process. Nothing dramatic, to be sure, but unnecessary. Autocompleter.Base (controls.js) follows a smarter strategy to watch for changes. Currently this functionality is tied

Hello everyone, It seems that the answer to my question should be obvious, but I''ve not yet found a way to do what I want. Any advice on the best method would be greatly appreciated. Have the following database table: CREATE TABLE datasets ( id int not null auto increment, name varchar not null, value varchar not null, year varchar not null, state

Is there any reason to avoid using postgresql for small web apps? That is, is it''s overhead so large that the lighter MySQL will work substantially better for small apps on small machines? Or are they very similar in performance and configuration? I''ve used MySQL but postgresql has its appeals and I''m wondering if I need to keep MySQL around at all. On the other