search for: select_list

...me="PaymentDesc", @value=""> #<WWW::Mechanize::Field:0xb7c64014 @name="PaymentDescFrench", @value=""> #<WWW::Mechanize::SelectList:0xb6f87314 @name="listCatg0", @options= [#<WWW::Mechanize::Option:0xb6f7a6f0 @select_list=#<WWW::Mechanize::SelectList:0xb6f87314 ...>, @selected=false, @text="W\344hlen Sie...", @value="">, #<WWW::Mechanize::Option:0xb6f7a1c8 @select_list=#<WWW::Mechanize::SelectList:0xb6f87314 ...>, @selected=false,...

...= TRUE)' and put "browser()" at the beginning of the onOK body (e.g. in Vim run <<:g/onOK/put ='browser()'>>). That is, transform onOK <- function() { res <- 1L + as.integer(tkcurselection(box)) cat("res is: ", res) ans.select_list <<- choices[res] tkgrab.release(dlg) tkdestroy(dlg) } to: onOK <- function() { browser() res <- 1L + as.integer(tkcurselection(box)) cat("res is: ", res) ans.select_list <<- choices[res] tkgrab.release(dlg...

I have a select list for a boolean column in postgresql in the ''model'' ... YES_NO = [ [ "Yes", "1" ], [ "No", "0" ] ].freeze in the ''view code'' ... <%= options = [[''Accepted?'', '''']] + Placement::YES_NO select("placement", "accepted",

I am curious what you find is good and bad MVC design. Let''s use the find and find_by_sql methods as examples. Currently I have these spread out all over the place... View: here I have some find methods when I am for example populating a select list with choices in a form. Controller: here I have the simpler find methods. Model: here I have the more complicated find methods (usually

Hi everyone! Im trying to install mechanizer from http://github.com/tenderlove/mechanize. I`ve clone the project into /tmp folder. When I do rake inside the folder /tmp/mechanizer it gives me this error: mac159180:mechanize renatosis$ rake (in /private/tmp/mechanize) /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -w -Ilib:bin:test:. -e ''require "rubygems";