I've got a number of possibly semi-complex forms to create that will be
part of a content management system (in this case, Typo3). The CMS-provided
form tools are not really up to the task.
The CMS does however allow reasonably arbitrary php inclusion onto parts
of pages, and we can write the forms in php if need be.
I was pondering whether or not it would be reasonably simple to leverage
rails here and author the forms in that instead.
Just curious if anyone has any thoughts on that?
The approaches that crossed my mind:
1) Hook things up so that rails outputs html into a Typo3 content element. This
way, the html will be wrapped up in the CMS framing and styling and so on.
Not sure how to plumb this together though, and it strikes me as likely
clumsy and not particularly straightforward to maintain in the long run.
Plus, we have to be sure to get the form handling action output plumbed
up correctly as well.
2) Have the forms actually be outside-the-cms pages that in the end redirect
back to a CMS page depending on what the form handler decides.
The issue on this one would be keeping the styling in sync with the CMS.
Is there a fairly straightforward way to have a rails app use "foreign"
css? Is hardcoding the css path into application.rhtml (or one of its
included partials) the best way to go about this? Am I betraying my lack of
recent rails experience by saying "application.rhtml"? :) It's been
a while since I've played with rails...)
Thanks for any thoughts. Just pondering at this point, and in the end
it may not be worth doing over the php route unless there's a friction-free
dead easy way to go.
-glenn
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
