Ber Kessels wrote:
I think it is important to know the audience and use. * Images as node == for galleries. 99% for photo's. * Images in any node == blogs, news, articles, manuals. Not nessecarily photo's, most just for "spice". Blogs, news, forum posts don't need power of placement of inline images (aka handled trough the theme) while manuals and articles will need this.
We should consider to include both in core, with a clear line between them, and re-use of code.
Hi, I'm new here, but here's my take on this discussion: Frankly I feel all images should be a node. Even if an image is included in a content node just for spice or illustration, very likely these images could be thumbnails that link to a larger version. Same story if I include a true photo in a content node, it will most likely also be a thumbnail linking to the full image node. So I see no reason to build two frameworks for handling images when one will do. Why the arbitrary separation? They should all be nodes, and if we need organizational separation of "photos-available-in-galleries" vs "spice-and-illustration-images", that should be handled via taxonomy, and only the desired terms made available in menus/galleries. Sebastian