hi all! FYI, this is a bit of a cross post to another list as well... but I could use a little help. You can read the original post here: http://groups.google.com/group/resourcespace/t/edd2803216b351de
I have been working with an opensource asset manager called ResourceSpace www.montala.net/resourcespace.php It's PHP based and was originally built for OxFam. It's slick and very usable.... one of the better asset managers I've ever used for web big teams and highly customizable to boot. It uses a "collections" & "themes" method of organizing assets (assets being images, audio, video, pdf's, or whatever you configure in the asset manager). All that said. I've been doing quite a bit of mashups with my *big* Radiant project and this asset manager in hand with wymeditor is a great combo. I have a fairly decent working barebones version linked at the bottom of the this post and some major updates I'm hammering out this week. The biggest update I am working on so far has been creating an extension to publish podcasts & audio / video streams via Radiant with the management of the assets themselves done through RS; so the ResourceSpace install doubles as the media manager and assets server. This integrates very well into "blog-like" and straight "article-style" sections of our site where I found it was beneficial to be able to hyperlink directly to a media resource on the assets server, with the end goal being that the user almost never has to type a URL for anything. Yet an interesting problem has arised .... As stated previously I am running RadiantCMS, which runs on Rails; and I am mashing up with RS through simple iframes and Julien Lecomte's crossframe method to get the frames talking. http://www.julienlecomte.net/blog/2007/11/31/ In prior tests I had used a simple onclick function and $("input.wym_src").val($(this).attr('src')); to insert the image's source into the wymeditor src field. This basic method will work on most other editors with a little hacking. And this should suffice for installations which are running on the same exact domain as the CMS ( ie www.mydomain.com/cms/ & www.mydomain.com/assets/ ); however, in our scenario I have Radiant running on one subdomain and RS running on a different subdomain which creates a cross-domain scripting issue unfortunately. Yet using cross-frame & a proxy this *should* not be a problem. All works fine on the initial collections.php page presented to the user when entering the image insertion window, however there is something weird going on when the user selects a different collection that breaks the ability to send the image's source URL to the receiving input field in the parent frame. I believe it has to do with the URL parsing and the fact that Julien's method is based on URL fragmentation. Just an idea. Take a look at the screenshot's I have linked to below to get the big picture of what this all means. http://media.themetnet.org/Picture15.png <-- our friend the editor http://media.themetnet.org/Picture16.png <-- selecting an image from a collection list http://media.themetnet.org/Picture17.png <--- YAY it works http://media.themetnet.org/Picture18.png <-- selecting a new collection http://media.themetnet.org/Picture19.png <-- selected a new collection / no good... bad cop.. no donut.. http://media.themetnet.org/Picture20.png <--- no pic I am including a link to a down and dirty version of this mashup which requires: RadiantCMS with the Wymeditor filter installed. ResourceSpace. Copy the files into their corresponding folders on both sites and edit the following files with proper URLs for your sites (you can search for www.myradiantsite.com & www.myresourcespacesite.com in the source): jquery.wymeditor.js collections_wymeditor.php (which resides alongside collections.php, so don't delete collections.php) Source: http://media.themetnet.org/wymeditor_radiant_resourcespace_mashup_0.1.zip You should be able to get the basic idea of how to integrate RS into other CMSs/ editors from this stripped down code. If anyone can help with the cross-frame issue I seem to be having that would be much appreciated. Cheers all; Ash _______________________________________________ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
