[Radiant] Asset Manager Mephisto Style => Plugin system

dror tirosh dtirosh at gmail.com
Fri Sep 1 17:36:59 CDT 2006


Hey Nicholas,
Look at the page_part_type in the trac system for an implementation of
something similar to what you are talking about.
The only thing is that this doesn't come instead of behaviors, it is a
compliment, and they work together very well. For example an event page_part
allows you to choose a date ( instead of the text box ) and then an event
behavior uses those dates to create tags for coming and past events.
I'm using it in a project were my writers can hardly use word, I have
created a rich text page_part based on fckeditor, an event page_part, an
attachment page_part and a multiple uploads page part (this one loads images
in the background, ajax like) that also shows a gallery.
There is an attachment page_part in the works, but there is some problem
with act_as_taggable not working in development environment, which makes it
realy hard to debug anything else.
Dror

On 9/1/06, Nicholas Mulder [Mulder Consulting] <nick at mulderconsulting.ca>
wrote:
>
> > Once we have a robust plugin system going I would love to see someone
> > create an asset management solution similar to Mephisto's. I'm not sure
> > if buckets trump the idea for attachments, but it is definitely causing
> > me to rethink my previous ideas about assets.
>
> > That would probably be up the the plugin authors (and the Mephisto
> > people). But I do think it would be great if code could be shared.
>
>
> Ya, their asset management is really good.  So simple.  So simple we all
> could have thought of it.  But we didnt.... Rick and Justin did.  Now we
> should ask them if they will play nice with us...
>
> About the plugins.  I know it is on the road map to make a really cool
> plugin system.  I dropped a message about this a week or so ago, and got
> no answer.
>
> Is there room in the plugin system for  some hooks into the admin
> interface??  What would be really sweet is to be able to define a page
> part as a behavior and have its interface change a bit.  Think about a
> gallery part where instead of a great big text box, the user could add
> descriptions to their sub-folders/albums of photo's.  Or in a menu part
> where you could define and reorder menu items and such.  Hooking into
> those page parts in the admin interface might not be too 'evil'... Would
> need to be able to define a form in radius tags, then parse the result
> of that form(s) in the behavior.
>
> Thoughts?
>
> Nicholas Mulder
>
> Mulder Consulting
> 905 658 5641
> nick at mulderconsulting.ca <mailto:nick at mulderconsulting.ca>
>
>
>
> _______________________________________________
> Radiant mailing list
> Radiant at lists.radiantcms.org
> http://lists.radiantcms.org/mailman/listinfo/radiant
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.radiantcms.org/pipermail/radiant/attachments/20060901/666e2361/attachment.html


More information about the Radiant mailing list