Great -- I hereby grab the write bit with the intention of fixing the API doc directory.
Will send mail when this is checked in. Eddie On 8/28/05, Rich Feit <[EMAIL PROTECTED]> wrote: > This is in -- revision 263967. > > Rich Feit wrote: > > > I agree, definitely. I should have my first cut at the "NetUI"->"Page > > Flow" change in within a few hours (sorry for the delay). At that > > point, I can wait before doing other page-stomping changes until > > you've made the change you're talking about. > > > > Rich > > > > Eddie O'Neil wrote: > > > >> Rich-- > >> > >> Hey; one other thing we should do is rename the directory that > >> contains the NetUI Javadoc. Currently, it's called > >> "classref_pageflows", and it should probably be called > >> "classref_netui". > >> > >> If you're working on fixing this name elsewhere, let's coordinate > >> this change so we don't stomp on each other's change and have to deal > >> with a large merge in the doc files. > >> > >> Sound good? > >> > >> Eddie > >> > >> > >> On 8/25/05, Eddie O'Neil <[EMAIL PROTECTED]> wrote: > >> > >> > >>> Yeah, that seems like a good characterization of the problem -- I've > >>> noticed that as well. We've always been NetUI as per: > >>> > >>> - the package name (org.apache.beehive.netui) > >>> - the names of the samples > >>> - the names of the TLDs > >>> - the name of the config file > >>> > >>> The site and doc seem to just conflate the two terms. It makes sense > >>> to me to use NetUI as the umbrella to describe the web / UI stuff in > >>> Beehive which includes (today) Page Flow as a controller technology > >>> and the JSP tags as a UI technology. In the future, we may expand the > >>> number of technologies under this NetUI umbrella to include AJAX, JSF, > >>> and other things. > >>> > >>> So, the use of the NetUI name seems like a good thing. ;) > >>> > >>> I'll help change those references where I see them... > >>> > >>> Eddie > >>> > >>> > >>> On 8/25/05, Richard Feit <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>> This does bring up a larger issue that we've talked about in the past: > >>>> the term "NetUI" vs. "Page Flow". I see that you changed "NetUI Page > >>>> Flow" to "NetUI" on that page, but I think that it probably needs > >>>> to get > >>>> changed throughout the rest of the docs (including the rest of > >>>> index.html). > >>>> > >>>> So, change "Page Flow" to NetUI in the doc tree and throughout the doc > >>>> text? Thoughts? > >>>> > >>>> The only other thing I'd change is some wording in the description of > >>>> NetUI. NetUI is *more* than "an annotation-driven web application > >>>> programming framework built on Struts" (which is exactly what Page > >>>> Flow > >>>> is). It's basically Page Flow plus the Tags. Anyone disagree with > >>>> that > >>>> distinction? > >>>> > >>>> Rich > >>>> > >>>> Eddie O'Neil wrote: > >>>> > >>>> > >>>> > >>>>> All-- > >>>>> > >>>>> I just reworked the content of the /index.xml file for the release > >>>>> documentation kit to include some high-level information about what > >>>>> Beehive is. Will still add some content about how the Beehive > >>>>> sub-projects work together (ie -- they can be used together or > >>>>> separately). > >>>>> > >>>>> Interested parties, please take a look and pass along comments. > >>>>> > >>>>> Thanks! > >>>>> > >>>>> Eddie > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >> > >> > >> > > >
