Do they belong to you? Claim these comments.
Oshoma Momoh
Is this you? Claim Profile »
1 year ago
in Introducing resource_controller: Focus on what makes your controller special. on James on Software
The URL helpers in helpers.rb and urligence seem to assume the object's class name is always the correct name to use within the URL path. What is the best way to override this with a custom resource name?
Example: We have a model SpecialPost, and a controller SpecialPostsController. We want to expose paths such as, "/user/1/posts/", rather than "/user/1/special_posts/". So in routes.rb we do:
map.resources :users do |user|
user.resources :posts, :controller => 'special_posts', :name_prefix => 'user_'
end
Example: We have a model SpecialPost, and a controller SpecialPostsController. We want to expose paths such as, "/user/1/posts/", rather than "/user/1/special_posts/". So in routes.rb we do:
map.resources :users do |user|
user.resources :posts, :controller => 'special_posts', :name_prefix => 'user_'
end
1 year ago
in Introducing resource_controller: Focus on what makes your controller special. on James on Software
The URL helpers in helpers.rb and urligence seem to assume the object's class name is always the correct name to use within the URL path. What is the best way to override this with a custom resource name?
Example: We have a model SpecialPost, and a controller SpecialPostsController. We want to expose paths such as, "/user/1/posts/", rather than "/user/1/special_posts/". So in routes.rb we do:
map.resources :users do |user|
user.resources :posts, :controller => 'special_posts', :name_prefix => 'user_'
end
Example: We have a model SpecialPost, and a controller SpecialPostsController. We want to expose paths such as, "/user/1/posts/", rather than "/user/1/special_posts/". So in routes.rb we do:
map.resources :users do |user|
user.resources :posts, :controller => 'special_posts', :name_prefix => 'user_'
end
3 years ago
in a week in the world of robert scoble on Scobleizer
Big shoes to fill you did it well, Bubba. Great hearing your voice shine through. I'll track you on your Space.
3 years ago
in Software, patents and innovation on Mathew's comments
The patent problem is indeed vexing, and part of a broader and growing class of problems I label as "IP squatting". The thicket is easy to see. What's hard is getting out of it.
One possible partial solution is to force patent owners to implement within a reasonable time or yield their hold on an IP claim. Of course that has its drawbacks too; for instance, what if you're a great inventor but not a good implementor? On the whole, though, it feels one step closer to a fix.
One possible partial solution is to force patent owners to implement within a reasonable time or yield their hold on an IP claim. Of course that has its drawbacks too; for instance, what if you're a great inventor but not a good implementor? On the whole, though, it feels one step closer to a fix.