Keith Bingman wrote:
> I just want to second this, the extensions are very well thought out and 
> pretty easy to use even in their very raw state. I have a very simple 
> assets management system (based on acts_as_attachment) that took maybe a 
> few hours to set up. Most of that was making sure that the views 
> integrated nicely into Radiant.

Would you be willing to share that with the rest of us? I'd like to have 
an assets extension in the repository when the next release becomes 
available.

> I found another small gotcha with the migrations. If you have more than 
> one extension, you do have to make sure that the migrations are properly 
> numbered.

More than one extension? Please elaborate.

> 2 "No. !" doesn't work.

???

> And the rake task provides no 
> feedback, I have gotten used to the new Rake  task telling me what it is 
> doing. Not a biggie, but it would be nice.
> 
> All in all, this is a really great addition to Radiant and vastly 
> increases its value, at least to me. I can't wait until an official 
> release.
> 
> One sort of funny note: I tried to add tagging to Radiant while I was at 
> it.

I'd love to see the implementation for this as well.

> I used the acts_as_taggable plugin (not the Gem) from DHH and only 
> had to add one line to the Page model and one line in the control, plus 
> a very small change in the views. It worked great. Except that it 
> totally broke the Radius tagging system and the front end rendered nothing.

That's probably because Radiant now has a "Taggable" module for Radius 
tags. Perhaps we should move it into the Radiant namespace 
(Radiant::Taggable).

--
John Long
http://wiseheartdesign.com
_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to