You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Programozás <pr...@hotmail.com> on 2004/04/17 12:58:39 UTC
Tapestry component reference
Hello,
I have a plan to create some functionality to generate a component reference from a set of library and/or application files.
I've begun to develop an Ant task which uses XSL templates for the layout.
I have plans for creating a unified folder structure for holding component examples which would be included automatically into the generated component reference.
I was wondering if Tapestry already has some similar mechanism for this purpose, or the surrent component reference was created manually?
If there is no such tool yet, and somebody thinks that it would be useful for public purposes too then please write some details about how can this "task" be compatible with the current document and build structure.
Norbi
Re: Tapestry component reference
Posted by Programozás <pr...@hotmail.com>.
I'm on the way, I will write to this list if at least part of it is
finished.
I'm happy that somebody is interested in my idea.
Norbi
----- Original Message -----
From: "Mindbridge" <mi...@yahoo.com>
To: "Tapestry development" <ta...@jakarta.apache.org>
Sent: Sunday, April 18, 2004 9:59 AM
Subject: Re: Tapestry component reference
> Hi,
>
> I just want to say that something like this would be extremely useful and
> would be very helpful for some of things that are being done. Please
mention
> when you have something ready, I personally will be waiting with great
> anticipation :)
>
> -mb
>
> ----- Original Message -----
> From: "Programozás" <pr...@hotmail.com>
> To: "tapestry-dev" <ta...@jakarta.apache.org>
> Sent: Saturday, April 17, 2004 1:58 PM
> Subject: Tapestry component reference
>
>
> Hello,
>
> I have a plan to create some functionality to generate a component
reference
> from a set of library and/or application files.
> I've begun to develop an Ant task which uses XSL templates for the layout.
> I have plans for creating a unified folder structure for holding component
> examples which would be included automatically into the generated
component
> reference.
>
> I was wondering if Tapestry already has some similar mechanism for this
> purpose, or the surrent component reference was created manually?
> If there is no such tool yet, and somebody thinks that it would be useful
> for public purposes too then please write some details about how can this
> "task" be compatible with the current document and build structure.
>
> Norbi
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
RE: Tapestry component reference
Posted by "Howard M. Lewis Ship" <hl...@comcast.net>.
It would be very cool to use XDoclet + Forrest, perhaps, to generate some or all of the
documentation, to ensure that it is kept in synch at all times.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Tapestry: Java Web Components
Creator, HiveMind
http://howardlewisship.com
> -----Original Message-----
> From: Mindbridge [mailto:mindbridgeweb@yahoo.com]
> Sent: Sunday, April 18, 2004 4:00 AM
> To: Tapestry development
> Subject: Re: Tapestry component reference
>
>
> Hi,
>
> I just want to say that something like this would be
> extremely useful and
> would be very helpful for some of things that are being done.
> Please mention
> when you have something ready, I personally will be waiting with great
> anticipation :)
>
> -mb
>
> ----- Original Message -----
> From: "Programozás" <pr...@hotmail.com>
> To: "tapestry-dev" <ta...@jakarta.apache.org>
> Sent: Saturday, April 17, 2004 1:58 PM
> Subject: Tapestry component reference
>
>
> Hello,
>
> I have a plan to create some functionality to generate a
> component reference
> from a set of library and/or application files.
> I've begun to develop an Ant task which uses XSL templates
> for the layout.
> I have plans for creating a unified folder structure for
> holding component
> examples which would be included automatically into the
> generated component
> reference.
>
> I was wondering if Tapestry already has some similar
> mechanism for this
> purpose, or the surrent component reference was created manually?
> If there is no such tool yet, and somebody thinks that it
> would be useful
> for public purposes too then please write some details about
> how can this
> "task" be compatible with the current document and build structure.
>
> Norbi
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry component reference
Posted by Mindbridge <mi...@yahoo.com>.
Hi,
I just want to say that something like this would be extremely useful and
would be very helpful for some of things that are being done. Please mention
when you have something ready, I personally will be waiting with great
anticipation :)
-mb
----- Original Message -----
From: "Programozás" <pr...@hotmail.com>
To: "tapestry-dev" <ta...@jakarta.apache.org>
Sent: Saturday, April 17, 2004 1:58 PM
Subject: Tapestry component reference
Hello,
I have a plan to create some functionality to generate a component reference
from a set of library and/or application files.
I've begun to develop an Ant task which uses XSL templates for the layout.
I have plans for creating a unified folder structure for holding component
examples which would be included automatically into the generated component
reference.
I was wondering if Tapestry already has some similar mechanism for this
purpose, or the surrent component reference was created manually?
If there is no such tool yet, and somebody thinks that it would be useful
for public purposes too then please write some details about how can this
"task" be compatible with the current document and build structure.
Norbi
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org