Programmatically getting access to the layout?

Hi !

I am looking into using RadiantCMS in another software. The admins
will manage the content using RadiantCMS, while I will generate views.
Think E-Commerce.

Obviously, I’d like the layouts to be defined only once – DRY. Is
there a pre-defined way to get to the layout and reuse it in regular
Rails views ?

Please note I haven’t dug into the code yet, but since this is
something I need, I would be interested in coding it if need be.

Thanks !

Francois B. wrote:

I am looking into using RadiantCMS in another software. The admins
will manage the content using RadiantCMS, while I will generate views.
Think E-Commerce.

Obviously, I’d like the layouts to be defined only once – DRY. Is
there a pre-defined way to get to the layout and reuse it in regular
Rails views ?

Not at the moment. If you are interested in making this work take a look
at #process on Behavior::Base:

http://dev.radiantcms.org/radiant/browser/trunk/radiant/app/models/behavior.rb

If the software you are creating is radically different from Radiant,
you could just use Radius within your own administration system. Radius
is the library that Radiant uses to process the <r:tag_name /> tags:

http://radius.rubyforge.org


John L.
http://wiseheartdesign.com

Francois
There was some discussion of this a while ago. Andrew H. had
some
useful advise, have a look at this
http://www.ruby-forum.com/topic/71319#new

Harvey
On 18/7/06 14:46, “Francois B.” [email protected]
wrote:

Hi !

2006/7/18, John W. Long [email protected]:

at #process on Behavior::Base:

http://dev.radiantcms.org/radiant/browser/trunk/radiant/app/models/behavior.rb

If the software you are creating is radically different from Radiant,

you could just use Radius within your own administration system. Radius
is
the library that Radiant uses to process the <r:tag_name /> tags:

No, it is

not radically different. I just need a CMS that goes around
the parts that I
code. My first task will be attempting to make
Radiant an Engine or a plugin,
so I can integrate it with my own
application.

I will look at how to get the

layout programmatically.

Thanks !

François

Beausoleil
http://blog.teksol.info/



Radiant mailing

list
[email protected]
http://lists.radiantcms.org/mailman/listinfo
/radiant

This e-mail has been scanned for all viruses by MessageLabs.

This e-mail has been scanned for all viruses by MessageLabs.

2006/7/18, Harvey B. [email protected]:

There was some discussion of this a while ago. Andrew H. had some
useful advise, have a look at this http://www.ruby-forum.com/topic/71319#new

Great, just what I needed.

Bye !

Hi !

2006/7/18, John W. Long [email protected]:

If the software you are creating is radically different from Radiant,
you could just use Radius within your own administration system. Radius
is the library that Radiant uses to process the <r:tag_name /> tags:

No, it is not radically different. I just need a CMS that goes around
the parts that I code. My first task will be attempting to make
Radiant an Engine or a plugin, so I can integrate it with my own
application.

I will look at how to get the layout programmatically.

Thanks !

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs