On Dec 11, 8:56 pm, real_jax <[EMAIL PROTECTED]> wrote: > > On Dec 11, 2:46 am, real_jax <[EMAIL PROTECTED]> wrote: > >> When creating HTML pages, it took me while before I understood how to use > >> uploaded images in the body part. You need to first have a relationship > >> and > >> have an image selected in the associated media. (why are those items > >> draggable there? > > > Because many people -- especially in larger installations -- do not > > allow contributors to place images inline within their content. > > Instead they prefer to have images positioned based on the template > > chosen to render the page. You can order the images because often the > > order of images has considerable significance for the design of the > > template. > > Are you sure that 'many people' should not be 'some people' instead ? Are > you sure you are not forcing the majority of your users to think along the > way that only some require? > > Anyway, my intention was to show that things might be confusing. I Know it > was confusing to me.
The UI issue is relatively complex (note we refer to images but the same is true for links, files and other content types). We have the following requirements: a) associate images with the page but *not* embed them in a rich text editor b) these associated images need to be specifically ordered c) allow embedding images (optional for install) into the editor drawn from a library d) allow images to be added to a global media library in the context of the content item being edited e) library can run to thousands of images so provide search across library f) prevent accidental deletion of images in a global library that are required by a content item Given these real world requirements, we need to maintain an array of associated media assets bound to the content item. We need a rich library interface that goes outside of what is possible within the context of the rich text editors interface. That is why we require images to be "added" or associated to a content item, and then optionally embedded into the rich text editor. After several years of reflection and feedback from real users it is the most flexible, and scalable approach we have devised thus far. Of course the UI can be improved -- and we aim to do so every revision. But there is considerable method to the madness. -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev?hl=en -~----------~----~----~----~------~----~------~--~---
