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.

Does it make sense to have an "asset" module for generic asset
management functionality, and separate the actual asset resource
types from this module, using plug-in-like interfaces?
We could use a default resource type for assets which are
not handled in a specific way.

modules/
  assets            - asset management classes + usecases
  images            - image resource types, svg, ...
  attachment        - generic attachment resource type
  flash             - flash resource type
  ...


We could add an image module (resource type), which treats an image as any other resource (xhtml, homepage, opendoc, image, ...) would be treated.

Yes, this sounds like a good idea.


We would have to add xhtml:img/@src to the linkRewritingTransformer, but the link rewriting needs to have this configurability anyway.

Yes, that's true.

IMO a major problem is the DocumentBuilder. Unless we can get rid of
it (that would be great), it has to match image URLs as well.


Images could just have a nav visibility of false. I guess the biggest change would be the addlink usecase. We could make it much more robust by allowing others to link to any images in the pub (other pubs as well?).

That sounds good.

-- 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]

Reply via email to