> 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.
Sure, it is very simple, but a good start. I have tried to integrate the "look and feel" of Radiant as much as possible. Let me clean it up a bit and I will provide an svn link. Like the acts_as_taggable plugin, I don't have any radius tags for it yet, only the backend. I will be getting to those next. >> 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. > > ??? I had two separate plugins, one for the tagging and one for the assets. I ran the tagging migration first. then I tried to run the assets. I believe it didn't run the assets until i changed the migration number from 001 to 002... though now that I think about it, I am not so sure. The lack of feedback on the rake task might have confused me. (I am easily confused, especially hacking in the middle of the night) >> >> 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). > If you moved the Taggable module into it's own namespace, i think we could have basic tagging very easily. I had the admin side part programmed literally in a matter of minutes. The changes need are very small, if you use the plugin. Of course, this doesn't include the work for the Radius tags, but that shouldn't be too hard. Even without using the plugin, it wouldn't be that hard. The plugin provides a lot of functionality, but does has some quirks. It doesn't accept comma separated lists for instance, which makes multiword tags hard. There are a lot of changes floating around on the wiki though. > -- > 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 _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
