Doug Chestnut wrote:
[...]
I'm replacing the fallback:// URL with a call to the fallback
input module, this way the input module does the resolving and
passes a comprehensible URL to Batik.
Thanks :)
No problem :)
The main reason for the commit was to allow shared resources to be
displayed. On giving this some thought though, the shared resources
should really just be a part of the template/skin and should be sized
for the display when created (I guess there are some exceptions to this).
The transition between template/skin-related resources and other resources
is probably quite smooth, I wouldn't handle them in a different way.
In an ideal world, both would be CMS assets and support versioning etc.
This could apply to XSL stylesheets and CSS as well.
Do we want to incur the extra processing for shared resources?
IMO that should be up to the publication. At the moment, the default pub
adds the ?lenya.module=svg to all image requests using an XSLT, which is
simple and just works. But other publications might use the SVG module only
for images that were uploaded using a special mechanism. In fact, the
pipelines are caching and therefore performance is probably not really an
issue.
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}/..."/>
-- 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]
