Sounds like a good doc plan for the custom TreeRenderer, I will try to get the doc in today.
Carlin, could you send me a sample TreeRenderer impl class, if you have one lying around? On 12/7/05, Carlin Rogers <[EMAIL PROTECTED]> wrote: > > Steve, > > Here's an item I've thought of for your earlier query about doc needs. I > think you already have this on your list. We now allow users to configure > a > custom TreeRenderer implementation (beehive-974). The way to configure a > custom implementation of the TreeRenderer is through the beehive netui > config file. I put a note in the Javadoc at the top of the TreeRenderer > class but for some new additional doc we could... > > - Comment on the ability to implement your own TreeRenderer by extending > out > implementation and overriding any of the formatting methods desired and > state how to configure NetUI. Maybe this would go in the tagsTree.htmlpage, > just following the "TreeElement Rendered Contents" section which describes > the markup used to render a node. I'm open to suggestions. > > - add information about the new <tree-renderer-class> element (in the > <jsp-tag-config> section) to the beehive-netui-config document. > > Thanks, > Carlin > > On 12/1/05, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > > > > Steve-- > > > > Personally, I think that the Controls Tutorial will be more > > descriptive if it focuses solely on the end-to-end process of writing > > a Control. For example: > > > > - authoring the Control's source artifacts > > - building the Control > > - packaging the Control into a JAR file > > - authoring a JUnit test for the Control > > - testing the Control > > > > Today, most of the Controls Tutorial is about how to setup, build, and > > deploy a NetUI-enabled web application. While we should certainly > > have examples and documentation about how to use a Control from a Page > > Flow, it's probably more interesting to focus on the end-to-end cycle > > of building a Control JAR file. > > > > Note, this requires that I (finally!) commit the JUnit test > > container for Controls. Believe it or not, I've got that "svn add"ed > > locally and should have that done soon. Then, it's just a matter of > > rewriting the tutorial. > > > > Thoughts? > > > > Eddie > > > > > > > > On 11/30/05, Steve Hanson <[EMAIL PROTECTED]> wrote: > > > Hi Eddie and all: > > > > > > Eddie, yesterday you mentioned to me privately that you'd like to see > > the > > > control tutorial not use a page flow as its > > testing environment. Instead, > > > the page flow should be replaced with some sort of unit testing. > > > > > > Could you say more about what you are looking for here? > > > > > > thanks, > > > steveh. > > > > > > > > > > > > On 11/29/05, Steve Hanson <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi all: > > > > > > > > Seems like a good time to clean up and amend the 1.x docs. > > > > > > > > So here is a general call out for doc needs and wish lists for > Beehive > > 1.x > > > > . > > > > > > > > Are there any big, glaring problems with the current doc? > > > > Any little issues that have fallen through the cracks? > > > > > > > > Please respond with what you would like to see in the Beehive > 1.xdocs. > > > > > > > > thanks, > > > > Steve Hanson > > > > > > > > > > > > > > > > > > > > > > > > > >
