Re: Want XSL stylesheet that is used at jakarta.apache.org fortaglibs.

[Kees Jongenburger]

Hi,

I agree that that whould be very nice. 
I did some work on it.
for me basicaly adding:
info to tag attributes and
bodycontentinfo is all that is nececary.

we a looking if Ant could remove those tags when they are
copyed to the WEB-INF dir.

attached the "xslt and demo html"


Alen Milkovic wrote:
> 
> I read in a post here that someone had the same idea as me:
> To extend the taglib.tld with comments so I could write
> the definition and the documentation in the same file.
> I plan to use this extended taglib format (xml of course) to generate
> the taglib.tld file and documentation (Xalan & Cocoon). I have also plans
> to make it possible to generate skeleton classes and ant files (Xalan).
> 
> What do you people think? If people are interested I can post
> some examples as my work progresses. As for now I only have
> a preliminary xml format with support for multiple languages. And
> have started on a xsl template to generate the documentation.
> 
> Anyway, I want to present the tags in the same manner as on
> jakarta.apache.org so I wondered if anyone has made a xsl stylesheet
> for this that generates the pages from html. I would really apreciate it.
> 
> *****************************************************************
> This footnote confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
> *****************************************************************

-- 
Kees Jongenburger/Java developer/ [EMAIL PROTECTED] /NetlinQ Framfab
All our sourcecode are belong to us

Title: MMBase taglib documentation

Tag library for MMBase based on MMCI(MMBase Cloud Interface) list|head|tail|cloud|mod|node|param|info about the syntax of this document list toc info The list tag provides a syntax to list objects managed by MMBase attributes nodes Comma-separated list of nodes, this attribute defines the starting point of the list.the parameter is equivalent to node node Node number, or node alias. This attribute defines the starting point of the list type A comma-separated list of NodeManagers and/or RelationManagers. The list forms a "chain of relations" examples "mags" "mags,news" or "mags,related,news" "mags,,news,images" or "mags,related,news,related,images" fields Comma-separated list of fields that should be made available in the page. The fields are selected from attributes of the corresponding node managers defined in type. If the type fields contains more elements eq type="mags,news" then it is required to append a prefix to each field listed eq fields="mags.title,news.title".In the jsp page the values are available in form of Strings eq mags.title is available as mags_title and can be accessed using <%= mags_title >. where sorted direction distinct max The maximum allowed results offset The start index search Determines how directionality affects the search. This is a string with the following possible values: "both", which is the default, searches for all valid relations through a path, checking full directionality of relations where appropriate. "destination" searches for only those relations in a path where valid relations exist from source to destination, in the order of the nodemanagers given in the nodePath. "source" searches for only those relations in a path where valid relations exist from destination to source, in the order of the nodemanagers given in the nodePath. "all" searches all existing relations, and does not check on directionality. A value of null or any other values than those listed above are ignored. In that case, search is treated as if the default ("both") was specified. prefix body JSP For every item found the list tag will iterate through the content of the body of the tag. Some variables are available in this context node: depending on the type of listing this might be a real or a virtual node fields defined in the type attribute: if type attribute is type="number" then the String number will be available from the jsp. If the type="mags.number,news.number" the variables available wil be mags_number and news_number item: for each type in the types field a String is returned. The first item is called item1 the second item2 etc... uses org.mmbase.bridge.Cloud.getList(...) org.mmbase.bridge.NodeManager.getList(...) example <mm:list node="123" type="mags,news" fields="mags.title,news.number" > <mm:head> magazine list </mm:head> <%= mags_title %> <mm:tail> </mm:tail> </mm:list> head toc info The tag can be used in a list to determine if this is the fist item in the list body JSP tail toc info The tag can be used in a list to determine if this is the fist item in the list body JSP cloud toc info The cloud tag initializes the cloud to use attributes name The name of the cloud eq "mmbase" cache expire logon The authentication name to use (account). pwd The password to use to logon to the cloud. authenticate body JSP mod toc info This tag can be used to call features provided by Modules in MMBase attributes name value uses org.mmbase.bridge.Module.getInfo(..) node toc info This tag replaces the mod-mmbase-field tag attributes number action field type uses org.mmbase.bridge.Node param toc info This tag handles request parameters attributes number name This document lists the current tags implemented for MMBase. Attributes in red are required. If a tag definition contains a body section this means that the tag might do something with the content of the body.

Title: taglib documentation

info about the syntax of this document Attributes in red are required. If a tag definition contains a body section this means that the tag might do something with the content of the body. |
toc	info attributes body uses example