Re: images module

[Andreas Hartmann]

Doug Chestnut wrote:

Andreas Hartmann wrote:

Doug Chestnut wrote:

Andreas Hartmann wrote:

[...]

A random thought:

We could consider an "images" module, which offers the SVG functionality

and image upload usecases. With the new possibility to use a module URL

prefix, this could be the starting point of a centralized asset management

system.

<img src="{$contextprefix}/images/{$pubId}/..."/>

I like it, but why would we need .../images/... in the path. We don't have .../documents/... in the paths for our documents.

That's the URL prefix to call the module. I called it "images"
instead of "image" to make the URL look nice.

cool
so {$contextprefix}/images/{$pubID}/..."/> would give you the image,

Yes, though we probably have to support image URLs in the publication
itself. Many users won't want a special proxy setting for the images.
But these URLs can be backed up by internal redirects:

$pub/sitemap.xmap:

<map:match pattern="**.png">
  <map:redirect-to uri="cocoon://modules/images/{1}.png"/>
</map:match>

{$contextprefix}/{$pubID}/{$area}/... could give you a page with the image on it?

or in the case of an asset

{$contextprefix}/{$pubID}/{$area}/... could give you a page with the assets metadata, and a link to the raw asset.

Yes, for example. These pages could be generated by the module as well
and included in the publication's pipeline for styling.


-- Andreas


--
Andreas Hartmann
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com                      http://lenya.apache.org
[EMAIL PROTECTED]                     [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]