Just checking my understanding of the purpose of the functions
mentioned in this thread.

1. Is the purpose to have multiple sitetrees based on selection
criteria (possibly fields within documents)?
2.  Or is the purpose to have Category nodes in the navigation?  A
Category node opens to display more Resources in the navigation
without changing the current page.

#1 is handled in 1.3, although the administration functions for
editing structures have not been implemented yet.
#2 could be added easily to 1.3, but I had not designed for it because
experience/research suggests people expect a new page to open when
clicking navigation entries.  Allowing some entries to expand menus
without changing the current page leads to an inconsistent experience.
 I have been involved with many designs including this functionality;
all removed this functionality later due to confusion and complaints.

solprovider


On 3/3/08, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
> Hi Jürgen,
>  Jürgen Ragaller schrieb:
> > Hi Andreas
>  > Over the weekend I was working on a web-sitemap module and came across a
>  > similar problem:
>  >
>  > The goal is to hide documents from the sitemap using a "visible in
>  > sitemap (true | false)" metadata field.
>  >
>  > Now I am thinking about using the possibiliy to call lenyas java method
>  > to read metadata from the within the xsl that builds the web-sitemap
>  > (using xalans way to call java) - uuid / pub-id and area are known when
>  > walking through the sitetree xml so it should work...
>
> I guess this will be quite difficult, since you can't access the current
>  session and document factory from the XSLT. Have you considered the
>  MetaDataTransformer?
>
>  The first stylesheet would insert meta data query tags:
>  <meta:value element="visibleInSitemap"
>    ns="http://yourproject.org/lenya/sitemap/1.0";
>    default="true"
>    uuid="{$uuid}"
>    lang="{$language}"/>
>
>  After this XSLT you apply the meta data transformer, and a subsequent
>  XSLT removes the hidden nodes.
>
>  > Of course I am now looking at how you approached this in the foldernode
>  > module!
> I have now put the functionality in a module called "navigation". It
>  needs a bit more testing, though.
>
>  > When I have a improved version of the sitemap module I'll add it to the
>  > sandbox.
> Cool - I'm sure the sitemap functionality is also useful for others.
>  -- Andreas

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

Reply via email to