On Tue, 2006-01-24 at 23:14 +0100, Andreas Hartmann wrote:
> Michael Wechner wrote:
>
> [...]
>
> >> I'd start with option (2). Concepts like resource type inheritance and
> >> overriding resource types in publications could be discussed,
> >
> > do you see any negative side-effects with this?
>
> Actually I don't know what it would look like. At the moment, "overriding"
> a resource type would just mean to declare an additional resource type
> like "default/xhtml" and maybe reference the schema and samples of the xhtml
> module, so there's no real inheritance. But you could declare additional
> formats which are served by the default publication's sitemap. Maybe
> this isn't such a bad idea.
I would like to make an example how I imagine "different layouts for one
resource type".
The layout types are defined in module.xconf of the resource type as
follows:
<layout-types>
<layout-type>type1</layout-type>
<layout-type>type2</layout-type>
</layout-types>
The type of a document may be specified at creation time and will be
stored in the meta-data.
When a document is rendered, it's the reponsability of the publication
to use the layout-type.
It may ignore it and use page2xhtml-{doctype}.xsl, or it may render the
document with page2xhtml-doctype-{layout-type}.xsl
Andreas, is that similar to your idea, or did I misunderstand you?
Did you want to use the <format> element to define different layouts? If
so, could you please make an example?
Something else: right now, it seems not to be possible to tell a
resource type to use the menu items and the {doctype}2index.xsl of a
different resource type.
Is that correct?
Josias
>
> >> but I'd
> >> rather see the resource type as a black box and apply an additional
> >> transformation inside the publication (e.g., as you already mentioned,
> >> using meta data).
> >
> > well, it's seems to me that this will be a never-ending story, but
> > it's more of guts feeling and maybe one can limit it.
>
> The concept described above is probably a quite clean solution.
> It allows a clear separation between resource type presentation formats
> and publication logic. But it requires to declare an additional
> resource type.
>
> -- Andreas
>
>
> ---------------------------------------------------------------------
> 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]
