Ejemplo:

map.resources :users, :shallow => true do |user|
  user.resources :posts
end

* GET /users/1/posts (mapea a la acción PostsController#index action como siempre)
se agrega la ruta nombrada "user_posts" como siempre.

Lo nuevo:

* GET /posts/2 (mapea a la acción PostsController#show como si no sería anidada)
Adicionalmente, se agrega también la ruta nombrada "post".

Ah, quando vai ser mesmo? Sábado, dia 06/09/2008, às 15:00, no site http://www.treinatom.com.br/cafe-com-o-tom.

Quanto custa? Seu tempo e paciência. :P

Espero por vocês!

Nailing the worst few( -24 seconds out of 174 ):
 I used spec ./spec -f profile to get me the 10 most time taking specs. And changed before(:each) to before(:all). In RSpec world, theoretically, each spec is supposed to validate one behavior. So specs on there own, were pretty lean, doing things like asserting sensible defaulting, correct options for SQL query, or verifying result of a query etc... The data setup was happening in the before block, and everyone was using the same data. Nested describe(s) were adding to the before(s)... 
On these low performing specs, before(s) were pretty bloated... so making them before(:all) reduced the execution time by (before block time)*(number of specs).....
 Practicality beats purity.... I should not have done this... but it gave me some 24 seconds of boost...(when done for 40 specs)... so i took it..... BUT it left the specs vulnerable to side effects(hence not infinitely scalable.... more you do it... lesser the benefit, and more the miseries.....). I had to put some extra effort to fix the side effects caused by the same entities getting shared across multiple specs... Not the best solution in the galaxy.... but whatever works..... 

Parallelization..... The bad boy( -78 seconds out of 174 ):
 The thought process behind this one was, that a lot of time is wasted on a synchronized process, when it gets IO bound. Writing to the db socket, reading from it... reading files...(ruby files, haml templates, spec files themselves... rails code-base files....) you name it... 
But wait... bringing Ruby Threads in, is gonna be NO better either.... because ruby doesn't have native threads...
Old friend to rescue..... I used fork.... 
The app has specs segregated in sub-directories...(spec -> controllers, spec -> views, spec -> models, spec -> helpers, spec -> lib) etc.... I spawned one process per sub-directory....
I wrote this crude rake task(http://pastie.org/266452), which did the trick.... 
I defined more environments for each sub-spec set in the database.yml file... which had different database names(to avoid deadlocks @ the DB level)....  now the database.yml looks like this.... (http://pastie.org/266456)
Thats it..... now i just run rake foo, which does the trick....
Reporting is pretty insane... because it has to be inspected it visually.... but thats fairly ok... because we are planning to use this only for developers doing quick sanity check before pushing to the source control.... continuous integration box is still using the conventional single process thing(rake spec).
Im sure reporting can be tweaked to figure out passing or failing of specs.... and then the parallelized version can be used on the continuous integration box as well...... Wether im gonna do it or not... depends on how much time i get tomorrow... ;-)

Hope this was useful......

Hello all Rubists!!!

After a much needed summer hiatus, the Ruby on Rails Project Night 'community' is set to gather again on Friday September 19th at a NEW location: the Rich Media Institute!

As some of you may realize, this is a new evening for us. I don't intend on having our get togethers on Friday, but September 19th is very special.

I am pleased to have James Robertson, Cincom Smalltalk Product Evangelist, joining us on his 'Canadian Tour' to look at Seaside and WebVelocity:

WebVeocity is a new Smalltalk Development Environment that is oriented around Seaside for Web Development and Glorp for Object/Relatonal Mapping. Come and see how WebVelocity re-targets the Smalltalk development experience into the Web Browser and simplifies the challenge of learning a new environment for newcomers. We'll even build an entire application using Active Record and Scaffolding during the presentation, with minimal programming. If you're a fan of Ruby on Rails, you need to come out and see this presentation!

We will also be joined by local Ruby on Rails developer Paul Doerwald, who will examine insights gained from working with ActiveRecord validation internals.

As always, it is the audience - and their participation - that really makes these events great; so I hope you can all join us for this special opportunity. These FREE presentations will take place on September 19th starting at 6pm until approx 7:30pm at the Rich Media Institute.

Please email me at corecorina@hotmail.com or leave a comment below if you are attending - space is limited, please RSVP!

Recomendo para quem tem interesse de conhecer esse magnifico S.O., mas não recomendo se você pretende ter estabilidade.

Após ocorrer alguns problemas.. e algumas reinstalações.. voltei para o meu querido Debian.

Mas como fazer para programar rails sem o TextMate? vamos adaptar o Gedit para ficar com a aparência o mais próximo possível com o TextMate.

Aqui vai algumas dicas simples:

para instalar é o de sempre

#apt-get install gedit

Digite gedit no console para abrir o programa.

Clique em editar -> preferências:

Na aba "Visualização" marque

(X) Habilitar quebra de texto;
(X) Não dividir uma palavra em duas linhas;
(X) Mostrar números de linha;
(X) Destacar linha atual;
(X) Destacar parênteses correspondentes;

Na aba "Editor" marque:

Largura das tabulações = 2

(X) Habilitar recuo automático;
(X) Criar uma cópia de backup dos arquivos antes de salvar;
(X) Salvar arquivos automaticamente a cadas 5 minutos;

Na aba "Fontes e Cores"

Em esquema de Cores recomendo o tema Clássico ou o Oblivion (Na minha opinião Oblivion é melhor :D ), mas isso vai da preferência de cada um.

Na aba "Plug-ins" marque:

(X) Estatísticas do Documento;
(X) Inserir Data/Hora;
(X) Modelines;
(X) Painel de Navegador de Arquivos;
(X) Trechos;
(X) Verificador Ortográfico;

Para exibir o painel lateral basta pressionar F9.

No painel lateral não utilize "Documentos" e sim "Navegador de arquivos"

Créditos do artigo: Marcos Miras

## ProductGroup have this:

class ProductGroup < ActiveRecord::Base
set_primary_key "id"
has_and_belongs_to_many :products
validates_uniqueness_of :id
def self.gen_new_id() # {{{
counter = 1001
groups = ProductGroup.find :all
if groups.nil? || groups.empty?
return counter
end

all_ids = groups.collect{|g| g.id}
unless all_ids.nil?
while all_ids.include?(counter)
counter = counter+1
end
end
return counter
end # }}}
...

## migration:

create_table :product_groups, :id => false do |t|
t.integer :id, :nil => false, :key => true
t.string :name
t.string :identifier
t.string :type_is
t.timestamps
end


doing rake db:drop:all && rake db:create:all && rake db:migrate. then jumping into ./script/console


Loading development environment (Rails 2.1.0)
>> f = ProductGroup.find_or_create_by_identifier('first')
=> #
>> f.id = ProductGroup.gen_new_id
=> 1001
>> f.save
=> true
>> f.id
=> 1001
>> ProductGroup.find :all
=> [#]
>> s = ProductGroup.find_or_create_by_identifier('second')
=> #
>> s.id = ProductGroup.gen_new_id
=> 1001
>> s.save
=> true
>> s.id
=> 1001
>> ProductGroup.find(:all).collect{|g| "#{g.identifier} has id:(#{g.id})" }
=> ["first has id:()", "second has id:(1001)"]
>> ProductGroup.destroy_all
=> [#, #]
>> ProductGroup.find :all
=> [#]
>> ProductGroup.delete_all
=> 1
>>