This project is read-only.

Small question concerning the futur media manager

Topics: Customizing Orchard
Mar 20, 2013 at 2:48 PM

I had a look on the last meeting video where Sebastien was presenting its progress on the new media manager, looks great and promissing.
But it raised a question: as far as I understand every media content will be implemented as a part (we see image part in demo), and as I have understood that each part instance belong to only one content item, how could we share these media parts in our own content items (and potentially we use often the same image in several content items like pages)?

This in relation with the fact that there is actually a 1:n relationship between a part and a content item.


PS: should be nice to have a place to comment the last meeting.
Mar 20, 2013 at 5:50 PM
Each media will be a content item. It will live it's own life and other content items can point to it, or just use it, query it, display it. And because it's a content item you can edit its properties, or alter its content type.
Mar 20, 2013 at 6:21 PM
And if in several pages I want to insert the same image in body, just as we are doing with the html editor ?
I suppose the answer is in this case we will access directly the image, not the content item 'surrounding' it ?
Or will we include in our html body a kind of iframe where the contentype will display the image (or the sound, the video, pdf, whetever is inside ? Is it the idea ?
Mar 20, 2013 at 6:44 PM
When you pick the image (content item) from tinymce, it will inject an <img> tag. I would like to provide custom filters in the image picker, so you can decide how to actually render it in this context, like a link to the actual image, or a popup, or the image with its properties as data attributes, or whatever you want (extensible).
Mar 20, 2013 at 6:54 PM
Very interesting this idea of injecting from one content item to another some kind of formatted html.