Not possible that I know of. Certainly not good practice even if it were.
What you'd normally use render for in a view is to render partials, which it
sort of looks like you're trying to do...
Am I supposed to use RJS?
... except that you're using link_to_remote which sends an xhr to the server
which, yes, would lead one to believe you're going to render that partial
using RJS.
From the view below, it looks like you're interested in the use of Rails in
healthcare. As an aside, I recently open-sourced my first 'big' Rails app.
It's an app using CCRs for new patient registration. You might find it
interesting. Perhaps even helpful. It's at
http://rubyforge.org/projects/ccredit
Not possible that I know of. Certainly not good practice even if it
were.
What you'd normally use render for in a view is to render partials,
which it
sort of looks like you're trying to do...
... except that you're using link_to_remote which sends an xhr to the
server
which, yes, would lead one to believe you're going to render that
partial
using RJS.
From the view below, it looks like you're interested in the use of Rails
in
healthcare. As an aside, I recently open-sourced my first 'big' Rails
app.
It's an app using CCRs for new patient registration. You might find it
interesting. Perhaps even helpful. It's at
http://rubyforge.org/projects/ccredit
Best regards,
Bill
Well the reason why is to use activescaffold's new action. It takes a
crap on you if you render it's forms, so I was trying access the action
directly.
Well the reason why is to use activescaffold's new action.
It takes a crap on you if you render it's forms, so I was
trying access the action directly.
It's easy to get 'wrapped around the axel' with routes, and especially
nested routes. My personal recommendation is to delete the routes stuff
that's being scaffolded for you, make the app do what you need it to do,
then add back the stuff that _might_ help you make the code base smaller.