What do you think about this?
Currently I have very limited free time, plus next week I go on a long-long
holiday :)
I could do the transferring of component and parameter descriptions from the
static component reference to the JWC files this week and send you the
generated forrest XML skeletons.
It's sad but I will release TapDoc to the public only in September after I
come home from vacation. (It works now but several enhancements should be
done yet.)
BR,
Norbi
----- Original Message -----
From: "Norbert Sándor" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, August 07, 2005 2:08 AM
Subject: Fw: [IMPORTANT] Community effort to supply documentation
It seems that the list don't accept attachements... :\
----- Original Message -----
From: "Norbert Sándor" <[EMAIL PROTECTED]>
To: "Tapestry development" <[email protected]>; "Howard
Lewis Ship" <[EMAIL PROTECTED]>
Sent: Saturday, August 06, 2005 11:31 PM
Subject: Re: [IMPORTANT] Community effort to supply documentation
I have successfully used TapDoc to generate skeleton Forrest XML files for
the Framework component reference. I attached the output files.
You are right that it is not trivial to automatically generate
documentation
because of links, etc.
But it would be great :)
The current state of TapDoc helps also to build the docs more easily:
- Component and parameter descriptions should be copied to the jwc files
- TapDoc can be used to generate skeleton Forrest XML files
- Custom parts like "see also" and examples should be manually copied to
the
XMLs currently. But it would not be difficult to merge the generated XMLs
with static hand-written ones (eg. example sections), so copy-paste could
be
eliminated.
I would help (if you accept it) in:
- copying documentation from current XMLs to component specifications
- generating Forrest XML skeletons
BR,
Norbi
----- Original Message -----
From: "Howard Lewis Ship" <[EMAIL PROTECTED]>
To: "Tapestry development" <[email protected]>
Sent: Saturday, August 06, 2005 4:43 PM
Subject: Re: [IMPORTANT] Community effort to supply documentation
As appealing as that is, there's also examples, hyperlinks,
cross-refererences to other classes and components, etc.
---------------------------------------------------------------------
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]
