DeconStudio wrote:
> But in the example that you posted with the SamplePage class -- I am
> assuming I would make my own class as a subclass of page and then follow the
> instructions for loading it as an extension from the Radiant docs.
Creating that class and the extension is a step in the right
direction. After that you can create pages that have the type of your
new class.
> Then calling it in the theme with something like this:
>
> <% form_remote_tag :url => { :action => :SamplePage, :id => form_button } do
> %>
> <%= submit_tag "Email Me" %>
> <% end %>
Pages don't support ActionView helpers. You will have to convert
everything to "real" HTML/Javascript.
> But replacing the action with whatever Class I made, like FormDisplay let's
> say.
No a URL to a page with the type of your new page class.
> And then change the appropriate Element.update calls to whatever RJS actions
> I want to take on the element within the Body of the document, which would
> be the HTML I have loaded into that page's body section through Radiant's
> backend administration.
Hmm, I don't think you can use ActionController functions such as
render in a Page's process method. So no RJS, again pure Javascript
only, as in the example.
> Am I close? :)
Just a little.
You are probably better off writing a separate controller that handles
your requests instead of creating a derived page class.
Cheers,
Oliver
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
