Thanks, Nate.  So, to clarify because I'm dense:
1. I need to build an extension
2. The archives/docs should show me how.

Will I need to learn git to do this?

As you may suspect, my end goal is to get either the content alone or
the stylized content (not sure which) from Radiant and display it in
Flex via AMF.  I intend to do my own styling in Flex, but I would like
any HTML markup that the user may have entered.  

Does this seem feasible?  


-----Original Message-----
[mailto:[EMAIL PROTECTED] On Behalf Of Nate Turnage
Sent: Wednesday, October 08, 2008 9:31 AM
Subject: Re: [Radiant] Radiant and RubyAmf

On Wed, Oct 8, 2008 at 10:13 AM, Marcus Blankenship

> Hello all,
> Has anyone used Radiant and RubyAmf together?  I was hoping to get 
> Radiant content in AMF format with this module, but had no luck.  It 
> seems to cause errors in the routes.rb file.

I don't think anyone has ever done this before, but I, for one, am very
interested in how you get it working. I didn't even know RubyAmf

> Also, and I'm sure this is a dumb question, but why is there no App 
> folder in Radiant?

Radiant is primarily used as a gem. There is no App folder because you
don't modify the Radiant app. If you want to create additional Rails
classes, you do it by building an extention. They sit in the
vendor/extensions folder. To make use of the layouts generated by
Radiant you use the share_layouts extension on github. If you search the
archives from about 1-2 months ago somebody (Sean?) wrote a quick how-to
on using share_layouts.

If you have any specific questions when you start building your
extension, there are plenty of people on the list that can help.

Radiant mailing list
Radiant mailing list

Reply via email to