Be sure to do an update today because I noticed there has been a big checkin of stuff last night.
Also when you checkout forrest, be sure to check out the trunk (myfaces/forrest/trunk). Good luck. sean On 7/8/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > On 7/8/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > Yes we could use help porting these over (I did a few way back when.) > > The component documentation should really go in the website so if you > > could get up to speed with forrest that would be good. Basically just > > install forrest and setup a FORREST_HOME environment variable (follow > > their instructions on that.) Then you can checkout the > > "myfaces/forrest" project from SVN and build. > > > > There is a sample component documentation that I setup > > (component-template.xml.) This is the preferred way to document > > components. Note that I setup a template for most compoonets a while > > back (with just a bunch of to-dos.) If you want to document one of > > those, please just replace with the new component-template.xml format. > > The documentation for newspaperTable is representative of the new > > format. > > I use forrest for another project, and I already saw > component-template.xml in forrest/content/xdocs/components (checked > out along with current). > > I'll see what I can do later tonight. > > I wasn't sure if there were other reasons why that documentation > shouldn't be ported (like maybe it was completely out of date.) > > For anyone else who wants to help out on this, you also need to patch > forrest/content/site.xml so that the new component page shows up in > the index. > Ie, just add a > > <component-name="component-name" href="component-name.html"/> > > line in site.xml at the appropriate spot. > > This is all very easy work if you want to contribute -- it's just > time-consuming. > > I'll open up a JIRA issue with directions copied from above and we can > work on it in there. Folks can comment in the issue when they start > converting a page (or set of pages) so that we're not duplicating > work. >
