similar to: [JOBS] Technical writer familiar with Rails and documenting a RESTful API

Is there some way to format the layout of the fields within a form? I''ve got about 10 fields that I''d like to lay out in a couple of columns. Tried putting them in a table and that didn''t work too good. Any pointers will be very much appreciated. Thanks, Bill -------------- next part -------------- An HTML attachment was scrubbed... URL:

Open-source or commercial. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit

Redbubble is developing a web app where designers, authors, illustrators, musicians and artists can upload their creative work for sale to the Australian market. Redbubble takes care of the logistics ? billing, production, marketing and distribution. We are looking for 2 developers with experience building clean, elegant and usable web applications. Toolset will be Rails, CSS, HTML, and

I''m using bundled_resource, login_engine, and a few other plugins. It appears Rails considers plugins in alphabetic order. Turns out that there is a particular order that will work and alphabetic ain''t it. The login engine must be loaded first. Bundled resource then includes ''application_helper'' and the application helper includes LoginEngine. If

If you want to use rspec-0.9.2 with autotest (ZenTest-3.5.2), you''ll want to read this blog: http://blog.davidchelimsky.net/articles/2007/05/01/rspec-0-9-1-and-autotest-zentest-3-5-2 Enjoy! David

POSTING DATE: JUNE 9, 2011 CLOSING DATE: JUNE 30, 2011, OR UNTIL FILLED The International Food Policy Research Institute (IFPRI) seeks to recruit a Technical Writer into its HarvestChoice team in the Environment and Production Technology Division. This is a one-year, exempt, renewable appointment depending on performance and funding based at IFPRI headquarters in Washington, D.C. HarvestChoice is

I can''t believe I''m back again with another rest question. I did go through the peepcode podcast. I thought though you can have multiple nested resources, is that not true ? I have this set up map.resources :candidates do |candidate| candidate.resources :canbackgrounds candidate.resources :canpositions end I just coded up teh canpositions and now all

I see that there is an integration testing example in the plugin code. What is the thinking about integration specs? Thanks, Steve

For those of you interested in getting a jump on learning about and using the new Story Runner in a Rails app, I''ve added an experimental Rails-Story adapter to trunk. You can see how to use it here: http://pastie.caboo.se/92320 This is PURELY EXPERIMENTAL, however it actually works and will likely not change much in the way that it does work. Happy hacking! David

I got the most current rspec and installed as a plugin. Running rake spec:controllers gives me this error: ignoring attempt to close td with tr I dumped response.body and everything looks fine. Is this a known issue? Nothing in Google about it. Thanks, Steve

There is an assert_difference helper for Test::Unit (you can read about it at http://blog.caboo.se/articles/2006/06/13/a-better- assert_difference and to some it should look familiar -- you know who you are :), so I took a shot at one for rSpec on Rails. class Object def should_be_different(method = nil, difference = nil) return self.should_not_eql(yield) if method.nil?

Given this code (which renders rjs), I''m faced with the fixture- driven way of spec-ing or mocking. How the heck to you mock this so the code at line (2) and (4) work right? I''m still struggling with mocks but it seems like this can be done. Forgive the naivety of this question. 1. def change_quantity 2. @line_item = LineItem.find_by_id(params[:id]) 3. unless

The floating-point expectations allow for an error tolerance. Is there any similar facility for dates? For example, say I have a custom class that handles date/time spans and I want to spec it: context "A DateRange span" do specify "should know when a week ago is :)" do d = DateRange.new d.last_week.should_be_close_to(1.week.ago, 24*60*60) end end The idea

Hi all. I'm looking to change from a standard telephone line to a VoIP phone line at home. I'm looking for recommendations for VoIP providers that I can use with Asterisk. One of the catches is that I often telecommute and sometimes I do some side business; these practices violate many provider's acceptable use policies. So, I need a provider who doesn't care how I use the

I want to use mocks and stubs to test the controller, but am having trouble getting my validation not to trigger. Here''s the code: # spec: Image.stub!(:find).and_return(@image) @image.should_receive(:save!).once.with(:any_args) put :update, :id => @image.id, :category_id => @category.id, :image => {:name => ''test'', :image_number =>

I''m backed off Edge Rails and all the way back to 0.7.2 of rSpec to make my tests pass. The changes to rSpec are coming together fast and furious and they seem too good to pass up. Is there an approved way to upgrade the components in the absence of prebuilt stuff? Every time I''ve tried, I''ve been punished harshly by the Version Conflict Gods. Just asking for

Would it be desirable to have before and after take a spec name as well as :each and :all? Scott

While the spirit of BDD is to spec first and code second, many of us have legacy code. Worse, some of us have legacy code without very good coverage. Recognizing that *I* have such code, I created a script that grinds through your .rb files and creates placeholder specs for each public method. While it is more sensible to spec behavior of code function than of individual methods, this

I am setting up an AR mock object and wanted to sanity check it. My intent is to mix this into all my examples and then override/add methods where necessary. Note that I''ve anticipated three cases for find: find with one numeric argument => object find with :all => Array find with anything else => nil This roughly approximates how ActiveRecord::find works in this case

* Hamcrest-style parameter matchers * Values returned and exceptions raised on consecutive invocations * Yields on consecutive invocations * Multiple yields on single invocation * Invocation dispatch fixed * Deprecated returning result of a Proc -- James. http://blog.floehopper.org