Bob Harner wrote:
On 2/2/06, Doug Chestnut <[EMAIL PROTECTED]> 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, and
{$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.
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
...
This sounds good.
[...]
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.
"Document" should really be "Object" (DocumentBuilder -> ObjectBuilder,
Document -> Object, DefaultDocument -> DefaultObject) and we add
something like getRawURL to Object (to get the .odt url instead of the
.html, or to get the .jpg url instead of the .html)
My knowledge of the api is not to great so I might be way off base here.
--Doug
[...]
-- Andreas
Maybe don't use the term "Object" -- much too vague. "ContentItem" is
better, and other CMS's I know of use that term for each "thing the
CMS manages".
That works, Document is just too descriptive, I wouldn't classify an
image as a document. ContentItem fits :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
