Radiant Plugins Directory

Everyone,

After users get Radiant up and running, they will probably want to
create plugins, I think the vendor/plugins directory should only be used
for the core product. My though is to have a RAILS_ROOT/extras
directory where users can place their own plugins or third-party
plugins.

Do you agree? I created a radiant_loader plugin that sits in the
vendor/plugins directory that loads plugins from RAILS_ROOT/extras
directory. If anyone thinks this is a good idea I will package it up
and create a [research] ticket.

cheers,

scott


What’s an Intel chip doing in a Mac? A whole lor more that it’s ever
done in a PC.

My Digital Life - http://scottwalter.com/blog
Pro:Blog - http://scottwalter.com/problog
Snippets - http://snippets.scottwalter.com

Scott W. wrote:

After users get Radiant up and running, they will probably want to create plugins, I think the vendor/plugins directory should only be used for the core product. My though is to have a RAILS_ROOT/extras directory where users can place their own plugins or third-party plugins.

Do you agree? I created a radiant_loader plugin that sits in the vendor/plugins directory that loads plugins from RAILS_ROOT/extras directory. If anyone thinks this is a good idea I will package it up and create a [research] ticket.

I initially had the same idea, but vetoed it because it didn’t work with
the standard script/plugin script. Would your radiant_loader plugin
handle this case? If it does I’d prefer that the directory be
RAILS_ROOT/plugins/.


John L.
http://wiseheartdesign.com

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