Just talking about the Ajax topic, there already is a Wiki page that, at least to some degree, goes into it... why don't we do some brainstorming and determine what everyone thinks needs to be covered? Maybe it's enough to just do a "survey" or various Ajax libraries with some examples, along with the basic info on Ajax that's on the Wiki page already.

Martin Cooper wrote:


On 10/25/05, *Frank W. Zammetti* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Ted (et al), I'd like to take a crack at writing that Ajax part... where
    do you envision it fitting?  I see it in the FAQs under the Howto Guides
    section.  Anyone have a different thought?


I would suggest writing it up as a wiki page, at least initially. There are going to be multiple ways of doing all of the pieces Ted mentioned (i.e. Ajax, Portlets and RIA), so it would be good to have that variety reflected in multiple wiki pages, perhaps one page per technique. We can then distill out the essential parts for the core documentation.

--
Martin Cooper


    Frank

    Apache Wiki wrote:
     > Dear Wiki user,
     >
     > You have subscribed to a wiki page or wiki category on "Struts
    Wiki" for change notification.
     >
     > The following page has been changed by TedHusted:
     > http://wiki.apache.org/struts/StrutsClassicRelease130
     >
     >
    
------------------------------------------------------------------------------

     >   NOTES
     >
     >    * Core - Working down documentation menu bar, we into the
    UserGuide and up to Section 3.4. Some nomenclature has been updated
    for Section 4, but more review is needed.
     > +  * Core - FAQs also need to be reviewed.
     > +  * Core We should add someplace sections about "Using Ajax with
    Struts", "Using Portlets with Struts", and "Using RIA with Struts
    (e.g. Flex)".
     >    * Apps - Each application should be a separate artifact with
    its own build. MailReader should be streamlined to demonstrate best
    pratices. Add Struts Cookbook () to demonstrate other techniques.
    Move Tiles-Documentation to Sandbox until it can be reworked,
    perhaps for Standalone Tiles, and/or move important content to
    Cookbook.  Also see if the struts-examples content can be moved to
    the Cookbook, to reduce number of applications in play.
     >    * Plugins - Rename to Extras and move Actions package from Core.
     >
     >
     >
    ---------------------------------------------------------------------
     > To unsubscribe, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
     > For additional commands, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
     >
     >
     >
     >

    --
    Frank W. Zammetti
    Founder and Chief Software Architect
    Omnytex Technologies
    http://www.omnytex.com
    AIM: fzammetti
    Yahoo: fzammetti
    MSN: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>

    ---------------------------------------------------------------------
    To unsubscribe, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>
    For additional commands, e-mail: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>



--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to